Microsoft KB Archive/281590

= BUG: Profiler Truncates RPC Procedure Name At 30 Characters =

Article ID: 281590

Article Last Modified on 10/16/2002

-

APPLIES TO


 * Microsoft SQL Server 7.0 Standard Edition

-



This article was previously published under Q281590



BUG #: 101023 (SQLBUG_70)



SYMPTOMS
When you use SQL Server Profiler to monitor RPC:Starting or RPC:Completed events, if the name of the stored procedure that is being called is longer than 30 characters in length, SQL Profiler truncates the name at 30 characters. If the procedure call is qualified by an object owner or database name, each of those component names are also truncated at 30 characters if they exceed 30 characters in length.

The full procedure name is correctly received by SQL Server and used in running the procedure. The problem is limited to the incorrect capture and display of this information by SQL Profiler.



CAUSE
When generating the events, SQL Profiler uses deprecated Open Data Services (ODS) APIs that truncate the database name, object owner, and procedure name at 30 characters. Thirty characters was the maximum length for an identifier in prior versions of SQL Server.



WORKAROUND
You can determine the full procedure name by capturing the SP:Starting or SP:Completed events. The Text column has the full name of the stored procedure, the Database ID column has the database name, and the Object ID column has the object ID. These events are generated inside the server and use a different method of obtaining the procedure name, which is not subject to the 30 character limit.



STATUS
Microsoft has confirmed this to be a problem in SQL Server 7.0.

Additional query words: srv_rpcname sqltrace RPC

Keywords: kbbug kbpending KB281590

-

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

© Microsoft Corporation. All rights reserved.