MSSQL Server Reporting Services: Black Belt Administration: Prepare the Execution Log for Reporting - Page 5
January 18, 2005
11. Adjust the settings on the Data Files and Transaction Log tabs to place the files in the file system location you desire (I left mine at default for this exercise).
12. Click OK to accept changes and to close the Database Properties dialog.
The dialog closes and the database appears (after refreshing the Enterprise Manager console, as required).
13. Leaving Enterprise Manager open, click the Start button once again.
14. Navigate to the Microsoft MSSQL Server - Query Analyzer shortcut in the Programs group, as appropriate.
The equivalent on my PC appears as shown in Illustration 8.
Click for larger image
15. Select Query Analyzer from the menu.
The Connect to SQL Server dialog appears.
16. Select the appropriate server in the SQL Server selector box.
17. Select the radio button to the left of the appropriate authentication selection, supplying login credentials as required.
The Connect to SQL Server dialog appears (with my settings for this exercise) as depicted in Illustration 9.
18. Click the OK button to log in to SQL Server via Query Analyzer.
The Connecting ... message briefly appears, and then the Query Analyzer console opens.
19. Select RSExecutionLog in the Database Selector atop the console.
20. Select File --> Open from the main menu.
21. Navigate to the folder we created above, RS013, in the Open Query File dialog that appears.
22. Select the following file within the RS013 folder:
The Open Query File dialog appears similar to that shown in Illustration 10.
23. Click Open on the Open Query File dialog to open the script.
The table creation script opens, and appears in the Editor pane of the Query window. This script, executed within the new RSExecutionLog database, will create the tables that we will target for the Execution Log data in later steps.
24. Click the Execute Query button on the toolbar, as depicted (circled) in Illustration 11.
NOTE: Had we named the database anything other than RSExecutionLog, or if we were working with any but the local instance of MSSQL Server, we would have needed to edit rsexecutionlog_update.ini for the respective Execution Log database (referenced as "[Destination]"), and / or Server identification, etc.. Modifications can be accomplished by accessing rsexecutionlog_update.ini (another of the files we copied into the RS013 folder above), using Notepad or any other text editor, as we shall see later in our exercises.
The script is executed, and we are informed of its successful completion, along with the various events that have transpired, in the Messages pane of the Query window, as shown in Illustration 12.
At this point, we can verify creation of the tables by shifting back to Enterprise Manager, expanding the RSExecutionLog database we created earlier, and clicking on Tables. Our tables appear as depicted in Illustration 13.
25. Select File --> Exit to close Query Analyzer.
Our preparation of the target database is now complete. We are ready to populate the tables with the contents of the Execution Log, which we will accomplish in the next section.