BUG: EXEC Long @string w/o Paran. Can Hang Server/Cause AV

• Microsoft SQL Server, version 6.0

SYMPTOMS

Executing a long local string variable without parantheses can hang the server with SQL Server version 6.0, or generate a thread-level handled access violation (AV) with Service Pack 2 for SQL Server version 6.0. The client connection does not terminate completely and will appear to hang even though the client process has been terminated by SQL Server.

WORKAROUND

EXEC is documented to execute the string only with parantheses. Always execute the string within parantheses.

STATUS

Microsoft has confirmed this to be a problem in Microsoft SQL Server version 6.0. We are researching this problem and will post new information here in the Microsoft Knowledge Base as it becomes available.

This problem does not occur in Microsoft SQL Server version 6.5.

MORE INFORMATION

Executing a string variable without the parantheses can hang the server. It generates a "stored procedure %s not found" message if the string is < 128 characters; if the string >= 128 characters, it generates an Access Violation and hangs the server with the released version of SQL Server 6.0.

With the version 6.0 Service Pack 2 installed, it still generates the AV and hangs the client connection, but does not terminate the server.

Microsoft SQL Server version 6.5 generates error 8128 for this condition:

   Msg 8128, Level 16, State 1:
   Object identifier '%s' is longer than 124 bytes.