FIX: Auto-Start Stored Procedure w/ WAITFOR Causes 100% CPU Use

Last reviewed: June 27, 1997
Article ID: Q166337

The information in this article applies to:

Microsoft SQL Server, versions 6.5

BUG #: 16379 (WINDOWS: 6.5)

SYMPTOMS

The SQL Server service starts up and the % Total Processor Time Performance Monitor counter for the System object rapidly increases to 100 percent. The system appears to be very slow.

CAUSE

The auto-start stored procedure contains a WAITFOR statement.

WORKAROUND

To work around this problem, avoid having a WAITFOR statement in a startup stored procedure. Run the stored procedure using a query tool instead. Unmark the procedure as a startup procedure by doing the following:

Start up SQL Server with the -f option to skip autoexec stored procedures and run in single-user mode.
Open up a query window and run sp_unmakestartup <procedurename>.

STATUS

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

Keywords : kbusage SSrvGen SSrvStProc kbbug6.50
Version : 6.5
Platform : WINDOWS
Issue type : kbbug
Resolution Type : kbfix

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: June 27, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.