Troubleshooting
Problem
This technote identifies how to create and review Microsoft® SQL Server trace files to identify issues with IBM® Rational® RequisitePro® projects.
Resolving The Problem
How to generate a SQL Server trace file:
- Open SQL Profiler by selecting Start > Programs > SQL Server > Profiler
- Select Create a new trace file
- Create the trace file by selecting File > New Trace
- Select the appropriate server where the database resides from the SQL Server drop down
- Select SQL Server Authentication
- Enter the sa user name and password or another account that is a SQL system administrator
- The Trace Properties Dialog window will appear, select the General tab, enter a name for the trace in the Trace Name field, check the option Save to file and enter a file name to save the trace to
- Select the Events tab, in the Available event classes:, select and Add the following:
Errors and Warnings
Stored Procedures
Transactions - Select the Filters tab, select DatabaseName\Like and provide the name of your RequisitePro database.
- Ensure that RequisitePro is open prior to starting the trace. Select the RUN command
- Once the RUN command is selected, the trace will begin, and will record any action performed by the user.
- If the trace needs to be paused select the Pause option, if the trace needs to be Stopped, select the Red stop arrow.
Reviewing a SQL Server trace file:
A SQL trace file generated in the SQL Profiler will create file with a .trc extension. This file is a text file. Although a portion of it may be read in a text editor, it is recommended to review this file in the Profiler in SQL Server.
The Profiler will give the user the ability to review the trace file more fully. Users will be able to view transactions that have occurred, stored procedures, as well as error messages.
To open the trace file:
- Open SQL Profiler, Start > Programs > Microsoft SQL Server > Profiler
- Select File > Open >Trace File.
- Navigate to the directory where the trace file was stored and open it.
Historical Number
156937721
Was this topic helpful?
Document Information
Modified date:
16 June 2018
UID
swg21132269