This article describes how to use Microsoft SQL Profiler in Microsoft SQL Server 2005 to trace database events in Microsoft Dynamics SL.
Knowledge Base articles are intended to provide reactive, troubleshooting help. As this document contains informational or ‘how to’ related material, we have moved the document to one of the following areas:
You can also use the Advanced Search functionality to find information throughout CustomerSource or PartnerSource, including the Knowledge Base. Advanced Search can be found on the CustomerSource Home Page and the PartnerSource Home Page, or by using one of the following links:
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.
The following file is available for download from the Microsoft Dynamics File Exchange Server:
KB925033_SQL2005.tdf Release Date: May 3, 2007
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 click 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, click New Trace.
Connect to the server that is hosting the Microsoft Dynamics SL databases.
On the General tab, click the Use the template: drop-down box, click to select KB925033_SQL2005 (user), and then click Run.
Click File, and then click 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, click File, and then click Run Trace.
Run Microsoft Dynamics SL until you complete the event that you want to trace.
Switch to SQL Profiler, click File, and then click Stop Trace.
Note 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, click the following article numbers to view the articles in the Microsoft Knowledge Base:
869048 How to troubleshoot the error message: "Crystal Error 534 - Error detected by database DLL" in Microsoft Dynamics SL
936578 How to use SQL Profiler in SQL Server 2000 to trace database events in Microsoft Dynamics SL