Microsoft KB Archive/818079

From BetaArchive Wiki
< Microsoft KB Archive
Revision as of 18:05, 18 July 2020 by 3155ffGd (talk | contribs) (importing KB archive)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

Article ID: 818079

Article Last Modified on 11/2/2007


  • Microsoft SQL Server 2000 Developer Edition
  • Microsoft SQL Server 2000 Standard Edition
  • Microsoft SQL Server 2000 Enterprise Edition
  • Microsoft SQL Server 2000 Personal Edition
  • Microsoft SQL Server 2000 Enterprise Edition
  • Microsoft SQL Server 2000 Workgroup Edition
  • Microsoft SQL Server 2000 Desktop Engine (Windows)
  • Microsoft SQL Server 2000 Developer Edition
  • Microsoft SQL Server 2000 Enterprise Edition 64-bit


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.


Service pack information

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 How to obtain the latest SQL Server 2000 service pack

Hotfix information

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.

    Date         Time  Version         Size       File name
   31-May-2003  03:45  2000.80.818.0      78,400  Console.exe      
   24-Jun-2003  10:01  2000.80.818.0      33,340  Dbmslpcn.dll     
   24-Apr-2003  11:12                    786,432  Distmdl.ldf
   24-Apr-2003  11:12                  2,359,296  Distmdl.mdf
   29-Jan-2003  10:55                        180  Drop_repl_hotfix.sql
   26-Aug-2003  05:16  2000.80.854.0     528,960  Dtspump.dll      
   23-Jun-2003  07:40  2000.80.837.0   1,557,052  Dtsui.dll        
   23-Jun-2003  07:40  2000.80.837.0     639,552  Dtswiz.dll       
   23-Apr-2003  11:51                    747,927  Instdist.sql
   02-May-2003  10:56                      1,581  Inst_repl_hotfix.sql
   07-Feb-2003  15:40  2000.80.765.0      90,692  Msgprox.dll      
   31-Mar-2003  11:07                      1,873  Odsole.sql
   04-Apr-2003  10:46  2000.80.800.0      62,024  Odsole70.dll     
   07-May-2003  05:41  2000.80.819.0      25,144  Opends60.dll     
   02-Apr-2003  06:48  2000.80.796.0      57,904  Osql.exe         
   02-Apr-2003  08:15  2000.80.797.0     279,104  Pfutil80.dll     
   04-Aug-2003  03:17                    550,780  Procsyst.sql
   22-May-2003  07:57                     19,195  Qfe469571.sql
   11-Jul-2003  02:04                  1,084,147  Replmerg.sql
   04-Apr-2003  06:53  2000.80.798.0     221,768  Replprov.dll     
   07-Feb-2003  15:40  2000.80.765.0     307,784  Replrec.dll      
   13-Aug-2003  01:28                  1,086,797  Replsys.sql
   13-Aug-2003  01:28                    986,603  Repltran.sql
   29-Jul-2003  05:13  2000.80.819.0     492,096  Semobj.dll       
   31-May-2003  03:27  2000.80.818.0     172,032  Semobj.rll
   05-Aug-2003  06:06                    127,884  Sp3_serv_uni.sql
   31-May-2003  10:01  2000.80.818.0   4,215,360  Sqldmo.dll       
   07-Apr-2003  02:44                     25,172  Sqldumper.exe    
   19-Mar-2003  03:20  2000.80.789.0      28,672  Sqlevn70.rll
   01-Jul-2003  09:18  2000.80.834.0     180,736  Sqlmap70.dll     
   07-Feb-2003  15:40  2000.80.765.0      57,920  Sqlrepss.dll     
   26-Aug-2003  05:16  2000.80.854.0   7,598,161  Sqlservr.exe     
   25-Jul-2003  06:44  2000.80.845.0     590,396  Sqlsort.dll      
   07-Feb-2003  15:40  2000.80.765.0      45,644  Sqlvdi.dll       
   24-Jun-2003  10:01  2000.80.818.0      33,340  Ssmslpcn.dll     
   31-May-2003  10:01  2000.80.818.0      82,492  Ssnetlib.dll     
   31-May-2003  10:01  2000.80.818.0      25,148  Ssnmpn70.dll     
   31-May-2003  10:01  2000.80.818.0     158,240  Svrnetcn.dll     
   31-May-2003  03:59  2000.80.818.0      76,416  Svrnetcn.exe     
   30-Apr-2003  08:52  2000.80.816.0      45,132  Ums.dll          
   01-Jul-2003  09:19  2000.80.834.0      98,816  Xpweb70.dll      


Note Because of file dependencies, the most recent hotfix or feature that contains the files may also contain additional files.


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.


Steps to Reproduce the Behavior

  1. Start SQL Query Analyzer, and then connect to a server that is running SQL Server 2000.
  2. Run the following Transact-SQL statement:

    Use Northwind
    Create Procedure [dbo].[sp_InnerRepeatedTextData]As
    Select  1
    Create Procedure [dbo].[sp_OuterRepeatedTextData]As
    Exec sp_InnerRepeatedTextData
  3. Create a new SQL Profiler trace. To do so, follow these steps:
    1. Start SQL Profiler.
    2. On the File menu, point to New, and then click Trace.
    3. In the Connect to SQL Server dialog box, type the SQL Server name and the authentication details, and then click OK.
    4. In the Trace Properties dialog box, click the Events tab.
    5. Click to select Stored Procedures in the Available event classes: list box, and then click Add.
    6. Click the Data Columns tab, click ObjectID in the Unselected data: list box, and then click Add.
    7. Click Run.
  4. In SQL Query Analyzer, run the following Transact-SQL statement on the Northwind database:

    {call sp_OuterRepeatedTextData}
  5. In SQL Profiler, on the File menu, click Stop Trace.
  6. 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.

Keywords: kbbug kbfix kbstoredproc kbtsql kbqfe kbdatabase kbsqlserv2000presp4fix kbhotfixserver KB818079