Hello, Running SCCM SP2 on Windows 2003 SP, database on a separate dbserver, SQL 2005. We recently had some issues with the database, found some errors while running CHECKDB agains the database. Here is the SQL message. Check Database Integrity Task (dbserver) Check Database integrity on Local server connection Databases: SMS_WTH Include indexes Task start: 2010-07-26T03:15:02. Task end: 2010-07-26T03:16:51. Failed:(-1073548784) Executing the query "DBCC CHECKDB WITH NO_INFOMSGS " failed with the following error: "Table error: Object ID 109347554, index ID 1, partition ID 72057594999603200, alloc unit ID 72057594907852800 (type LOB data). The off-row data node at page (1:461), slot 0, text ID 1533214720 is not referenced. ....(lots of similar errors).... CHECKDB found 0 allocation errors and 73 consistency errors in table 'sys.xml_index_nodes_654625375_32000' (object ID 109347554). CHECKDB found 0 allocation errors and 73 consistency errors in database 'SMS_WTH Through trial and error we have established that this occurs during the window of time setup for the Site Maintenance Tasks. We're going to start the process of elimination and see if we can figure out which task is causing the error, but was curious if anyone has seen errors like this in before or has any suggestions, hints, or tricks on how to patch this up. Pretty consistent that this has caused consistency errors for the last 3 weekends. Nothing much has changed with our environment, though about 4+ weeks ago did have an issue with WSUS not synchronizing with Microsoft for the updates catalog. Microsoft's solution, reinstall WSUS. Which worked at the time. Otherwise no changes that we are aware of. Any help or suggestions would be much appreciated, thank you.

Could come down to a hardware or host OS issue. You might consider migrating your database to another server, which is scary enough until you've done it the first time. Have a look at this: http://support.microsoft.com/kb/2015748 "The cause of these problems can vary from file system corruption, underlying hardware system issues, driver issues, corrupted pages in memory, or problems with the SQL Server Engine. Read through the Resolution section for more information on how to find the cause of errors that are reported."

Could come down to a hardware or host OS issue. You might consider migrating your database to another server, which is scary enough until you've done it the first time. Have a look at this: http://support.microsoft.com/kb/2015748 "The cause of these problems can vary from file system corruption, underlying hardware system issues, driver issues, corrupted pages in memory, or problems with the SQL Server Engine. Read through the Resolution section for more information on how to find the cause of errors that are reported." data integrity issues there, maybe the server is causing it, moving to another server would stop further corruption if this is the case

Hello, Running SCCM SP2 on Windows 2003 SP, database on a separate dbserver, SQL 2005. We recently had some issues with the database, found some errors while running CHECKDB agains the database. Here is the SQL message. Check Database Integrity Task (dbserver) Check Database integrity on Local server connection Databases: SMS_WTH Include indexes Task start: 2010-07-26T03:15:02. Task end: 2010-07-26T03:16:51. Failed:(-1073548784) Executing the query "DBCC CHECKDB WITH NO_INFOMSGS " failed with the following error: "Table error: Object ID 109347554, index ID 1, partition ID 72057594999603200, alloc unit ID 72057594907852800 (type LOB data). The off-row data node at page (1:461), slot 0, text ID 1533214720 is not referenced. ....(lots of similar errors).... CHECKDB found 0 allocation errors and 73 consistency errors in table 'sys.xml_index_nodes_654625375_32000' (object ID 109347554). CHECKDB found 0 allocation errors and 73 consistency errors in database 'SMS_WTH Through trial and error we have established that this occurs during the window of time setup for the Site Maintenance Tasks. We're going to start the process of elimination and see if we can figure out which task is causing the error, but was curious if anyone has seen errors like this in before or has any suggestions, hints, or tricks on how to patch this up. Pretty consistent that this has caused consistency errors for the last 3 weekends. Nothing much has changed with our environment, though about 4+ weeks ago did have an issue with WSUS not synchronizing with Microsoft for the updates catalog. Microsoft's solution, reinstall WSUS. Which worked at the time. Otherwise no changes that we are aware of. Any help or suggestions would be much appreciated, thank you. I wouldn't recommend digging around in the database too much, and unless there is a hotfix for SQL server or ConfigMgr that I don't know about that fixes this, then a server move might just be putting off a big fail further down the line due to the integrity of the database now. I'd suggest going to MS CSS and getting some guidance to fix this.