create code 128 barcode c# User!UserID in C#

Encoder ANSI/AIM Code 128 in C# User!UserID

Sometimes you might want to develop a report where you limit the data shown depending on the specific user requesting the report. Normally, I prefer to use security to determine who can run a report; therefore, anyone with the rights for the report can see all the data, but this isn t always what you want. I have some reports that anyone in our company can use as far as security is concerned. First, I create a table for the reports that lists the user, what reports they can run, and the parameter values for that report. The report dataset joins to this table. A key point here is that a query parameter doesn t have to be mapped to a report parameter. Instead, the query parameter is mapped to the User!UserID global parameter. This global parameter contains the user running the report. This means that you can t use this for subscriptions. Also, report snapshots can use the wrong UserID when accessed via web services or URL access. Report Snapshots work correctly with UserID only when the report is accessed via Report Manager. My advice is to only use UserID for on-demand reports. User!UserID includes the domain. If you don t want the domain, use the following expression when mapping the query parameter:

Summary

Reporting Services is both a flexible and powerful tool, but there are a number of things we need to be aware of to derive maximum performance from our reports. Hopefully I ve provided you with several ideas that you can use when building your next report.

Bruce Loehle-Conger works for a Fortune 100 company and works with data ranging from real-time control databases to SQL Server to Sybase. He has been working with Reporting Services since it was first in beta form and was one of the first two MVPs to be awarded for Reporting Services.

SQL Server 2008 introduces three new features for tracking data and object changes within the database: change tracking, change data capture, and SQL

Server Audit. Based on the marketing information alone, it might be difficult to determine which, if any, would be useful for your specific scenario. In this chapter, I will compare the features, outline their pros and cons, and try to help you to decide which solution or solutions might work best in your environment.

Since shortly after the very first database was persisted to disk, database administrators everywhere have been asking questions like, Who did what to my data, and when did they do it It is in our nature to be curious about the way users utilize our systems in general. In some specific cases, it is important to track down exactly when a piece of data was changed, and who was responsible for the change. Before talking about the new features introduced in SQL Server 2008, it will be useful to briefly outline some of the key motivations for implementing an auditing or change tracking solution in the first place. One reason is compliance enforcement. Depending on your industry, you may be required to adhere to regulations for data access and privacy, for example Sarbanes-Oxley, HIPAA, or PCI-CISP. Even if you are not required to do so by law, you may still have an interest in recording information about all of the activity on your server. (For example, you may be interested in identifying specific activity, such as a delete operation that nobody will take credit for, without resorting to a log reader utility.) In the past, this could be accomplished by placing the server in C2 Audit Mode, which is an all-or-nothing approach, or by using SQL Trace. Both of these