FIX:Repeated Temp Table Creation/Access Can Cause Errs 208/267

Last reviewed: May 2, 1997
Article ID: Q149244

The information in this article applies to:
  • Microsoft SQL Server, version 6.0
BUG#: 11400 (6.00)

SYMPTOMS

When multiple (50 or more) clients repeatedly run a stored procedure that creates temporary tables and then insert and select from these temporary tables against a quad-processor SQL Server simultaneously, SQL Server can randomly generate errors #208( Invalid object name '%.*s'.) and #267(Object

'%.*s' cannot be found.).

WORKAROUND

Create a temporary table outside the stored procedure if the stored procedure is designed to be called by multiple users simultaneously and repeatedly. Only perform truncate, insert, and select commands inside the stored procedure.

STATUS

Microsoft has confirmed this to be a problem in Microsoft SQL Server version 6.0. This problem has been corrected in U.S. Service Pack 3 for Microsoft SQL Server version 6.0. For more information, contact your primary support provider.

MORE INFORMATION

These error messages are received at the client side, and can be trapped and simply handled by performing retry. This can not be reproduced on a single processor computer, and can rarely be reproduced on a dual-processor computer.


Additional query words: sql6
Keywords : kbbug6.00 kbfix6.00.sp3 kbprg kbusage SSrvStProc
Version : 6.0
Platform : WINDOWS


THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.

Last reviewed: May 2, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.