Optimizing Microsoft SQL Server Reporting Services: Performance and Access Reports from the Execution Log
7. Click OK.
We are returned to the Home page Folder View, and see our new folder appear on the Contents tab, as shown in Figure 9.
Figure 9: The Execution Log Reports Folder, on the Folder View – Contents Tab
8. Click the link for the new Execution Log Reports folder, to open it. We enter the Execution Log Reports folder, which is empty at present.
9. Click New Data Source atop the Folder View, as depicted in Figure 10.
Figure 10: Click New Data Source atop Report Manager Folder View
The New Data Source page appears.
10. Type the following into the Name box:
11. Type the following into the Description box:
Shared Data Source for Execution Log Reporting
12. Ensure that the checkbox to the left of Enable this data source is checked (the default).
13. Ensure that Microsoft SQL Server is selected in the Connection Type selector.
14. Type the following into the Connection String text box:
data source=”(local)”;persist security info=False;initial catalog=RSExecutionLog
15. Under Connect Using, select Windows NT Integrated Security.
NOTE: Adapt the Data Source and authentication settings to your own environment, as necessary (for example, if the RSExecutionLog database is on another server and access is being attempted across a network, etc.)
With our input, the New Data Source page appears as shown in Figure 11.
Figure 11: The New Data Source Page, with Input
16. Click OK to accept the shared data source.
We are returned to the Execution Log Reports page, Folder View, and see our new data source appear on the Contents tab, as depicted in Figure 12.
Figure 12: The Data Source Appears on the Folder View, Contents Tab
Having created a data source, we will now upload the sample Execution Log reports from the Report Manager. We will then marry the reports to the common data source we have created.