How to Monitor Performance in .NET framework

Painting QR in .NET framework How to Monitor Performance

You can monitor execution performance by using Report Manager to enable or disable logging and to limit the number of days for which logging is retained. Execution logs differ from trace logs because the latter are stored in a set of files,

10

A script to create tables in your own database A Data Transformation Services (DTS) package to load logging records into this database Reports that allow you to review the execution information loaded into the new database You will work with these tools later in this chapter. You can schedule the DTS package to perform periodic extracts from the ExecutionLog table to keep your logging database current and to allow you to delete rows from the log tables.

You can use the Site Settings page in Report Manager to start or stop execution logging at any time. You must be assigned to the System Administrator role in SQL Server to be able to change this setting. By default, execution logging is enabled, and log records will be kept only for 60 days. You can increase or decrease the number of days as desired to limit the amount of logging history that accumulates in the ExecutionLog table in the ReportServer database. Logging records that exceed the specified number are removed each day at 2:00 AM (local time for the Report Server). Alternatively, you can remove this limitation if you want to allow logging records to accumulate indefinitely. If you use the DTS package mentioned earlier to copy the logs to a reporting database, you can delete logs as soon as they are copied to the logging database by adding an additional package step.

In this procedure, you will open the Site Settings page in Report Manager to review the current execution logging settings.

whereas execution logs are stored in the ReportServer database. Because execution logs are intended for continual analysis, the data is stored relationally. The information that is stored in the ExecutionLog table of the ReportServer database is not the best format for general reporting and analysis, but you can create your own logging database to which you can export logging records on a periodic basis. Reporting Services supplies you with the following tools to facilitate reporting on the logs:

Click the Site Settings link to review the settings shown here:

If you want to disable execution logging, you can clear the Enable Report Execution Logging check box. Notice that you can type a different number of days to change the frequency with which logging records are removed from the ExecutionLog table. To make the changes take effect, you need to click the Apply button.

Reporting Services provides the tools you need to effectively report and analyze information related to report processing. To get started, you will need to create a SQL Server database, and then you can use a supplied script to build the necessary tables in your new database. After creating the tables, you can use the DTS package supplied by Reporting Services to load the new tables with data from the ExecutionLog table. You will need to make a small modification to this DTS package to reference the correct path to an .ini file needed by this DTS package. In this procedure, you will create the RSExecutionLog database in which you will create tables using a script and then use a DTS package to load data into the tables.

Open Enterprise Manager. Expand the (local) server (or the instance to which you installed Reporting Services and the practice files), right-click the Databases folder, and then click New Database.

10

Note The createtables.sql file is included for your convenience in the practice files. Reporting Services supplies this file on the installation CD in the \Extras \Execution Log DTS Package folder. 6