When working with SQL Server through a client application, it's often extremely helpful to see the client application as it appears from SQL Server.
When working with SQL Server through an ADO Recordset, an ADO.NET dataset, or a Visual FoxPro remote cursor, the instructions that are actually being received by the server can sometimes be very different from what we think is being sent.
The SQL Server Profiler can often help debug an application by understanding what our tools are actually sending to the server.
For instance, when attempting to understand what SQL Server is receiving in response to an action in a Visual FoxPro client application, start a trace in SQL Server Profiler, trapping the following events for the indicated client-side actions:
|If using||Trap with event|
|Non-parameterized views||SQL:Batch Starting|
|SQL Pass-through||SQL:Batch Starting|
Contributors: Steve Sawyer
( Topic last updated: 2003.07.11 11:31:30 AM )