Microsoft KB Archive/252865

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


FIX: Replay of Prepared Cursor Statements May Generate Error 16902

Article ID: 252865

Article Last Modified on 3/14/2006



APPLIES TO

  • Microsoft SQL Server 7.0 Standard Edition



This article was previously published under Q252865

BUG #: 54703 (SQLBUG_70)

SYMPTOMS

When attempting to replay a trace captured with SQL Profiler that contains prepared cursor statements (sp_cursorprepare), the following error may occur:

Server: Msg 16902, Level 16, State 21, Line 0
sp_cursorprepare: The value of parameter 'paramdef' is invalid.

This error occurs when the query is submitted as a parameterized query, but no parameter markers are actually supplied, resulting in the second parameter value being NULL.

STATUS

Microsoft has confirmed this to be a problem in SQL Server 7.0. This problem has been corrected in U.S. Service Pack 2 for Microsoft SQL Server 7.0. For more information, click the following article number to view the article in the Microsoft Knowledge Base:

254561 INF: How to Obtain Service Pack 2 for Microsoft SQL Server 7.0 and Microsoft Data Engine (MSDE) 1.0


For more information, contact your primary support provider.

MORE INFORMATION

Beginning in SQL Server 7.0 Service Pack 2, SQL Server accepts NULL as a valid second parameter to sp_cursorprepare and does not generate an error in this situation.


Additional query words: sqltrace replay cursors prepare

Keywords: kbbug kbfix KB252865