Sql 2008 r2 reporting services log files

These decisions will impact how the data is returned to the design grid and ultimately to the report itself. The Shared Dataset Properties windows opens; enter a data set name, and be sure the Data Source field displays the data source mentioned in the above step. Next, click on Query Designer to open the Query Designer window as displayed in the below figure. The query designer has several options and methods that will ultimately affect your end report. See the figure below for the exact query; finally, click OK, and OK.

Name the new report and select the Report not Report Wizard template. Finally, click Add. The last two steps in the Add Report Process is to add our shared data source and shared data set.

Name your Report data source and then click on the Use shared data source reference radio button, and select the previously created data source from the list. Set your credentials if needed. Follow the same process with the data set. Right click on Datasets, and select Add Dataset. The first step is to prepare the report by adding a Report Header and Report Footer.

Do the same for Page Footer. Next, we will add the Top 10 Filter Criteria to the Table. Right click on the upper left corner box of the table and Select Tablix Properties. Additionally add the Filter Properties as described in the below figure. Subsequently, add the Sorting functionality as shown in the figure below. As we want the longest running queries, be sure to change the Order to Z to A.

Finally for this table, a few formatting items are completed. First, the column names and column widths are adjusted and the column headers font and background colors are changed to white and blue respectively.

Also, a row is inserted above the existing column headers which describes the data displayed in this particular portion of the report. Next, using the same process described above, add two additional tables, one for Generated Bytes and one for Row Counts. One short cut you could take is to copy and paste first table twice , and then change the column 2 header and value, and then adjust the Filtering and Sorting options to reflect the current Top 10 Item.

The ensuing figure displays the three tables for our report. The variation of the reports from this point are only limited by the data in the ExecutionLogStorage table. Time to look at some new Execution Log Reports. A group of tables or charts by day of the week, day of month, and time of day would likely be beneficial. Skip to main content. This browser is no longer supported. Download Microsoft Edge More info. Contents Exit focus mode. Is this page helpful?

Please rate your experience Yes No. Any additional feedback? In this article. In actuality, there are several different logs which are at our disposal when working with SSRS. As mentioned above, the Execution Log retains details about query and report execution in the ReportServer database and is probably your first troubleshooting stop when errors arise. The SSRS trace log is likely your second stop in your trouble shooting journey.

The information in this log is extensive and maybe in some ways overwhelming. However, to assist in troubleshooting a problem, this level of detail is significant and necessary. If you have already reviewed the execution log and did not find what was causing an error, the level of detail in the trace log will be helpful in reviewing an issue. Likely, the most common search you will do, at least initially, is for an error. You can, if you would like, change the default name for the trace file.

Furthermore the log file is in plain text, so it is readable with any text editor. You can actually set the trace level from 0 tracing turned off to 4 full verbose messaging. In order to make these and other adjustments to the trace file, you need to modify the ReportingServicesService.

As shown below, you can adjust several of the settings in the ReportingServicesService. Notice in the above screen print, that we can additionally adjust the file size. Microsoft does recommend not changing the following log settings: Prefix or TraceFileMode. Finally the last line in the screen print specifies not only the trace level 3 in the above example , but it also allows you to specify the component categories to be included in the trace. The default level for these options is: "all:3".

Now that we have the trace setup, we can now review what is actually in the file. As shown in the below example, the beginning of the trace file shows a whole sundry of different values which are set when SSRS starts.