When you run a stored procedure that contains nested stored
procedure calls by using a Remote Procedure Call (RPC), you may notice that the
TextData column in the SQL Profiler trace shows incorrect values for the
nested stored procedure call events. The TextData columns of the SP:Starting and the SP:Completed events of the nested stored procedure may have the same value as
the TextData column for the RPC:Starting event.
To resolve this problem, obtain the latest service pack for Microsoft SQL Server 2000. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:
290211
(http://support.microsoft.com/kb/290211/
)
How to obtain the latest SQL Server 2000 service pack
The English version of
this fix has the file attributes (or later) that are listed in the following
table. The dates and times for these files are listed in coordinated universal
time (UTC). When you view the file information, it is converted to local time.
To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel.
To work around the problem, use the ObjectID column in the SQL Profiler trace to identify the stored procedure
that was called instead of the TextData column.
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.This problem was first corrected in Microsoft SQL Server 2000 Service Pack 4.
Start SQL Query Analyzer, and then connect to a server
that is running SQL Server 2000.
Run the following Transact-SQL statement:
Use Northwind
Go
Create Procedure [dbo].[sp_InnerRepeatedTextData]As
Begin
Select 1
End
Go
Create Procedure [dbo].[sp_OuterRepeatedTextData]As
Begin
Exec sp_InnerRepeatedTextData
End
Go
Create a new SQL Profiler trace. To do so, follow these
steps:
Start SQL Profiler.
On the File menu, point to
New, and then click Trace.
In the Connect to SQL Server
dialog box, type the SQL Server name and the authentication details, and then
click OK.
In the Trace Properties dialog
box, click the Events tab.
Click to select Stored Procedures
in the Available event classes: list box, and then click
Add.
Click the Data Columns tab, click
ObjectID in the Unselected
data: list box, and
then click Add.
Click Run.
In SQL Query Analyzer, run the following Transact-SQL
statement on the Northwind database:
{call sp_OuterRepeatedTextData}
In SQL Profiler, on the File menu,
click Stop Trace.
In the profiler, view the trace events that correspond
to the RPC:Starting, the SP:Starting, and the
SP:Completed event class.
You may notice that the TextData value is the same for the RPC:Starting, the SP:Starting, and the SP:Completed event, regardless of the stored procedure that is
called.
Back to the top
