Optimizing Microsoft SQL Server Reporting Services: Execution Log Reporting: Preparation as a Data Source

9. Navigate to, and enter, the SSP-RS001 folder we created above.

10. Right-click in the within the folder.

11. Select Paste from the context menu that appears, as depicted in Figure 3.



Figure 3: Placing Copies of the Components into the New Folder

Copies of the four files appear in the new folder.

We are now ready to create a database to house the data from the Execution Log. In doing so, we will make use of the files we have placed in the folder we created in this step.

Create a Database to Contain the Execution Log


Our next step is to create a database to contain the information from the Execution Log. As we have discussed, Reporting Services creates a log to house this information already – a log that we might simply access, and from which we might report, without the need for an “intermediate” database. The information that we find in the default database leaves a little to be desired from the perspective of formatting, ease of reporting and so forth. We will therefore take a gift as it is presented, and use the tools provided to create a database and user-friendly schema to make our job easier. We can, after all, modify the database as required in the future, should the need arise, based upon client feedback or our own inclinations.


To begin the construction of our reporting data source, we will first create a new database from the MSSQL Server Enterprise Manager, and then create the constituent tables of the database using the Query Analyzer. This step will be facilitated by the table creation script that resides among the components that we placed into the folder we created above.


1. Click Start.

2. Navigate to the Microsoft MSSQL Server Enterprise Manager shortcut in the Programs group, as appropriate.


The equivalent on my PC appears as shown in Figure 4.




Figure 4: Navigating to the Enterprise Manager

3. Select Enterprise Manager from the menu. The Enterprise Manager console opens.


4. Expand Microsoft SQL Servers by clicking the “+” sign to its immediate left, as required.

5. Expand SQL Server Group.

6. Expand the appropriate server.


The Enterprise Manager console appears as depicted in Figure 5.




Figure 5: Enterprise Manager (Compressed) View

 

Continues…



Related Articles :

  • No Related Articles Found

No comments yet... Be the first to leave a reply!

Software Reviews | Book Reviews | FAQs | Tips | Articles | Performance Tuning | Audit | BI | Clustering | Developer | Reporting | DBA | ASP.NET Ado | Views tips | | Developer FAQs | Replication Tips | OS Tips | Misc Tips | Index Tuning Tips | Hints Tips | High Availability Tips | Hardware Tips | ETL Tips | Components Tips | Configuration Tips | App Dev Tips | OLAP Tips | Admin Tips | Software Reviews | Error | Clustering FAQs | Performance Tuning FAQs | DBA FAQs |