Microsoft KB Archive/825883

= FIX: The TextData column of the SP:StmtStarting event and the SP:StmtCompleted event displays the dynamic Transact-SQL statement even when the stored procedure is encrypted =

Article ID: 825883

Article Last Modified on 11/2/2007

-

APPLIES TO


 * 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

-





SYMPTOMS
When you run an encrypted stored procedure that runs a dynamic Transact-SQL statement, you may notice that the TextData column of the SP:StmtStarting event and the SP:StmtCompleted event in the SQL Profiler tool displays the dynamic Transact-SQL statement.



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 hotfix 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  18:45  2000.80.818.0      78,400  Console.exe 25-Jun-2003 01:01  2000.80.818.0      33,340  Dbmslpcn.dll 25-Apr-2003 02:12                    786,432  Distmdl.ldf 25-Apr-2003 02:12                  2,359,296  Distmdl.mdf 30-Jan-2003 01:55                        180  Drop_repl_hotfix.sql 23-Jun-2003 22:40  2000.80.837.0   1,557,052  Dtsui.dll 23-Jun-2003 22:40  2000.80.837.0     639,552  Dtswiz.dll 24-Apr-2003 02:51                    747,927  Instdist.sql 03-May-2003 01:56                      1,581  Inst_repl_hotfix.sql 08-Feb-2003 06:40  2000.80.765.0      90,692  Msgprox.dll 01-Apr-2003 02:07                      1,873  Odsole.sql 05-Apr-2003 01:46  2000.80.800.0      62,024  Odsole70.dll 07-May-2003 20:41  2000.80.819.0      25,144  Opends60.dll 07-May-2003 18:47                    132,096  Opends60.pdb 02-Apr-2003 21:48  2000.80.796.0      57,904  Osql.exe 02-Apr-2003 23:15  2000.80.797.0     279,104  Pfutil80.dll 22-May-2003 22:57                     19,195  Qfe469571.sql 12-Jun-2003 16:37                  1,083,989  Replmerg.sql 04-Apr-2003 21:53  2000.80.798.0     221,768  Replprov.dll 08-Feb-2003 06:40  2000.80.765.0     307,784  Replrec.dll 05-May-2003 00:05                  1,085,874  Replsys.sql 01-Jun-2003 01:01  2000.80.818.0     492,096  Semobj.dll 31-May-2003 18:27  2000.80.818.0     172,032  Semobj.rll 29-May-2003 00:29                    115,944  Sp3_serv_uni.sql 01-Jun-2003 01:01  2000.80.818.0   4,215,360  Sqldmo.dll 07-Apr-2003 17:44                     25,172  Sqldumper.exe 19-Mar-2003 18:20  2000.80.789.0      28,672  Sqlevn70.rll 02-Jul-2003 00:18  2000.80.834.0     180,736  Sqlmap70.dll 08-Feb-2003 06:40  2000.80.765.0      57,920  Sqlrepss.dll 23-Jun-2003 22:40  2000.80.837.0   7,553,105  Sqlservr.exe 23-Jun-2003 22:40                 12,747,776  Sqlservr.pdb 08-Feb-2003 06:40  2000.80.765.0      45,644  Sqlvdi.dll 25-Jun-2003 01:01  2000.80.818.0      33,340  Ssmslpcn.dll 01-Jun-2003 01:01  2000.80.818.0      82,492  Ssnetlib.dll 01-Jun-2003 01:01  2000.80.818.0      25,148  Ssnmpn70.dll 01-Jun-2003 01:01  2000.80.818.0     158,240  Svrnetcn.dll 31-May-2003 18:59  2000.80.818.0      76,416  Svrnetcn.exe 30-Apr-2003 23:52  2000.80.816.0      45,132  Ums.dll 30-Apr-2003 23:52                    132,096  Ums.pdb 02-Jul-2003 00:19  2000.80.834.0      98,816  Xpweb70.dll

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



STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the &quot;Applies to&quot; section of this article.This problem was first corrected in Microsoft SQL Server 2000 Service Pack 4.



Steps to reproduce the behavior
 Start the SQL Query Analyzer, and then connect to the computer that is running Microsoft SQL Server.  Run the following Transact-SQL statement to create the sp_MytestencryptionWithExec and the sp_MytestencryptionNoExec stored procedures: use northwind go drop proc sp_MytestencryptionWithExec go CREATE PROCEDURE [dbo].[sp_MytestencryptionWithExec] WITH ENCRYPTION AS DECLARE @MySQL varchar(100) BEGIN -- SET @MySQL = 'select @@version' -- EXEC(@MySql) EXEC('select @@version') END GO drop proc sp_MytestencryptionNoExec go CREATE PROCEDURE [dbo].[sp_MytestencryptionNoExec] WITH ENCRYPTION AS DECLARE @MySQL varchar(100) BEGIN select @@version END GO Note The sp_MytestencryptionWithExec stored procedure has a dynamic Transact-SQL statement. The sp_MytestencryptionNoExec stored procedure does not have any dynamic Transact-SQL statement.  Start SQL Profiler to capture the SP:StmtStarting event and the SP:StmtCompleted event. To do this, follow these steps:  Start SQL Profiler. On the File menu, point to New, and then click Trace.</li> In the Connect to SQL Server dialog box, provide the authentication information to connect to the computer that is running SQL Server, and then click OK.</li> In the Trace Properties dialog box, click the Events tab.</li> In the Available event classes list, expand Stored Procedures.</li> Under Stored Procedures, expand SP:StmtCompleted, and then click Add. Similarly add the SP:StmtStarting event.</li> Click Run.</li></ol> </li>  Run the following Transact-SQL statement in the Query Analyzer: Use northwind go Exec sp_MytestencryptionWithExec go Exec sp_MytestencryptionNoExec Go </li> In SQL Profiler, click Stop Trace on the File menu.

Note You may notice that the TextData column of the SP:StmtStarting and the SP:StmtCompleted events displays the dynamic Transact-SQL statement although the stored procedure sp_MytestencryptionWithExec is encrypted.</li></ol>

Keywords: kbbug kbfix kbstoredproc kbqfe kbsqlserv2000presp4fix KB825883

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.