SQL Server Performance Forum – Threads Archive
Rebuild of database falls overHi all, One of our database crashed last night while rebuilding the indexes in a scheduled job.
The exact error was : [Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 169: [Microsoft][ODBC SQL Server Driver][SQL Server]A column has been specified more than once in the order by list. Columns in the order by list must be unique.
[Microsoft][ODBC SQL Server Driver][SQL Server]SqlDumpExceptionHandler: Process 58 generated fatal exception c0000005 EXCEPTION_ACCESS_VIOLATION. SQL Server is terminating this process. It looks like one of the indexes has the same name as one of the field names in the table, after some searching on groups it would appear this is the problem, what I don’t understand though is why this never happened before, I’m not sure if the index was one added by the index tuning wizard or not but either way it’s not a very good index name. Does anyone know anything more about this, I’m abit on edge about it because like I said it’s never happened before so I don’t feel 100% confident that this is the only problem. Cheers
Shaun World Domination Through Superior Software
With regard to the error message can you execute DBREINDEX for that table and see the results.
Also this could be issue with executing parallel operations like backup statements while DBCC is running. BTW, what is the level of service pack and version? _________
The index may be created by the CREATE AUTOSTATISTICS functionality of the database. But the chances of index name being same as column name is remote. Please follow the previous post made by Satya. Gaurav
Man thrives, oddly enough, only in the presence of a challenging environment- L. Ron Hubbard
Ok, <br /><br />Version : <br />Microsoft SQL Server 2000 – 8.00.760 (Intel X86) <br />Dec 17 2002 14:22:05 <br />Copyright (c) 1988-2003 Microsoft Corporation<br />Standard Edition on Windows NT 5.2 (Build 3790: )<br /><br />Product level <img src=’/community/emoticons/emotion-7.gif’ alt=’:S’ />P3<br /><br />Satya, I ran DBCC REINDEX against the table and execution completed just fine even though the index is the same name as one of the fields which makes me think there is more going on. Is it possible <br /><br />Cheers<br />Shaun<br /><br /><br /><br />World Domination Through Superior Software