Tracing database activities in SQL Server 2005 vs. SQL Server 2000.
Creating SQL Server 2005 trace file for troubleshooting purposes for LiteSpeed, Quest Central for SQL Server and database applications supported on SQL Server 2005.
A SQL Profiler traces databases activities and save the report in different formats.
This is a helpful tool to investigate a technical support issue. While the SQL Server trace profile is collecting data, you should recreate the problem and the potential problem will be logged in this report.
On SQL Server 2000, it is SQL Profiler and you can run it from Start/All Programs/ Microsoft SQL Server/Profiler.
On SQL Server 2005:
From the Start | All Programs | Microsoft SQL Server 2005 | Performance Tools | SQL Server Profiler or Start | All Programs | SQL Server Management Studio Interface | Tools menu/ SQL Server Profiler.
The naming and basic functionality of the utility remains the same as its SQL Server 2000; however, these are the enhancements introduced in this new version, see Microsoft or SQL Server 2005 Books online for additional information:
To generate a SQL Profile trace file:
1
To create a trace:
On the File menu, click New Trace, and connect to an instance of SQL Server. The Trace Properties dialog box appears.
In the Trace name box, type a name for the trace. You do not need to use a template.
To save the trace results, do the following: Click 'Save to file' to capture the trace to a file. Specify a value for Set maximum file size. The default value is 5 megabytes (MB) is fine.
Start the trace, run the failing process, then immediately stop the trace. Forward the resulting trace file to Support.
NOTE: The SQL Profile uses the database resources to generate this trace file, performance may be degraded.
© 2025 Quest Software Inc. ALL RIGHTS RESERVED. Terms of Use Privacy Cookie Preference Center