FIX: Repeated DBCC DBREINDEX Causes Stack Overflow ErrorID: Q184478
|
16706 (SQLBUG_65)
Running DBCC DBREINDEX in a loop against many tables, including some without any indexes, may cause the connection to stop responding and the following errors to be reported in the errorlog:
98/03/30 21:50:36.17 spid10 ex_testhandle: stack overflow, top=05F2D860, end=05F2D860
98/03/30 21:50:36.17 spid10 Recursive error 900 in ex_print
98/03/30 21:50:36.18 spid10 Original error was 2528, severity 10, state 1
The problem only occurs when a number of the tables have no indexes.
To work around this problem, do one of the following:
Microsoft has confirmed this to be a problem in SQL Server
version 6.5. This problem has been corrected in U.S. Service Pack 5a
for Microsoft SQL Server version 6.5. For information about
downloading and installing the latest SQL Server Service Pack, see
http://support.microsoft.com/support/sql/.
For more information, contact your primary support provider.
When the connection stops responding, it is usually still possible to
cancel it from the client.
With some combinations of indexes on the tables, this may also result in an
access violation (AV) that closes the connection.
Additional query words: sp sp5hang hung hangs terminate terminates terminated
Keywords : SSrvStProc SSrvTran_SQL kbbug6.50 kbfix6.50.SP5
Version : winnt:6.5
Platform : winnt
Issue type : kbbug
Last Reviewed: April 21, 1999