How to use SQL Profiler in SQL Server 2005 to trace database events in Microsoft Dynamics SL
This article describes how to use Microsoft SQL Profiler in Microsoft SQL Server 2005 to trace database events in Microsoft Dynamics SL.
Applies to: Microsoft Dynamics SL
Original KB number: 925033
Knowledge Base articles are intended to provide reactive, troubleshooting help.
You can also use the Advanced Search functionality to find information throughout CustomerSource or PartnerSource, including the Knowledge Base.
Steps to trace database events
To use SQL Profiler in SQL Server 2005 to trace database events in Microsoft Dynamics SL, follow these steps:
Download, and then save the SQL2005.tdf file on the desktop of the computer that is running SQL Server 2005.
Microsoft scanned this file for viruses. Microsoft used the most current virus-detection software that was available on the date that the file was posted. The file is stored on security-enhanced servers that help prevent any unauthorized changes to the file.
Double-click the KB925033_SQL2005.tdf file, and then select OK when you receive the following message:
SQL Server Profiler - File C:\Documents and Setting\username\Desktop\DynamicsSL2005.tdf was imported successfully
On the File menu, select New Trace.
Connect to the server that is hosting the Microsoft Dynamics SL databases.
On the General tab, select the Use the template: drop-down box, select KB925033_SQL2005 (user), and then select Run.
Select File, and then select Pause Trace.
Start Microsoft Dynamics SL. Run Microsoft Dynamics SL to the point before the event that you want to trace.
Switch to SQL Profiler, select File, and then select Run Trace.
Run Microsoft Dynamics SL until you complete the event that you want to trace.
Switch to SQL Profiler, select File, and then select Stop Trace.
The trace results can be viewed on screen. The trace results can also be saved to a file. The file can then be sent to technical support for review.
For more information about how to create SQL Profiler traces in Microsoft SQL Server 2000, see How to troubleshoot the error message: "Crystal Error 534 - Error detected by database DLL" in Microsoft Dynamics SL.