CHAPTER 10 MANAGING REPORTS
Note With data-driven subscriptions, unlike with standard subscriptions, you can control the rendering format
per subscriber because it too is a data-driven setting. If you need to control the rendering format per user, you can
add a field to store this value in the Employee table and select this value in the query. Also note that the default
rendering format for subscriptions is a Web archive. For many types of reports, this isn’t the ideal choice. Other
printable reports are better suited for printed reports, such as Adobe Acrobat PDF, Microsoft Word files or static
image files such as TIFF.In step 5, you have the option to specify a static value or a value from the database. Since you want
the subscription to produce one report for every record returned, you’ll select the radio button to get the
value from the database. The EmployeeTblid field is used for the one parameter in the report. Because
you’ve selected this field in the query and passed this as a parameter input, each report is automatically
generated with data specific to the employee who subscribed to the report. Select EmployeeTblID as the
value to use as the parameter and click the Next button. The other field, HWUserLogin, is put in the
driving query, which you’ll ultimately compare to the Windows login name of the user executing the
report. You can accomplish this, as you’ll see in Chapter 11, by using the User global collection.
For the final step, you create a schedule that processes the report each weeknight at 9:30 PM, as
described earlier. You can create another shared schedule to process the subscription and test it to verify
that the e-mail is being delivered successfully. After that is complete, you’re finished with the
subscription configuration.Performing Execution Auditing and Performance Analysis
As you deploy SSRS between development, test, and production environments, you'll find that gauging
performance involves a variety of benchmarking and analysis tools. Based on the performance analysis,
administrators are armed with the knowledge of what stress levels their servers can endure, and they’ll
be able to configure the environment accordingly. We’ll show how to put the components of your SSRS
deployment to the test and show how to analyze the output using standard tools. Note The SSRS 2008 release brought us a redesigned reporting engine, with its memory management features
enhanced by removing the reliance on IIS that prior versions of SSRS suffered. With that release, both Web and
Windows services were combined into one Windows service.Many agencies need to monitor and archive the details of user activity. This is especially important
if you suspect there’s undesired access to data. SSRS provides a built-in logging feature that captures
several key pieces of information. This information is useful in two ways:- You can capture performance information about the reports, such as the
processing duration and record count. - You can capture security information, such as who executed the report and
whether or not they were successful.