InstantForum.NET v2.9.0SQLServerCentralhttp://www.sqlservercentral.com/Forums/notifications@sqlservercentral.comWed, 19 Jun 2013 19:33:57 GMT20http://www.sqlservercentral.com/Forums/Topic1454158-265-1.aspxI have a 2tb database with one table that has apparently been corrupted (torn page). Since we only run the DBCC Checkdb once a week (no time for daily on this large a database). The DBCC returns the following error - I am leaving out all the clean messages as its just noise: At the top of DBCC report:Msg 8909, Level 16, State 1, Line 1Table error: Object ID 0, index ID -1, partition ID 0, alloc unit ID 0 (type Unknown), page ID (1:14060424) contains an incorrect page ID in its page header. The PageId in the page header = (0:0).Msg 8909, Level 16, State 1, Line 1Table error: Object ID 0, index ID -1, partition ID 0, alloc unit ID 0 (type Unknown), page ID (1:14060425) contains an incorrect page ID in its page header. The PageId in the page header = (0:0).CHECKDB found 0 allocation errors and 2 consistency errors not associated with any single object.Later at the table checks:DBCC results for 'RPT_DAILY_KPI_CUST_MATERIAL_old'.Msg 8928, Level 16, State 1, Line 1Object ID 1709249144, index ID 1, partition ID 393492328611840, alloc unit ID 112017351901184 (type In-row data): Page (1:14060423) could not be processed. See other errors for details.Msg 8928, Level 16, State 1, Line 1Object ID 1709249144, index ID 1, partition ID 393492328611840, alloc unit ID 112017351901184 (type In-row data): Page (1:14060424) could not be processed. See other errors for details.Msg 8928, Level 16, State 1, Line 1Object ID 1709249144, index ID 1, partition ID 393492328611840, alloc unit ID 112017351901184 (type In-row data): Page (1:14060425) could not be processed. See other errors for details.Msg 8978, Level 16, State 1, Line 1Table error: Object ID 1709249144, index ID 1, partition ID 393492328611840, alloc unit ID 112017351901184 (type In-row data). Page (1:14060426) is missing a reference from previous page (1:14060425). Possible chain linkage problem.Msg 8978, Level 16, State 1, Line 1Table error: Object ID 1709249144, index ID 1, partition ID 393492328611840, alloc unit ID 112017351901184 (type In-row data). Page (4:15685472) is missing a reference from previous page (1:14060423). Possible chain linkage problem.Msg 8939, Level 16, State 98, Line 1Table error: Object ID 1709249144, index ID 1, partition ID 393492328611840, alloc unit ID 393492328611840 (type In-row data), page (1:14060423). Test (IS_OFF (BUF_IOERR, pBUF->bstat)) failed. Values are 12716041 and -1.Msg 8976, Level 16, State 1, Line 1Table error: Object ID 1709249144, index ID 1, partition ID 393492328611840, alloc unit ID 393492328611840 (type In-row data). Page (1:14060423) was not seen in the scan although its parent (4:15685688) and previous (1:14060422) refer to it. Check any previous errors.Msg 8976, Level 16, State 1, Line 1Table error: Object ID 1709249144, index ID 1, partition ID 393492328611840, alloc unit ID 393492328611840 (type In-row data). Page (1:14060424) was not seen in the scan although its parent (4:15685688) and previous (4:15685511) refer to it. Check any previous errors.Msg 8980, Level 16, State 1, Line 1Table error: Object ID 1709249144, index ID 1, partition ID 393492328611840, alloc unit ID 393492328611840 (type In-row data). Index node page (4:15685688), slot 51 refers to child page (1:14060425) and previous child (1:14060424), but they were not encountered.There are 121254588 rows in 1443509 pages for object "RPT_DAILY_KPI_CUST_MATERIAL_old".CHECKDB found 0 allocation errors and 9 consistency errors in table 'RPT_DAILY_KPI_CUST_MATERIAL_old' (object ID 1709249144).This table is not in use. We confirmed it by renaming it to _old and only when it is read by support staff do any errors pop up, The table is not being updated. The Instance is 64 bit SQL 2008 R2 Sp1. Can we simply drop this table - or do we risk the database going suspect by doing that? Our other alternative is to take an outage and run a DBCC repair. The users do not want that, but they also would not appreciate a suspect database.Fri, 17 May 2013 12:12:23 GMTDimbulbzhttp://www.sqlservercentral.com/Forums/Topic949537-265-1.aspxWe have a database that was put in 'suspect' mode, it is now in 'emergency' mode; using DBCC CHECKDB the problem table was identified.I tried using DBCC CHECKTABLE ( 'MyTable', REPAIR_ALLOW_DATA_LOSS ) WITH ALL_ERRORMSGS but it was not allowedI've had messages that it needs to be in single user mode, which I then altered the database to single_user mode but since it is still in emergency mode it ignores the single user mode.I cannot drop or truncate the table -- it will not let me drop the primary key constraint and clustered index to rebuild that way either.Does anyone know any way to get around this? I hate to have to rebuild the whole database just because of one bad table.Thank you in advance for your assistance.Thu, 08 Jul 2010 12:52:26 GMTEllen-477471http://www.sqlservercentral.com/Forums/Topic1448738-265-1.aspxHi, Pls i'm having the error 'ERROR 823: I/0 error (torn page) detected during read at the offset 0x00000000182e000 in file D:\program files\microsoft\SQL server\MSSQL\data\msdbdata.mdf' when i when i want to view jobs. Before now, i notice my jobs weren't running thing i notice my msdb database was flagged as suspect. I usually run the below script when i get any of my databases is flagged as suspect.#### For database flagged as suspect and reduce log size#####EXEC sp_configure 'allow updates', 1RECONFIGURE WITH OVERRIDEGOBEGIN TRANUPDATE master..sysdatabasesSET status = status | 32768WHERE name = '<Your Database Name Goes Here>'IF @@ROWCOUNT = 1BEGINCOMMIT TRANRAISERROR('emergency mode set', 0, 1)ENDELSEBEGINROLLBACKRAISERROR('unable to set emergency mode', 16, 1)ENDGOEXEC sp_configure 'allow updates', 0RECONFIGURE WITH OVERRIDEGO--------------------------------------------------------------------DBCC REBUILD_LOG('<Your Database Name Goes Here>','C:\filePath\filename.LDF')ALTER DATABASE <Your Database Name Goes Here> SET MULTI_USERGOAfter running this my msdb database was no longer flagged as suspect but on trying to start my jobs again, i want able to view them with the 'torn page' error displaying.Pls note that i don't have a backup of my msdb database. This is what i have tried so far as suggested by other people.I have ran sqlservr -c -T 3608, moved/renamed the msdbdata.mdf and msdblog.ldf files, run instmsdb to recreate the msdb database. and restarted the server without trace 3608.GilaMonster: this is the result of 'DBCC CHECKDB (<Database Name>) WITH NO_INFOMSGS, ALL_ERRORMSGS'Server: Msg 7995, Level 16, State 1, Line 1Database 'Msdb' consistency errors in sysobjects, sysindexes, syscolumns, or systypes prevent further CHECKDB processing.Thu, 02 May 2013 03:41:23 GMTchristy.umorenhttp://www.sqlservercentral.com/Forums/Topic406081-265-1.aspxIn our server suddenly we are getting this problem and we couldnt solve this ERROR 823: I/0 error (torn page) detected during read at the offset 0x00000000182e000 in file D:\program files\microsoft\SQL server\MSSQL\data\msdbdata.mdfthanks in advancecheersv.kanagaraj kumarWed, 03 Oct 2007 03:01:39 GMTkanagarajkumarvhttp://www.sqlservercentral.com/Forums/Topic1420561-265-1.aspx[b]SCENARIO 1[/b] Hi, i'm getting the error msg 601: Could not continue scan with NOLOCK due to Data movement‎ - from a job scheduled to run. This is how the error comes about;I have two sql servers, (both 2000) lets say A and B. server A is my production server while server B is my standby server. I scheduled a database and log backup on server A in which the destination for the backup files are on server B where its to be recovery (sort of like the log shipping we have in sql 2008).Now I have two jobs( say job1 and job2) scheduled on server A. Job1 is a procedure which is to perform a full backup and then a log backups to server B. Job2 is a procedure that is to recovery(restore) the backups from server B onto the standby server B in the order they were backed up.Pls note that job2 will also fail if job1 fail because there are no backup files for job2 to recovery.One day i noticed job1 had been failing causing job2 to also fail. On checking the job history and log files i saw that full backup will complete but log backup will fail with the above error causing the the job to fail...I have no NOLOCK statement in my procedureI have upgraded my service pack to SP4 because i was told its a service pack issue but still nothingI have ran DBCCC CHECKDB and no error was displayed[b]SCENARIO 2[/b] This scenario is exactly like Scenario 1, the only difference is that i get the above error when recovery of the 'log files' is being performed on server B (that means full database recovery is successful but log recovery fails) . So in the case, job1 is fine but job2 is failing.Pls can anyone help??!Fri, 15 Feb 2013 07:58:21 GMTchristy.umorenhttp://www.sqlservercentral.com/Forums/Topic1417174-265-1.aspxA company pulled me in and wanted me to help with their sql server after a raid failure.They retrieved the data off the drive and re installed on a virtual server.They hired another company to install sql 7 from scratch and import the data.The server hosts their website which ties to the SQL server and 2 programs which store data on the sql server.Now is the part i am confused on and am sure you guys will know it.I think everything is setup to work through odbc connections. (dsn)The website is showing this errorMicrosoft OLE DB Provider for ODBC Drivers error '80040e4d'[Microsoft][ODBC SQL Server Driver][SQL Server]Login failed for user 'bhPress_user'./connect.asp, line 15On the server there are system dsn's and file dsn's in the odbc list.Since the company installed SQL 7 from scratch i believe sql lost all the login information? Am I on the right path?How do I go about setting up all these connections back up?All help is greatly appreciated and thanks for your time guys.- JarrodThu, 07 Feb 2013 09:17:22 GMTnetadmin 17163http://www.sqlservercentral.com/Forums/Topic1416376-265-1.aspxHi,Can someone please clarify my below doubtI have a database on which 2 tables are corrupted, I dont have good backup to restore.This is kind of page level corruption, so if i do an export of my database to some other new database, will my new be a good and healthy db?Thanks,Dev.Wed, 06 Feb 2013 03:38:19 GMTdevanandiiwayhttp://www.sqlservercentral.com/Forums/Topic1401646-265-1.aspxHi,Often am getting logical consistency error in one my production server. Recently i did DBCC with allow dataloss option, to correct the inconsistency. Now i see the below error in the database.SQL Server detected a logical consistency-based I/O error: incorrect pageid (expected 1:6743211; actual 0:0). It occurred during a read of page (1:6743211) in database ID 11 at offset 0x00000cdc956000Again do I need to repair the database? Why this inconsistency is happening often? Thanks,Dev.Tue, 01 Jan 2013 21:38:10 GMTdevanandiiwayhttp://www.sqlservercentral.com/Forums/Topic1366416-265-1.aspxHow to Recover Deleted rows from sql 2000 Database using with some period parameter eg: from 01/01/2012 - 20/05/2012 Display all deleted records on this period.Mon, 01 Oct 2012 03:26:13 GMTkuriakoserobinhttp://www.sqlservercentral.com/Forums/Topic1378680-265-1.aspxHi,In one of my production server, am seeing many MDMP files created on Oct 24. I just refreshed my mind and on Oct 23 we had a server refresh on this server. After the refresh, the database was accessible however our applications was unable to access few objects. They were getting the below error.Alarm Details: MSSQLSERVER: [8646] Unable to find index entry in index ID 0, of table 906486308, in database 'witness'. The indicated index is corrupt or there is a problem with the current update plan. Run DBCC CHECKDB or DBCC CHECKTABLE. If the problem persists, contact product support.when i perfromed DBCC i got the below error.Msg 8914, Level 16, State 1, Line 1Incorrect PFS free space information for page (1:29593) in object ID 906486308, index ID 0, partition ID 59407486681088, alloc unit ID 59407486681088 (type In-row data). Expected value 100_PCT_FULL, actual value 95_PCT_FULL.since the object moved to some other allocation unit we restored the database. After 24th oct i couldnt see any MDMP files. And on oct 28th DBCC check db had run and it gave 54 consistency errors on MSDB database.When i checked the object id it is related to backupmedia, backup file, backupmediafamily on MSDB. Pasting the sample DBCC check result DBCC results for 'backupmediaset'.Msg 8978, Level 16, State 1, Line 1Table error: Object ID 1858105660, index ID 1, partition ID 72057594042777600, alloc unit ID 72057594047168512 (type In-row data). Page (1:1624) is missing a reference from previous page (1:1665). Possible chain linkage problem.There are 1668 rows in 24 pages for object "backupmediaset".CHECKDB found 0 allocation errors and 1 consistency errors in table 'backupmediaset' (object ID 1858105660).DBCC results for 'sysmail_log'.There are 22 rows in 1 pages for object "sysmail_log".DBCC results for 'backupmediafamily'.Msg 8978, Level 16, State 1, Line 1Table error: Object ID 1890105774, index ID 1, partition ID 72057594042908672, alloc unit ID 72057594047299584 (type In-row data). Page (1:1587) is missing a reference from previous page (1:1586). Possible chain linkage problem.There are 1637 rows in 33 pages for object "backupmediafamily".CHECKDB found 0 allocation errors and 1 consistency errors in table 'backupmediafamily' (object ID 1890105774).DBCC results for 'sysdtspackages90'.There are 2 rows in 1 pages for object "sysdtspackages90".DBCC results for 'backupset'.Msg 8925, Level 16, State 1, Line 1Table error: Cross object linkage: Page (1:662), slot 41, in object ID 1954106002, index ID 1, partition ID 72057594043039744, alloc unit ID 72057594047430656 (type In-row data), refers to page (1:1604), slot 0, in object ID 2050106344, index ID 1, partition ID 72057594043236352, alloc unit ID 72057594047627264 (type In-row data)Am very much worried of my Prod database. Kindly assist me. Thanks in Advance. Thanks,Dev. (+91)89398-14749Tue, 30 Oct 2012 04:55:57 GMTdevanandiiwayhttp://www.sqlservercentral.com/Forums/Topic1351818-265-1.aspxhello, this is on sql server 2005.it is for a new client. this may be the first time dbcc checkdb was ran on the databases so the error may have been there for some time.executed the following:DBCC CHECKDB (ExampleProd3x) WITH NO_INFOMSGS, ALL_ERRORMSGSMsg 2576, Level 16, State 1, Line 1The Index Allocation Map (IAM) page (0:0) is pointed to by the previous pointer of IAM page (1:3878384) in object ID 1591012749, index ID 22, partition ID 72057594103005184, alloc unit ID 72057594108379136 (type In-row data), but it was not detected in the scan.CHECKDB found 1 allocation errors and 0 consistency errors in table 'EXAMPLEUsers' (object ID 1591012749).CHECKDB found 1 allocation errors and 0 consistency errors in database 'ExampleProd3x'.repair_allow_data_loss is the minimum repair level for the errors found by DBCC CHECKDB (ExampleProd3x).i can select from the table (select *, and select with where clause) just fine.from: DBCC PAGE('ExampleProd3x', 1, 913345, 3)i get: Metadata: IndexId = 1we've done the repair:dbcc checkdb ('ExampleProd3x', REPAIR_ALLOW_DATA_LOSS)DBCC results for 'EXAMPLEUsers'.Repair: IAM chain for object ID 1591012749, index ID 22, partition ID 72057594103005184, alloc unit ID 72057594108379136 (type In-row data), has been truncated before page (1:3878384) and will be rebuilt.Msg 2576, Level 16, State 1, Line 1The Index Allocation Map (IAM) page (0:0) is pointed to by the previous pointer of IAM page (1:3878384) in object ID 1591012749, index ID 22, partition ID 72057594103005184, alloc unit ID 72057594108379136 (type In-row data), but it was not detected in the scan.The error has been repaired.There are 29537 rows in 697 pages for object "EXAMPLEUsers".CHECKDB found 1 allocation errors and 0 consistency errors in table 'EXAMPLEUsers' (object ID 1591012749).CHECKDB fixed 1 allocation errors and 0 consistency errors in table 'EXAMPLEUsers' (object ID 1591012749).This says the error has been repaired.but when we run dbcc checkdb again it still fails on the same table/object:CHECKDB found 1 allocation errors and 0 consistency errors in table 'EXAMPLEUsers' (object ID 1591012749).What other methods are there to resolve the allocation error?the table only has 30k rows, though there are some dependencies, if it's an option to rebuild this or the indexes.thank youWed, 29 Aug 2012 12:15:29 GMTsierra4http://www.sqlservercentral.com/Forums/Topic1336517-265-1.aspxwhen i running this...DBCC CHECKDB('PMSdb') WITH NO_INFOMSGSServer: Msg 8966, Level 16, State 1, Line 1Could not read and latch page (1:399112) with latch type SH. sysindexes failed.and DBCC CHECKTABLE ('sysindexes') WITH NO_INFOMSGSServer: Msg 8966, Level 16, State 1, Line 1Could not read and latch page (1:399112) with latch type SH. sysindexes failed.Server: Msg 8909, Level 16, State 1, Line 1Table error: Object ID 1735289202, index ID 26996, page ID (1:399112). The PageId in the page header = (8224:538976288).CHECKTABLE found 0 allocation errors and 1 consistency errors in table '(Object ID 1735289202)' (object ID 1735289202).repair_allow_data_loss is the minimum repair level for the errors found by DBCC CHECKTABLE (PMSdb.dbo.sysindexes ).what should i do after this? lets discuss it...Fri, 27 Jul 2012 07:51:42 GMTslizamhttp://www.sqlservercentral.com/Forums/Topic1347354-265-1.aspxWe have a server running SQL 7 and one of the raid drives failed. In switching the drive, it corrupted the OS and we had to reinstall. Fortunatelyl all the files were intact including the SQL table files. I had to reinstall SQL and use the SP_ATTACH_DB command and was able to access them. My problem is I don't have any of the DTS packages or the USER ID's, etc. under SECURITY. I tried moving all the tables under DATA to the new server location and it wouldn't start. So I've got all the data but none of the security or DTS packages. Is there anyway to retrieve that information from the MASTER or MSDB tables?I have a fairly recent backup but one of the databases wasn't in it so I'm trying to determine my easiest most accurate path. I have all the DB's attached, but without the security or DTS, I"m kinda hosed ...Mon, 20 Aug 2012 11:23:37 GMTLen Morris-88237http://www.sqlservercentral.com/Forums/Topic1346338-265-1.aspxHelp needed to rectify the error below on SQL 2K SP4, any suggestion is welcome (DBCC REPAIR ALLOW DATA LOSS couldn't fix it, all the backup contain this error). The backup can be restore into SQL 2K but not on SQL 2008. Thanks in advance for all the suggestion and help.DBCC CHECKDB WITH NO_INFOMSGSreturn the following errorServer: Msg 8929, Level 16, State 1, Line 1Object ID 2: Errors found in text ID 1136355901440 owned by data record identified by RID = (1:118525:4) id = 1729349871 and indid = 10.Server: Msg 8929, Level 16, State 1, Line 1Object ID 2: Errors found in text ID 1136355966976 owned by data record identified by RID = (1:118525:5) id = 1729349871 and indid = 11.Server: Msg 8929, Level 16, State 1, Line 1Object ID 2: Errors found in text ID 1136356032512 owned by data record identified by RID = (1:118525:6) id = 1729349871 and indid = 12.Server: Msg 8965, Level 16, State 1, Line 1Table error: Object ID 2. The text, ntext, or image node at page (1:2580035), slot 2, text ID 1136355901440 is referenced by page (1:118525), slot 4, but was not seen in the scan.Server: Msg 8965, Level 16, State 1, Line 1Table error: Object ID 2. The text, ntext, or image node at page (1:2580035), slot 4, text ID 1136355966976 is referenced by page (1:118525), slot 5, but was not seen in the scan.Server: Msg 8965, Level 16, State 1, Line 1Table error: Object ID 2. The text, ntext, or image node at page (1:2580035), slot 9, text ID 1136356032512 is referenced by page (1:118525), slot 6, but was not seen in the scan.Server: Msg 8964, Level 16, State 1, Line 1Table error: Object ID 2. The text, ntext, or image node at page (1:3477818), slot 0, text ID 1136355901440 is not referenced.CHECKDB found 0 allocation errors and 7 consistency errors in table 'sysindexes' (object ID 2).CHECKDB found 0 allocation errors and 7 consistency errors in database 'SUN522AU'.Thu, 16 Aug 2012 23:57:02 GMTsurianto_agushttp://www.sqlservercentral.com/Forums/Topic1339328-265-1.aspxGood morning,It is a bit of a long story but i'm recently hired and have had a sql server that I did not know existed dropped into my lap because a third party software that uses the db would not let the user log in. I've learned that the reason is because one of the dbs is in suspect mode.A little more background, It was installed by an outside agency that has neither the knowledge or the desire to repair it at all, their solution is to start from scratch. Prior to this incident, the ties with this company had been severed because of this type of workmanship. There have been no backups made in over a year because the tape drive attached didn't even have a driver installed so i'm hoping someone can help me out. I must say that I was brought on board for networking and as/400 administration and know little about sql, so please forgive what is going to be obvious ignorance. The db is small and is running a security system for mag locks, door nodes, etc. The door nodes and locks operate on their last standing order, so right now the db being unavailable hasn't caused any problems for day to day use, which has afforded me time to lurk these forums and gain a little knowledge on the subject.This is the error the user received when trying to start up their security program:[code="plain"]ODBC;Driver={SQL Server};DATABASE=multiMAX;SERVER=HP12265206811;Trusted_Connection=Yes;: Cannot open database requested in login 'multiMAX'. Login fails. State:37000,Native:4060,Origin:[Microsoft][ODBC SQL Server Driver][SQL Server] [/code]From lurking I've learned that the first thing that always seems to be asked is what is in the error log. Well the error log is likely no help because the user restarted a bunch of times, so this is all that is in the 8 or so SQL error logs (multiMAX is the db in question):[code="plain"]2012-08-01 14:53:44.74 server Microsoft SQL Server 2000 - 8.00.2039 (Intel X86) May 3 2005 23:18:38 Copyright (c) 1988-2003 Microsoft Corporation Desktop Engine on Windows NT 6.1 (Build 7601: Service Pack 1)2012-08-01 14:53:44.74 server Copyright (C) 1988-2002 Microsoft Corporation.2012-08-01 14:53:44.74 server All rights reserved.2012-08-01 14:53:44.74 server Server Process ID is 1724.2012-08-01 14:53:44.74 server Logging SQL Server messages in file 'C:\Program Files (x86)\Microsoft SQL Server\MSSQL\LOG\ERRORLOG'.2012-08-01 14:53:44.83 server SQL Server is starting at priority class 'normal'(8 CPUs detected).2012-08-01 14:53:46.06 server SQL Server configured for thread mode processing.2012-08-01 14:53:46.06 server Using dynamic lock allocation. [500] Lock Blocks, [1000] Lock Owner Blocks.2012-08-01 14:53:46.15 spid3 Starting up database 'master'.2012-08-01 14:53:46.82 spid5 Starting up database 'model'.2012-08-01 14:53:46.82 server Using 'SSNETLIB.DLL' version '8.0.2039'.2012-08-01 14:53:46.82 spid3 Server name is 'HP12265206811'.2012-08-01 14:53:46.82 spid3 Skipping startup of clean database id 42012-08-01 14:53:46.82 spid3 Skipping startup of clean database id 62012-08-01 14:53:46.82 spid3 Skipping startup of clean database id 72012-08-01 14:53:46.82 spid3 Skipping startup of clean database id 82012-08-01 14:53:46.82 spid3 Skipping startup of clean database id 92012-08-01 14:53:46.82 spid3 Skipping startup of clean database id 102012-08-01 14:53:46.82 spid3 Skipping startup of clean database id 112012-08-01 14:53:46.82 spid3 Skipping startup of clean database id 122012-08-01 14:53:46.82 spid3 Starting up database 'multiMAX'.2012-08-01 14:53:46.84 server SQL server listening on 192.168.100.21: 1433.2012-08-01 14:53:46.84 server SQL server listening on 127.0.0.1: 1433.2012-08-01 14:53:46.90 spid5 Clearing tempdb database.2012-08-01 14:53:46.99 spid3 Bypassing recovery for database 'multiMAX' because it is marked SUSPECT.2012-08-01 14:53:47.10 server SQL server listening on TCP, Shared Memory, Named Pipes.2012-08-01 14:53:47.10 server SQL Server is ready for client connections2012-08-01 14:53:47.24 spid5 Starting up database 'tempdb'.2012-08-01 14:53:47.28 spid3 Recovery complete.2012-08-01 14:53:47.28 spid3 SQL global counter collection task is created.2012-08-01 14:53:47.28 spid3 Launched startup procedure 'xp_g4StartServices'2012-08-01 14:53:47.44 spid51 Using 'xplog70.dll' version '2000.80.2039' to execute extended stored procedure 'xp_cmdshell'.2012-08-01 14:53:48.98 logon Login succeeded for user 'NT AUTHORITY\SYSTEM'. Connection: Trusted.2012-08-01 14:53:48.98 spid52 Starting up database 'msdb'.2012-08-01 14:53:49.65 spid52 Using 'xpsqlbot.dll' version '2000.80.2039' to execute extended stored procedure 'xp_qv'.2012-08-01 14:53:52.75 logon Login succeeded for user 'NT AUTHORITY\SYSTEM'. Connection: Trusted.2012-08-01 14:53:53.31 logon Login succeeded for user 'NT AUTHORITY\SYSTEM'. Connection: Trusted.2012-08-01 14:53:54.03 spid51 Using 'xpstar.dll' version '2000.80.2039' to execute extended stored procedure 'xp_regread'.2012-08-01 14:53:54.37 logon Login succeeded for user 'NT AUTHORITY\SYSTEM'. Connection: Trusted.2012-08-01 14:53:54.37 logon Login failed for user 'NT AUTHORITY\SYSTEM'.[/code]I may be wrong but I see nothing here besides a message saying the db is in suspect mode. But like I said i know little about sql someone here might see something I don't.From here I checked the event viewer and see thousands of identical entries starting on 7/21/12:[code="plain"]- System - Provider [ Name] MultimaxTxnService - EventID 106 [ Qualifiers] 0 Level 3 Task 0 Keywords 0x80000000000000 - TimeCreated [ SystemTime] 2012-07-21T01:37:46.000000000Z EventRecordID 68340 Channel Application Computer HP12265206811 Security - EventData No more threads can be created in the system. [/code]There is a plenty of free space on the drive. I'm not 100% sure this is related because mutliMAXTxn is another related db on this system that is not in suspect. But I posted this here anyways in case it helped.According to the user, on 7/31 the user was viewing an IP camera on this system in a software application that does not use this db. The application locked the computer, the user powered down and back up and that's when they received the error message about login failed.[b]Now in making this post I discovered a BACKUP folder in the sql program folder.[/b] Not sure if this is an actual usable backup or not, the last modified date of the mutliMAX.bak is 07/31/12 at 2:00am, about 6 hours before the computer locked up. Again, I know next to nothing about sql so if it is usable I don't know the first thing about restoring it.Thank you in advance for any help.Thu, 02 Aug 2012 10:03:50 GMTUsual (Suspect)http://www.sqlservercentral.com/Forums/Topic1340290-265-1.aspxPlease help me with this problem.SQL 7.0I copied both ldf and mdf file after shutting down the SQLServer because of HDD failure.SQL 7.0 server on new computer won't attach the db with following error.[Microsoft][ODBC SQL Server Driver][SQL Server] The header file for the "D:\database\dbname.ldf" is not a valid database file header. The pageAudit property is incorrect.Thanks in advance.Sun, 05 Aug 2012 13:54:50 GMTsteve.ahn71http://www.sqlservercentral.com/Forums/Topic1334173-265-1.aspxI been having this problem since I changed hosting providers. My uddeIM files were missing but the database config said it was installed. So I re-installed uddeIM manually and I get this message in the CPanel and in the website when Im about to send a message to someone I get the same error BUT in 3 lines. I have tried uninstalling uddeIM manually by removing all the folders and all the SQL tables but nothing seems to work. Any help would be deeply appreciated.Error loading component: com_uddeim, 1[IMG]http://i46.tinypic.com/1zz5k43.png[/IMG]Mon, 23 Jul 2012 19:50:16 GMTsqlcentral2http://www.sqlservercentral.com/Forums/Topic1310601-265-1.aspxI have encountered the table corruption issue on one of the server. This server (SQL Server 2000 Ent edition on windows 2000) has publication database of pull-type merge replication. One of the table (MyDB.dbo.TestTABLE) got corrupted which is NOT being replicated (not a part of publication). Bad part is we do not have the good consistent backup.Server: Msg 8928, Level 16, State 1, Line 1Object ID 245575913, index ID 0: Page (1:26457) could not be processed. See other errors for details.Server: Msg 8944, Level 16, State 1, Line 1Table error: Object ID 245575913, index ID 0, page (1:26457), row 0. Test (nVarCols && (hdr->r_tagA & VARIABLE_COLUMNS)) failed. Values are 0 and 32.Server: Msg 8976, Level 16, State 1, Line 1Table error: Object ID 245575913, index ID 1. Page (1:26457) was not seen in the scan although its parent (1:2647915) and previous (1:1778496) refer to it. Check any previous errors.Server: Msg 8978, Level 16, State 1, Line 1Table error: Object ID 245575913, index ID 1. Page (1:713577) is missing a reference from previous page (1:26457). Possible chain linkage problem.Server: Msg 8964, Level 16, State 1, Line 1Table error: Object ID 245575913. The text, ntext, or image node at page (1:602493), slot 29, text ID 1083010711552 is not referenced.DBCC results for 'TestTABLE'.There are 3527305 rows in 68075 pages for object 'TestTABLE'.CHECKTABLE found 0 allocation errors and 5 consistency errors in table 'TestTABLE' (object ID 245575913).repair_allow_data_loss is the minimum repair level for the errors found by DBCC CHECKTABLE (MyDB.dbo.TestTABLE).I have restored the database in test environment and came to know that dbcc checktable with repair_allow_data_loss is the only option to correct this problem. After repair SQL Server dropped the page (1:26457) index ID 0 ...Next step is to correct the problem in production environment. Before I touch the production environment, I would like to know the risks and mitigation of this activity.My concerns are:1. Changing the database to single_user mode which is publisher in pull-type merge replication2. Steps to be taken to disable\enable the merge replication before\after repairLet me know if you have more inputs on this.Thanks.KRNMon, 04 Jun 2012 09:54:32 GMTkrn045http://www.sqlservercentral.com/Forums/Topic1306941-265-1.aspxDear Sir,I am in great trouble, at present I have no back of the database, while i attaching database in the sql server 2000, the Sql server giving error message which was mentioned below within single quotes.'Attach database failed for Server 'M3'. (Microsoft.SqlServer.Smo)An exception occurred while executing a Transact-SQL statement or batch. I/O error (torn page) detected during read at offset 0x0000003d0f4000 in file 'D:\TEST\DS1213.mdf'.Error while redoing logged operation in database 'DS1213'. Error at log record ID (1081:4550:10).Could not open new database 'DS1213'. CREATE DATABASE is aborted. (Microsoft SQL Server, Error: 823)'how to attach the database I don't know please help me anybodyThanking YouDebasis BagSat, 26 May 2012 05:12:29 GMTdeba_20032004http://www.sqlservercentral.com/Forums/Topic425130-265-1.aspxHi,I am in a very rough situation and would like some help/advise.My server crashed and I lost everything. Server was rebuilt and I tried to restore the .BAK file from tape. Noticed that backups were not going good as well. I found one .BAK file but when I restored it is reporting to be approx. 200Kb smaller than the size reported by windows. Backupexec restored 20785192 bytes but the size of the restored file is 20983171 bytes. Anyway, when I try to restore .BAK file from enterprise manager system just sits there for hours. and when I check the file it is reporting as corrupt/incomplete.Can anyone suggest any way to get data out of this file? It is a really bad situation. I will be calling MS tomorrow but any suggestions are welcome.Thu, 22 Nov 2007 22:23:56 GMTdpremihttp://www.sqlservercentral.com/Forums/Topic1282287-265-1.aspxHi all,Over the last few weeks 3 of our secondary (log-shipped) DB's have been marked 'Suspect', requiring drop+restore. I've been advised to check the I/O and try to faultfind.What practices/native tools exist for SS2K to get started on the investigation? BTW, if the initial diagnosis involves creating non-temp tables/objects, I would rather avoid this as even making slight changes involves having to raise an RFC.Also, would you recommend checking I/O on both Primary + Secondary servers?Thu, 12 Apr 2012 05:51:27 GMTjblovesthegymhttp://www.sqlservercentral.com/Forums/Topic1273153-265-1.aspxSorry Administrator (My Data is SQL Server 2005, I post in SQL Server 7,2000 :blush:)My Data Error After periodic check.Example:[quote]Table: NHAP—————ID | DateTime |—————1 | 20/2/2012|2 | 20/3/2012|Table: NHAPCT————-ID | SL | DG————-1 | 2 | 2001 | 2 | 5002 | 20 | 4003 | 30 | 700 <– This is Error[/quote]Pic:[img]http://i95.photobucket.com/albums/l137/thtuananh/MyDataError.gif[/img]My data has more than 70 tables and 50 FK. I want to test all FK. Which method. ThanksLink to download MyData:[url]http://www.mediafire.com/?z4azgwc2jwcx1om[/url]Mon, 26 Mar 2012 21:49:22 GMTtahatranhttp://www.sqlservercentral.com/Forums/Topic1132378-265-1.aspxRunning SQL Server 2000 standard 8.0.2055 (SP 4 +) on Windows 2003 standard. Server has low use to basically no use. Database has been growing since 2004, from about 10 MB to currently 292 MB (data 270 MB, log 23 MB), however data size has grown less than 10%. Recently have had two instances of data corruption (see dbcc errors below). My theory is that ghost rows are not being deleted and somehow that causes another bug which is the corruption. I'd like to know if my theory makes sense or not. The primary activity on the server is a copy program that copies 9 tables from a SQL 2008 database to the database in question using a delete all and then insert commands. Copy program runs every night.To resolve the problem I truncated the 9 tables and then re-ran the copy program. This reduced the data KB (per sp_spaceused) from 21296 KB to 2768 KB. Index size remained roughly the same.First instance of corruption produced errors like this in the FITB_EMPLOYEE table. I did not attempt to fix, I simply restored from the previous backup....[Microsoft][ODBC SQL Server Driver][SQL Server]Table error: Object ID 0, index ID 0, page ID (1:6719). The PageId in the page header = (0:0).[Microsoft][ODBC SQL Server Driver][SQL Server]Table error: Object ID 1442104178, index ID 2. Page (1:6480) is missing references from parent (unknown) and previous (page (0:0)) nodes. Possible bad root entry in sysindexes.[Microsoft][ODBC SQL Server Driver][SQL Server]Table error: Page (1:6481) allocated to object ID 1442104178, index ID 2 was not seen. Page may be invalid or have incorrect object ID information in its header....[Microsoft][ODBC SQL Server Driver][SQL Server]CHECKDB found 0 allocation errors and 5 consistency errors not associated with any single object.[Microsoft][ODBC SQL Server Driver][SQL Server]CHECKDB found 0 allocation errors and 64 consistency errors in table 'FITB_EMPLOYEE' (object ID 1442104178).[Microsoft][ODBC SQL Server Driver][SQL Server]CHECKDB found 0 allocation errors and 69 consistency errors in database 'DOFSHR'.[Microsoft][ODBC SQL Server Driver][SQL Server]repair_allow_data_loss is the minimum repair level for the errors found by DBCC CHECKDB (DOFSHR ).This is the entire report produced the second instance of data corruption. In this case, when we re-ran DBCC Checkdb, it found no errors. There may have been a rebuild index in between.[Microsoft][ODBC SQL Server Driver][SQL Server]Table error: Object ID 1442104178, index ID 2. Page (1:369) is missing references from parent (unknown) and previous (page (0:0)) nodes. Possible bad root entry in sysindexes.[Microsoft][ODBC SQL Server Driver][SQL Server]CHECKDB found 0 allocation errors and 1 consistency errors in table 'FITB_EMPLOYEE' (object ID 1442104178).[Microsoft][ODBC SQL Server Driver][SQL Server]CHECKDB found 0 allocation errors and 1 consistency errors in database 'DOFSHR'.[Microsoft][ODBC SQL Server Driver][SQL Server] repair_rebuild is the minimum repair level for the errors found by DBCC CHECKDB (DOFSHR ).Thank you in advance for you help and comments.lMon, 27 Jun 2011 12:42:43 GMTNicole Garrishttp://www.sqlservercentral.com/Forums/Topic1234254-265-1.aspxI was at least glad to find out what I am seeing in the error messages from a great article on this site:"Damaged allocation pagesMsg 8946, Level 16, State 12, Line 1 Table error: Allocation page (1:2264640) has invalid PFS_PAGE page header values. Type is 0. Check type, alloc unit ID and page ID on the page. Msg 8998, Level 16, State 2, Line 1 Page errors on the GAM, SGAM, or PFS pages prevent allocation integrity checks in database ID 13 pages from (1:2264640) to (1:2272727)In this case, one or more of the database allocation pages are damaged. The allocation pages are used to mark which pages and extents in the database are allocated and which are free. CheckDB will not repair damage to the allocation pages, as it is extremely difficult to work out, without those pages, what extents are allocated and which are not. Dropping the allocation page is not an option as that would discard up to 4GB of data."I guess the question I have is - where do I go from here? If I export the data and create a new database, can I import the data without importing the corruption? I have been working on this for 6 days now just to get the point I have the server back to between restoring the OS and backups and then working on trying to get the data to a recoverable state. I feel certain that I can get data via export/import but I don't want to do that until I know that corruption will not be included in this transaction. Here are the error messages I get on this database:Msg 8946, Level 16, State 12, Line 2Table error: Allocation page (1:40440) has invalid PFS_PAGE page header values. Type is 0. Check type, object ID and page ID on the page.DBCC results for 'accesscontrol'.Msg 8921, Level 16, State 1, Line 1CHECKTABLE terminated. A failure was detected while collecting facts. Possibly tempdb out of space or a system table is inconsistent. Check previous errors.Msg 8998, Level 16, State 1, Line 1Page errors on the GAM, SGAM, or PFS pages do not allow CHECKALLOC to verify database ID 5 pages from (1:40440) to (1:48527). See other errors for cause.CHECKDB found 1 allocation errors and 0 consistency errors not associated with any single object.Msg 8909, Level 16, State 1, Line 1Table error: Object ID 2133655552, index ID 32557, page ID (1:40440). The PageId in the page header = (0:13246).CHECKDB found 0 allocation errors and 1 consistency errors in table '(Object ID 2133655552)' (object ID 2133655552).CHECKDB found 1 allocation errors and 1 consistency errors in database 'AccessControl'.DBCC execution completed. If DBCC printed error messages, contact your system administrator.Any help is appreciated.Wed, 11 Jan 2012 11:52:01 GMTThomGhttp://www.sqlservercentral.com/Forums/Topic1211382-265-1.aspxHello.I'm currently trying to get a instance of sharepoint up and running after a server recovery. All the files have been restored including permissions. The MSSQL$SHAREPOINT service starts and then stops straight away. The error log looks like this2011-11-23 22:07:12.15 server Microsoft SQL Server 2000 - 8.00.2055 (Intel X86) Dec 16 2008 19:46:53 Copyright (c) 1988-2003 Microsoft Corporation Desktop Engine (Windows) on Windows NT 5.2 (Build 3790: Service Pack 2)2011-11-23 22:07:12.16 server Copyright (C) 1988-2002 Microsoft Corporation.2011-11-23 22:07:12.18 server All rights reserved.2011-11-23 22:07:12.18 server Server Process ID is 7544.2011-11-23 22:07:12.18 server Logging SQL Server messages in file 'C:\Program Files\Microsoft SQL Server\MSSQL$SHAREPOINT\LOG\ERRORLOG'.2011-11-23 22:07:12.21 server SQL Server is starting at priority class 'normal'(2 CPUs detected).2011-11-23 22:07:12.37 server SQL Server configured for thread mode processing.2011-11-23 22:07:12.37 server Using dynamic lock allocation. [500] Lock Blocks, [1000] Lock Owner Blocks.2011-11-23 22:07:12.44 spid4 Starting up database 'master'.2011-11-23 22:07:12.57 spid4 1 transactions rolled back in database 'master' (1).2011-11-23 22:07:12.57 spid4 Recovery is checkpointing database 'master' (1)2011-11-23 22:07:12.69 server Using 'SSNETLIB.DLL' version '8.0.2039'.2011-11-23 22:07:12.69 spid5 Starting up database 'model'.2011-11-23 22:07:12.71 spid4 Server name is 'INTEGRITY\SHAREPOINT'.2011-11-23 22:07:12.74 spid8 Starting up database 'msdb'.2011-11-23 22:07:12.76 spid9 Starting up database 'STS_Config'.2011-11-23 22:07:12.76 server SQL server listening on Shared Memory.2011-11-23 22:07:12.76 server SQL Server is ready for client connections2011-11-23 22:07:12.76 spid10 Starting up database 'STS_INTEGRITY_1'.2011-11-23 22:07:12.98 spid8 1 transactions rolled back in database 'msdb' (4).2011-11-23 22:07:12.99 spid10 1 transactions rolled back in database 'STS_INTEGRITY_1' (6).2011-11-23 22:07:13.01 spid10 Recovery is checkpointing database 'STS_INTEGRITY_1' (6)2011-11-23 22:07:13.01 spid9 1 transactions rolled back in database 'STS_Config' (5).2011-11-23 22:07:13.02 spid5 1 transactions rolled back in database 'model' (3).2011-11-23 22:07:13.02 spid8 Recovery is checkpointing database 'msdb' (4)2011-11-23 22:07:13.02 spid5 Recovery is checkpointing database 'model' (3)2011-11-23 22:07:13.02 spid9 Recovery is checkpointing database 'STS_Config' (5)2011-11-23 22:07:13.34 spid5 Clearing tempdb database.2011-11-23 22:07:14.46 spid5 Starting up database 'tempdb'.2011-11-23 22:07:15.07 spid4 Recovery complete.2011-11-23 22:07:15.12 spid4 System database checksum file has invalid signature.I've searched around the internet and cant find any solution. I have tried restoring the files in C:\Program Files\Microsoft SQL Server\MSSQL$SHAREPOINT\Data with no luck. It is an SBS server and there are other databases running, so I don't want to restore the other folders as those DB's are starting and running. Any help or suggestions would be greatly appreciated!ThanksJames Wed, 23 Nov 2011 15:23:41 GMTj_allen_http://www.sqlservercentral.com/Forums/Topic563318-265-1.aspxI am using SQL Serer 2000 and want to know how to recover deleted records from a table / transaction log.Unfortunately one of my team member has accidentally deleted some records of an important table.Kindly suggest appropriate solution for the same.Wed, 03 Sep 2008 12:51:38 GMTarpankashyap-869238http://www.sqlservercentral.com/Forums/Topic1188226-265-1.aspx[b]In a SQL 2000, I have 2 stored procedures[/b]sproc1sproc2and using sp_helptext to see the SQL definition of that object[b]exec sp_helptext sproc1[/b]returns:...create procedure sproc1...[b]exec sp_helptext sproc2[/b]...create procedure sproc1 -- That is not a typo ....sproc1...[b]I also tried a query like:[/b]syscomments inner joined with sysobjects to return:syscomments.textsysobjects.nameThere are a few rows of syscomments.text...create procedure sproc1...[b]for both stored procedure object.[/b]yet when I [b]use SSMS & right-click modify[/b] / alter / drop and create...... procedure sproc1 or sproc2 -- depending where the right click was done...BTW-the same result happened in SQL 2008 (not R2) SQL Server.Let me please ask the questions:How could the right click (modify / alter / drop and create) be correct yet a query on the system tables or system stored procedures return in-correct?Does this mean that the system tables of the user database are corrupt?Is there a way to fix this? DBCC CheckDB?[b]Thank you for your time and any ideas to fix this system table corruption?[/b]Tue, 11 Oct 2011 00:51:51 GMTron_leghttp://www.sqlservercentral.com/Forums/Topic1173804-265-1.aspxI was approached today for a crashed SQL 2000 SP2 server with a single 800G database on it. Log is 20G. The database crashed due to the reason in the subject. I successfully recovered another backup from the same server, unfortunately it was long long time ago and size is only 3G, but structure is the same.I wonder how do I recover the rest of the data? Where should I start? I checked sysdatabases, I don't see the damaged database, not even in suspect mode.Any clue is greatly appreciated.Mon, 12 Sep 2011 15:21:59 GMThalifaxdalhttp://www.sqlservercentral.com/Forums/Topic1169992-265-1.aspxHi all,I am struggling with some databases going inconsistent.We are running SQL 2000 MSDE on NT 5.2. The db's (most of the times is only one of them but at times others join the party) generate the following error:[i]A possible database consistency problem has been detected on database 'xx'. DBCC CHECKDB and DBCC CHECKCATALOG should be run on database 'xx'.[/i]Obviously DBCC doesn't detect any errors. I checked the disks and the RAM but no errors there either. We have other server running 2005 and 2008 and they are fine so far.So now I am stuck with sql dumps which are generated every now and then. I have no idea what to do with them, the sql code that is 'dumped' is always different so I can't even match the failure with a specific action... And anyway I don't understand how some code can randomly make a db incosistent.Is there anything else I can do other than helplessly hand over the problem to MS ? (which I can't afford).I read in a post that a guy rebuild all his indexes and that saved the problem but it sounds like pure luck to me (rebuilding them maybe just moved them away from the bad sectors and he had io problems). I will try that too because i'm desperate.Thank you.Mon, 05 Sep 2011 09:01:29 GMTPavle-192195http://www.sqlservercentral.com/Forums/Topic1059822-265-1.aspxI have a table :CREATE TABLE [dbo].[haEmails] ( [emailRef] [int] IDENTITY (1, 1) NOT NULL , [Sent] [bit] NOT NULL , [FromUserNum] [int] NOT NULL , [ToUserNum] [int] NOT NULL , [MessageType] [int] NOT NULL , [AddedAt] [datetime] NOT NULL , [SentAt] [datetime] NULL , [MessageText] [varchar] (600) NULL , [Version20091013] [bit] NOT NULL ) ON [PRIMARY]GOALTER TABLE [dbo].[haEmails] WITH NOCHECK ADD CONSTRAINT [PK_TestEmails] PRIMARY KEY CLUSTERED ( [emailRef] ) WITH FILLFACTOR = 90 ON [PRIMARY] GOALTER TABLE [dbo].[haEmails] ADD CONSTRAINT [DF_TestEmails_Sent] DEFAULT (0) FOR [Sent], CONSTRAINT [DF_TestEmails_MessType] DEFAULT ((-1)) FOR [MessageType], CONSTRAINT [DF_TestEmails_AddedAt] DEFAULT (getdate()) FOR [AddedAt], CONSTRAINT [DF_haEmails_Version20091013] DEFAULT (0) FOR [Version20091013]GOMy application wasn't always responding to an INSERT trigger on the table, and my investigations found that :In Enterprise Manager, adding a new row : haEmails(FromUserNum,ToUserNum,MessageType) Values (22,11,-1)fails, with message "string or binary data would be truncated".But, Values (22,11,1) is successful.In the range 1..250 I only get this behaviour for FromUserNum = 22 or 74 or 97, all other FromUserNum integers allow a negative MessageType value.The criteria for failure appear to be : (FromUserNum = 22 OR FromUserNum = 74 OR FromUserNum = 97) AND MessageType < 0Can anyone tell me what's going on and how to avoid the problem ?Thanks in anticipation.Mike CMon, 07 Feb 2011 12:04:23 GMTmcinwghttp://www.sqlservercentral.com/Forums/Topic1130048-265-1.aspxHi allDoes anyone know what would cause data loss on tables after commit with no errors raised neither executed DELETEs? Is this a symptom of database corruption?I have seen this just twice from thousands records, using exactly the same Net Frmework code and Stored Procedure, suddenly there's no record in two tables that always must have data.There's no chance to avoid inserting in those tables.thanks for any advice.Wed, 22 Jun 2011 16:16:07 GMTNemachtianihttp://www.sqlservercentral.com/Forums/Topic1105944-265-1.aspxHi guys,Due to an unknown cause, some data in one table was deleted. There is no audit trail functionality for the application nor any timestamp field.The recovery model of the database is set to FULL but the data loss happened days before since the backup yesterday was already affected.Is there any measures that we can take to find the user that deleted the data?Like query the last users that logged-in to the server and accessed the database? or get the all the DML statements that were executed to the database? or any related diagnostic measures.Thank you.Tue, 10 May 2011 03:05:30 GMTricharddelcarmenhttp://www.sqlservercentral.com/Forums/Topic1108597-265-1.aspxWe have a distribution database on a dedicated distributor server which went into suspect mode. The reason we believe to be that the log file size was limited to 2Gigs when we upgraded it from 2000 to 2008. The upgrade process worked fine and we've been using the server successfully ever since until this morning. The size of the LOG file is 24Gigs despite the size limitation and that is probably because it was like that at the moment when the upgrade was done. Due to some increasingly replication activity probably the db tried to increase the log file even more but failed due to the limitation and started to through errors. At that point we restarted the server but it shows suspect mode after finishes the restart.We have a backup until the problem started this morning.What are the options?Thank you.Fri, 13 May 2011 10:02:18 GMTthe sqlisthttp://www.sqlservercentral.com/Forums/Topic522478-265-1.aspxHi,When I tried attaching the AdventureWorks Database to the SQL 2005 I get the following error.Msg 1813, Level 16, State 2, Line 1Could not open new database 'AdventureWorks'. CREATE DATABASE is aborted.Msg 602, Level 21, State 50, Line 1Could not find row in sysindexes for database ID 8, object ID 1, index ID 1. Run DBCC CHECKTABLE on sysindexes.Could you please let me know how can I attach the AdventureWorks Database.Tue, 24 Jun 2008 06:11:58 GMTnisha.lakhwarahttp://www.sqlservercentral.com/Forums/Topic1088772-265-1.aspxnot speak english ,,, goodHi AllI Have Sql Server 2000 databasename : Horizonand if i want to update some tables show this messege :" Database Error|Integrty trigger failedid#s are maintained by triggers and cannot be updated otherwise"how do to solve this proble;firs time show this messege, i use this database since 4 years until nowThankYou;Tue, 05 Apr 2011 10:58:22 GMTambo.phphttp://www.sqlservercentral.com/Forums/Topic1083065-265-1.aspxSQL 2000 Enterprise SP4.Our SQL server is periodically getting 823 errors as follows: Error: 823, Severity: 24, State: 2I/O error (bad page ID) detected during read at offset 0x00000022018000 in file 'F:\SQLDataFiles\Click2Coach_Data.MDF'. If I run DBCC CHECKDB sometimes it returns errors and sometimes it doesn't. Today I ran DBCC CHECKDB with repair and it reported about 12 errors fixed. However, the 823s started up again shortly after the repair finished. I've been running the DBCC CHECKDB statement periodically throughout the day. Most times it's clean but other times it returns errors. I took one of the object IDs that were in the error message and couldn't find it in sysobjects. We have run diagnostics on the disk and haven't found any problems. We also detached and moved the DB to a different drive (although it was just a logical drive), but that seemed to have no effect. Any ideas?Wed, 23 Mar 2011 18:42:51 GMTChristopher Westhttp://www.sqlservercentral.com/Forums/Topic1063342-265-1.aspxI coulnd not backup the database in sql server 2000 . i got erro" Nonreoverable I/O error occured 'E:\mssql\data.mdf' . this is haraware related error. disk problem.. Please help me .How to recover the backup data..Mon, 14 Feb 2011 01:12:29 GMTsolomon.jernashttp://www.sqlservercentral.com/Forums/Topic1056204-265-1.aspxSQL Server 2000.... How do I find what tables these problem objects are?[Microsoft][ODBC SQL Server Driver][SQL Server]Table error: Table '(Object ID 324208951)' (ID 324208951). Missing or invalid key in index '(Index ID 5)' (ID 5) for the row:[Microsoft][ODBC SQL Server Driver][SQL Server]Table error: Table '(Object ID 324208951)' (ID 324208951). Missing or invalid key in index '(Index ID 5)' (ID 5) for the row:[Microsoft][ODBC SQL Server Driver][SQL Server]Data row (1:2569152:49) identified by (RID = (1:2569152:49) ) has index values (DMA_NBR = 678 and FRANID = '102800').[Microsoft][ODBC SQL Server Driver][SQL Server]Data row (1:2569152:69) identified by (RID = (1:2569152:69) ) has index values (DMA_NBR = 679 and FRANID = '105800').[Microsoft][ODBC SQL Server Driver][SQL Server]Table error: Table '(Object ID 324208951)' (ID 324208951). Missing or invalid key in index '(Index ID 5)' (ID 5) for the row:[Microsoft][ODBC SQL Server Driver][SQL Server]CHECKDB found 0 allocation errors and 36 consistency errors in database 'AFA_MKIS'.[Microsoft][ODBC SQL Server Driver][SQL Server]repair_fast is the minimum repair level for the errors found by DBCC CHECKDB (AFA_MKIS ).Mon, 31 Jan 2011 07:50:55 GMTMarkushttp://www.sqlservercentral.com/Forums/Topic1051070-265-1.aspxA SQL Server 200 database went down. It was backed up on tape, but I don't think it was a proper .bak backup, I think it was just a backup of the .mdb. (I don't have access to these things on this server). It is currently being restored. SQL Server lists the database as (Restoring...)What kind of problems should I look out for in this situation? Will the restoration simply fail if it isn't from a .bak?Thu, 20 Jan 2011 11:41:49 GMTStefan Krzywickihttp://www.sqlservercentral.com/Forums/Topic1043043-265-1.aspxWe have corruption on one of our Sharepoint databases (SQL Server 2000). We've run a DBCC REPAIR_ALLOW_DATA_LOSS on a test server and the output is below (dir names and leaf names removed):[b]Nonqualified transactions are being rolled back. Estimated rollback completion: 100%.DBCC results for '<dbname>'.DBCC results for 'sysobjects'.There are 529 rows in 11 pages for object 'sysobjects'.DBCC results for 'sysindexes'.There are 188 rows in 8 pages for object 'sysindexes'.DBCC results for 'syscolumns'.There are 3516 rows in 54 pages for object 'syscolumns'.DBCC results for 'systypes'.There are 28 rows in 1 pages for object 'systypes'.DBCC results for 'syscomments'.There are 698 rows in 206 pages for object 'syscomments'.DBCC results for 'sysfiles1'.There are 2 rows in 1 pages for object 'sysfiles1'.DBCC results for 'syspermissions'.There are 18 rows in 1 pages for object 'syspermissions'.DBCC results for 'sysusers'.There are 13 rows in 1 pages for object 'sysusers'.DBCC results for 'sysproperties'.There are 0 rows in 0 pages for object 'sysproperties'.DBCC results for 'sysdepends'.There are 6143 rows in 32 pages for object 'sysdepends'.DBCC results for 'sysreferences'.There are 1 rows in 1 pages for object 'sysreferences'.DBCC results for 'sysfulltextcatalogs'.There are 0 rows in 1 pages for object 'sysfulltextcatalogs'.DBCC results for 'sysfulltextnotify'.There are 0 rows in 1 pages for object 'sysfulltextnotify'.DBCC results for 'sysfilegroups'.There are 1 rows in 1 pages for object 'sysfilegroups'.Server: Msg 8929, Level 16, State 1, Line 1Object ID 1993058136: Errors found in text ID 301518225408 owned by data record identified by RID = (1:1673852:13) SiteId = D7187BC0-42A8-471F-B5A0-E34808CAFF6F and DirName = '<dirname>' and LeafName = '<leafname>'.Server: Msg 8929, Level 16, State 1, Line 1Object ID 1993058136: Errors found in text ID 301518290944 owned by data record identified by RID = (1:1673852:13) SiteId = D7187BC0-42A8-471F-B5A0-E34808CAFF6F and DirName = '<dirname>' and LeafName = '<leafname>'.Server: Msg 8929, Level 16, State 1, Line 1Object ID 1993058136: Errors found in text ID 301518356480 owned by data record identified by RID = (1:1673852:13) SiteId = D7187BC0-42A8-471F-B5A0-E34808CAFF6F and DirName = '<dirname>' and LeafName = '<leafname>'.Server: Msg 8929, Level 16, State 1, Line 1Object ID 1993058136: Errors found in text ID 301507018752 owned by data record identified by RID = (1:4455912:15) SiteId = A8380FDC-921C-438D-A184-67EC05B7140B and DirName = '<dirname>' and LeafName = '<leafname>Server: Msg 8929, Level 16, State 1, Line 1Object ID 1993058136: Errors found in text ID 120336154624 owned by data record identified by RID = (1:7785459:9) SiteId = FA32B7C4-C2C3-43D5-8D29-C5224EC2DC3F and DirName = '<dirname>' and LeafName = '<leafname>Server: Msg 8929, Level 16, State 1, Line 1Object ID 1993058136: Errors found in text ID 314912276480 owned by data record identified by RID = (1:7790766:7) SiteId = 7BA0E748-6B6D-41EE-A80C-233A94614F6A and DirName = '<dirname>' and LeafName = '<leafname>'.Server: Msg 8929, Level 16, State 1, Line 1Object ID 1993058136: Errors found in text ID 314912342016 owned by data record identified by RID = (1:7790766:7) SiteId = 7BA0E748-6B6D-41EE-A80C-233A94614F6A and DirName = '<dirname>' and LeafName = '<leafname>'.Server: Msg 8929, Level 16, State 1, Line 1Object ID 1993058136: Errors found in text ID 314909982720 owned by data record identified by RID = (1:7790766:8) SiteId = 7BA0E748-6B6D-41EE-A80C-233A94614F6A and DirName = '<dirname>' and LeafName = '<leafname>'.Server: Msg 8929, Level 16, State 1, Line 1Object ID 1993058136: Errors found in text ID 314910048256 owned by data record identified by RID = (1:7790766:8) SiteId = 7BA0E748-6B6D-41EE-A80C-233A94614F6A and DirName = '<dirname>' and LeafName = '<leafname>'.Server: Msg 8929, Level 16, State 1, Line 1Object ID 1993058136: Errors found in text ID 314910113792 owned by data record identified by RID = (1:7790766:8) SiteId = 7BA0E748-6B6D-41EE-A80C-233A94614F6A and DirName = '<dirname>' and LeafName = '<leafname>'.Server: Msg 8929, Level 16, State 1, Line 1Object ID 1993058136: Errors found in text ID 301509378048 owned by data record identified by RID = (1:8331567:8) SiteId = 40B075ED-CD17-47DF-93E6-EDE8626DE96C and DirName = '<dirname>' and LeafName = '<leafname>'.Server: Msg 8929, Level 16, State 1, Line 1Object ID 1993058136: Errors found in text ID 314907688960 owned by data record identified by RID = (1:8470263:17) SiteId = 726A74F2-A51F-425A-8404-93A0DF59C5B1 and DirName = '<dirname>' and LeafName = '<leafname>'.Server: Msg 8929, Level 16, State 1, Line 1Object ID 1993058136: Errors found in text ID 314907754496 owned by data record identified by RID = (1:8470263:17) SiteId = 726A74F2-A51F-425A-8404-93A0DF59C5B1 and DirName = '<dirname>' and LeafName = '<leafname>'.DBCC results for 'Sites'.There are 516 rows in 31 pages for object 'Sites'.DBCC results for 'Webs'.There are 516 rows in 430 pages for object 'Webs'.DBCC results for 'Categories'.There are 0 rows in 0 pages for object 'Categories'.DBCC results for 'WebCat'.There are 6192 rows in 96 pages for object 'WebCat'.DBCC results for 'Lists'.There are 5147 rows in 623 pages for object 'Lists'.DBCC results for 'UserData'.There are 823247 rows in 138691 pages for object 'UserData'.DBCC results for 'WebParts'.There are 28314 rows in 996 pages for object 'WebParts'.DBCC results for 'EventCache'.There are 0 rows in 0 pages for object 'EventCache'.DBCC results for 'EventLog'.There are 0 rows in 0 pages for object 'EventLog'.DBCC results for 'ImmedSubscriptions'.There are 0 rows in 0 pages for object 'ImmedSubscriptions'.DBCC results for 'SchedSubscriptions'.There are 0 rows in 0 pages for object 'SchedSubscriptions'.DBCC results for 'Personalization'.There are 0 rows in 0 pages for object 'Personalization'.DBCC results for 'WelcomeNames'.There are 2 rows in 1 pages for object 'WelcomeNames'.DBCC results for 'TimerLock'.There are 1 rows in 1 pages for object 'TimerLock'.DBCC results for 'DiskWarningDate'.There are 1 rows in 1 pages for object 'DiskWarningDate'.DBCC results for 'ComMd'.There are 42 rows in 1 pages for object 'ComMd'.DBCC results for 'UserInfo'.There are 17858 rows in 610 pages for object 'UserInfo'.DBCC results for 'dtproperties'.There are 0 rows in 0 pages for object 'dtproperties'.DBCC results for 'WebMembers'.There are 16872 rows in 165 pages for object 'WebMembers'.DBCC results for 'SiteGroupMembership'.There are 0 rows in 0 pages for object 'SiteGroupMembership'.DBCC results for 'WebGroupMembership'.There are 12421 rows in 90 pages for object 'WebGroupMembership'.DBCC results for 'WebGroups'.There are 2580 rows in 125 pages for object 'WebGroups'.DBCC results for 'SiteGroups'.There are 0 rows in 0 pages for object 'SiteGroups'.DBCC results for 'SystemVersion'.There are 1 rows in 1 pages for object 'SystemVersion'.DBCC results for 'HT_Settings'.There are 5 rows in 1 pages for object 'HT_Settings'.DBCC results for 'HT_Cache'.There are 0 rows in 0 pages for object 'HT_Cache'.DBCC results for 'Deps'.There are 69 rows in 4 pages for object 'Deps'.DBCC results for 'Docs'. The error has been repaired. The error has been repaired. The error has been repaired. The error has been repaired. The error has been repaired. The error has been repaired. The error has been repaired. The error has been repaired. The error has been repaired. The error has been repaired. The error has been repaired. The error has been repaired. The error has been repaired.Server: Msg 8929, Level 16, State 1, Line 1Object ID 1993058136: Errors found in text ID 314907820032 owned by data record identified by RID = (1:8470263:17) SiteId = 726A74F2-A51F-425A-8404-93A0DF59C5B1 and DirName = '<dirname>' and LeafName = '<leafname>'.Server: Msg 8929, Level 16, State 1, Line 1Object ID 1993058136: Errors found in text ID 312662818816 owned by data record identified by RID = (1:9907830:14) SiteId = 6104BB99-1030-4C9C-9285-958C88B8C25C and DirName = '<dirname>' and LeafName = '<leafname>'.Server: Msg 8929, Level 16, State 1, Line 1Object ID 1993058136: Errors found in text ID 312662884352 owned by data record identified by RID = (1:9907830:14) SiteId = 6104BB99-1030-4C9C-9285-958C88B8C25C and DirName = '<dirname>' and LeafName = '<leafname>'.Server: Msg 8929, Level 16, State 1, Line 1Object ID 1993058136: Errors found in text ID 301568819200 owned by data record identified by RID = (1:10138160:1) SiteId = 6104BB99-1030-4C9C-9285-958C88B8C25C and DirName = '<dirname>' and LeafName = '<leafname>Server: Msg 8929, Level 16, State 1, Line 1Object ID 1993058136: Errors found in text ID 301568884736 owned by data record identified by RID = (1:10138160:1) SiteId = 6104BB99-1030-4C9C-9285-958C88B8C25C and DirName = '<dirname>' and LeafName = '<leafname>Server: Msg 8929, Level 16, State 1, Line 1Object ID 1993058136: Errors found in text ID 315290615808 owned by data record identified by RID = (1:11937877:1) SiteId = 508120F8-4CFD-4B68-A046-BFEB1C59B123 and DirName = '<dirname>' and LeafName = '<leafname>'.Server: Msg 8929, Level 16, State 1, Line 1Object ID 1993058136: Errors found in text ID 315290681344 owned by data record identified by RID = (1:11937877:1) SiteId = 508120F8-4CFD-4B68-A046-BFEB1C59B123 and DirName = '<dirname>' and LeafName = '<leafname>'.Server: Msg 8929, Level 16, State 1, Line 1Object ID 1993058136: Errors found in text ID 315292909568 owned by data record identified by RID = (1:11946282:10) SiteId = 508120F8-4CFD-4B68-A046-BFEB1C59B123 and DirName = '<dirname>' and LeafName = '<leafname>'.Server: Msg 8929, Level 16, State 1, Line 1Object ID 1993058136: Errors found in text ID 315292975104 owned by data record identified by RID = (1:11946282:10) SiteId = 508120F8-4CFD-4B68-A046-BFEB1C59B123 and DirName = '<dirname>' and LeafName = '<leafname>'.Server: Msg 8929, Level 16, State 1, Line 1Object ID 1993058136: Errors found in text ID 315293040640 owned by data record identified by RID = (1:11946282:10) SiteId = 508120F8-4CFD-4B68-A046-BFEB1C59B123 and DirName = '<dirname>' and LeafName = '<leafname>'.Server: Msg 8929, Level 16, State 1, Line 1Object ID 1993058136: Errors found in text ID 301522944000 owned by data record identified by RID = (1:17738338:7) SiteId = 6104BB99-1030-4C9C-9285-958C88B8C25C and DirName = '<dirname>' and LeafName = '<leafname>'.Server: Msg 8964, Level 16, State 1, Line 1Table error: Object ID 1993058136. The text, ntext, or image node at page (1:9191128), slot 2, text ID 312662818816 is not referenced.Server: Msg 8928, Level 16, State 1, Line 1Object ID 1993058136, index ID 255: Page (1:9583792) could not be processed. See other errors for details.Server: Msg 8965, Level 16, State 1, Line 1Table error: Object ID 1993058136. The text, ntext, or image node at page (1:9583792), slot 1, text ID 301507018752 is referenced by page (1:4455912), slot 15, but was not seen in the scan.Server: Msg 8965, Level 16, State 1, Line 1Table error: Object ID 1993058136. The text, ntext, or image node at page (1:9583792), slot 2, text ID 301509378048 is referenced by page (1:8331567), slot 8, but was not seen in the scan.Server: Msg 8944, Level 16, State 1, Line 1Table error: Object ID 1993058136, index ID 255, page (1:9583792), row 3. Test (ColumnOffsets <= (nextRec - pRec)) failed. Values are 65280 and 1121.Server: Msg 8965, Level 16, State 1, Line 1Table error: Object ID 1993058136. The text, ntext, or image node at page (1:9583792), slot 4, text ID 301518225408 is referenced by page (1:1673852), slot 13, but was not seen in the scan.Server: Msg 8965, Level 16, State 1, Line 1Table error: Object ID 1993058136. The text, ntext, or image node at page (1:9583792), slot 5, text ID 301518290944 is referenced by page (1:1673852), slot 13, but was not seen in the scan.Server: Msg 8965, Level 16, State 1, Line 1Table error: Object ID 1993058136. The text, ntext, or image node at page (1:9583792), slot 6, text ID 301518356480 is referenced by page (1:1673852), slot 13, but was not seen in the scan.Server: Msg 8965, Level 16, State 1, Line 1Table error: Object ID 1993058136. The text, ntext, or image node at page (1:9583792), slot 7, text ID 301522944000 is referenced by page (1:17738338), slot 7, but was not seen in the scan.Server: Msg 8965, Level 16, State 1, Line 1Table error: Object ID 1993058136. The text, ntext, or image node at page (1:9583792), slot 8, text ID 301568819200 is referenced by page (1:10138160), slot 1, but was not seen in the scan.Server: Msg 8965, Level 16, State 1, Line 1Table error: Object ID 1993058136. The text, ntext, or image node at page (1:9583792), slot 9, text ID 301568884736 is referenced by page (1:10138160), slot 1, but was not seen in the scan.Server: Msg 8965, Level 16, State 1, Line 1Table error: Object ID 1993058136. The text, ntext, or image node at page (1:9583792), slot 16, text ID 312662818816 is referenced by page (1:9907830), slot 14, but was not seen in the scan.Server: Msg 8965, Level 16, State 1, Line 1Table error: Object ID 1993058136. The text, ntext, or image node at page (1:9583792), slot 17, text ID 312662884352 is referenced by page (1:9907830), slot 14, but was not seen in the scan.Server: Msg 8965, Level 16, State 1, Line 1Table error: Object ID 1993058136. The text, ntext, or image node at page (1:9583792), slot 19, text ID 314907688960 is referenced by page (1:8470263), slot 17, but was not seen in the scan.Server: Msg 8965, Level 16, State 1, Line 1Table error: Object ID 1993058136. The text, ntext, or image node at page (1:9583792), slot 20, text ID 314907754496 is referenced by page (1:8470263), slot 17, but was not seen in the scan.Server: Msg 8965, Level 16, State 1, Line 1Table error: Object ID 1993058136. The text, ntext, or image node at page (1:9583792), slot 21, text ID 314907820032 is referenced by page (1:8470263), slot 17, but was not seen in the scan.Server: Msg 8965, Level 16, State 1, Line 1Table error: Object ID 1993058136. The text, ntext, or image node at page (1:9583792), slot 22, text ID 314909982720 is referenced by page (1:7790766), slot 8, but was not seen in the scan. The error has been repaired. The error has been repaired. The error has been repaired. The error has been repaired. The error has been repaired. The error has been repaired. The error has been repaired. The error has been repaired. The error has been repaired. The error has been repaired. The error has been repaired. The error has been repaired. The error has been repaired. The error has been repaired. The error has been repaired. The error has been repaired. The error has been repaired. The error has been repaired. The error has been repaired. The error has been repaired. The error has been repaired. The error has been repaired. The error has been repaired. The error has been repaired. The error has been repaired. The error has been repaired. The error has been repaired. The error has been repaired.Server: Msg 8965, Level 16, State 1, Line 1Table error: Object ID 1993058136. The text, ntext, or image node at page (1:9583792), slot 23, text ID 314910048256 is referenced by page (1:7790766), slot 8, but was not seen in the scan.Server: Msg 8965, Level 16, State 1, Line 1Table error: Object ID 1993058136. The text, ntext, or image node at page (1:9583792), slot 24, text ID 314910113792 is referenced by page (1:7790766), slot 8, but was not seen in the scan.Server: Msg 8965, Level 16, State 1, Line 1Table error: Object ID 1993058136. The text, ntext, or image node at page (1:9583792), slot 25, text ID 314912276480 is referenced by page (1:7790766), slot 7, but was not seen in the scan.Server: Msg 8965, Level 16, State 1, Line 1Table error: Object ID 1993058136. The text, ntext, or image node at page (1:9583792), slot 26, text ID 314912342016 is referenced by page (1:7790766), slot 7, but was not seen in the scan.Server: Msg 8965, Level 16, State 1, Line 1Table error: Object ID 1993058136. The text, ntext, or image node at page (1:9583792), slot 27, text ID 315290615808 is referenced by page (1:11937877), slot 1, but was not seen in the scan.Server: Msg 8965, Level 16, State 1, Line 1Table error: Object ID 1993058136. The text, ntext, or image node at page (1:9583792), slot 28, text ID 315290681344 is referenced by page (1:11937877), slot 1, but was not seen in the scan.Server: Msg 8965, Level 16, State 1, Line 1Table error: Object ID 1993058136. The text, ntext, or image node at page (1:9583792), slot 30, text ID 315292909568 is referenced by page (1:11946282), slot 10, but was not seen in the scan.Server: Msg 8965, Level 16, State 1, Line 1Table error: Object ID 1993058136. The text, ntext, or image node at page (1:9583792), slot 31, text ID 315292975104 is referenced by page (1:11946282), slot 10, but was not seen in the scan.Server: Msg 8965, Level 16, State 1, Line 1Table error: Object ID 1993058136. The text, ntext, or image node at page (1:9583792), slot 32, text ID 315293040640 is referenced by page (1:11946282), slot 10, but was not seen in the scan.Server: Msg 8964, Level 16, State 1, Line 1Table error: Object ID 1993058136. The text, ntext, or image node at page (1:9871194), slot 0, text ID 301507018752 is not referenced.Server: Msg 8964, Level 16, State 1, Line 1Table error: Object ID 1993058136. The text, ntext, or image node at page (1:9871455), slot 0, text ID 301568884736 is not referenced.Server: Msg 8964, Level 16, State 1, Line 1Table error: Object ID 1993058136. The text, ntext, or image node at page (1:10088545), slot 0, text ID 312662884352 is not referenced.Server: Msg 8964, Level 16, State 1, Line 1Table error: Object ID 1993058136. The text, ntext, or image node at page (1:10088546), slot 0, text ID 312662884352 is not referenced.Server: Msg 8964, Level 16, State 1, Line 1Table error: Object ID 1993058136. The text, ntext, or image node at page (1:10088547), slot 0, text ID 312662884352 is not referenced.Server: Msg 8964, Level 16, State 1, Line 1Table error: Object ID 1993058136. The text, ntext, or image node at page (1:10088548), slot 0, text ID 312662884352 is not referenced.Server: Msg 8964, Level 16, State 1, Line 1Table error: Object ID 1993058136. The text, ntext, or image node at page (1:10153036), slot 1, text ID 314909982720 is not referenced.Server: Msg 8964, Level 16, State 1, Line 1Table error: Object ID 1993058136. The text, ntext, or image node at page (1:10153036), slot 2, text ID 314912276480 is not referenced.Server: Msg 8964, Level 16, State 1, Line 1Table error: Object ID 1993058136. The text, ntext, or image node at page (1:10153331), slot 0, text ID 314907754496 is not referenced.Server: Msg 8964, Level 16, State 1, Line 1Table error: Object ID 1993058136. The text, ntext, or image node at page (1:10153332), slot 0, text ID 314910048256 is not referenced.Server: Msg 8964, Level 16, State 1, Line 1Table error: Object ID 1993058136. The text, ntext, or image node at page (1:10153333), slot 0, text ID 314910048256 is not referenced.Server: Msg 8964, Level 16, State 1, Line 1Table error: Object ID 1993058136. The text, ntext, or image node at page (1:10153334), slot 0, text ID 314910048256 is not referenced.Server: Msg 8964, Level 16, State 1, Line 1Table error: Object ID 1993058136. The text, ntext, or image node at page (1:10153335), slot 0, text ID 314910048256 is not referenced.Server: Msg 8964, Level 16, State 1, Line 1Table error: Object ID 1993058136. The text, ntext, or image node at page (1:10159975), slot 0, text ID 315290681344 is not referenced.Server: Msg 8964, Level 16, State 1, Line 1Table error: Object ID 1993058136. The text, ntext, or image node at page (1:10159979), slot 0, text ID 315292975104 is not referenced.Server: Msg 8964, Level 16, State 1, Line 1Table error: Object ID 1993058136. The text, ntext, or image node at page (1:10159980), slot 0, text ID 315292975104 is not referenced.Server: Msg 8964, Level 16, State 1, Line 1Table error: Object ID 1993058136. The text, ntext, or image node at page (1:10159981), slot 0, text ID 315292975104 is not referenced.Server: Msg 8964, Level 16, State 1, Line 1Table error: Object ID 1993058136. The text, ntext, or image node at page (1:10159982), slot 0, text ID 315292975104 is not referenced.Server: Msg 8928, Level 16, State 1, Line 1Object ID 1993058136, index ID 255: Page (1:10542555) could not be processed. See other errors for details.Server: Msg 8939, Level 16, State 1, Line 1Table error: Object ID 1993058136, index ID 255, page (1:10542555). Test (IS_ON (BUF_IOERR, bp->bstat) && bp->berrcode) failed. Values are 2057 and -1.Server: Msg 8965, Level 16, State 1, Line 1Table error: Object ID 1993058136. The text, ntext, or image node at page (1:10542555), slot 0, text ID 120336154624 is referenced by page (1:10542531), slot 0, but was not seen in the scan.Server: Msg 8964, Level 16, State 1, Line 1Table error: Object ID 1993058136. The text, ntext, or image node at page (1:11926382), slot 15, text ID 315292975104 is not referenced.Server: Msg 8964, Level 16, State 1, Line 1Table error: Object ID 1993058136. The text, ntext, or image node at page (1:13640409), slot 0, text ID 314910048256 is not referenced.Server: Msg 8964, Level 16, State 1, Line 1Table error: Object ID 1993058136. The text, ntext, or image node at page (1:13640410), slot 0, text ID 314912342016 is not referenced.Server: Msg 8964, Level 16, State 1, Line 1Table error: Object ID 1993058136. The text, ntext, or image node at page (1:19888540), slot 0, text ID 301518290944 is not referenced. The error has been repaired. The error has been repaired. The error has been repaired. The error has been repaired. The error has been repaired. The error has been repaired. The error has been repaired. The error has been repaired. The error has been repaired. The error has been repaired. The error has been repaired. The error has been repaired. The error has been repaired. The error has been repaired. The error has been repaired. The error has been repaired. The error has been repaired. The error has been repaired. The error has been repaired. The error has been repaired. The error has been repaired. The error has been repaired. The error has been repaired. The error has been repaired. The error has been repaired. The error has been repaired. The error has been repaired. The error has been repaired. The error has been repaired. The error has been repaired. The error has been repaired. The error has been repaired. The error has been repaired. The error has been repaired.Repair: Deleted text column, text ID 301518225408, for object ID 1993058136 on page (1:1673852), slot 13.Repair: Deleted text column, text ID 301518290944, for object ID 1993058136 on page (1:1673852), slot 13.Repair: Deleted text column, text ID 301518356480, for object ID 1993058136 on page (1:1673852), slot 13.Server: Msg 8952, Level 16, State 1, Line 1Table error: Database '<dbname>', index 'Links.Links_Backward' (ID 2121058592) (index ID 2). Extra or invalid key for the keys:Server: Msg 8956, Level 16, State 1, Line 1Index row (1:22736431:4) with values (SiteId = 5515C06E-0231-4A19-8BF9-885CE79178A9 and TargetDirName = '<dirname>' and TargetLeafName = NULL and SiteId = 5515C06E-0231-4A19-8BF9-885CE79178A9 and DirName = 'pe) points to the data row identified by ().Server: Msg 8952, Level 16, State 1, Line 1Table error: Database '<dbname>', index 'Links.Links_Backward' (ID 2121058592) (index ID 2). Extra or invalid key for the keys:Server: Msg 8956, Level 16, State 1, Line 1Index row (1:22736431:9) with values (SiteId = 5515C06E-0231-4A19-8BF9-885CE79178A9 and TargetDirName = '<dirname>' and TargetLeafName = NULL and SiteId = 5515C06E-0231-4A19-8BF9-885CE79178A9 and DirName = '<dirname>' and LeafName = '<leafname>) points to the data row identified by ().Repair: Deleted text column, text ID 301507018752, for object ID 1993058136 on page (1:4455912), slot 15.Repair: Deleted text column, text ID 120336154624, for object ID 1993058136 on page (1:7785459), slot 9.Repair: Deleted text column, text ID 314912276480, for object ID 1993058136 on page (1:7790766), slot 7.Repair: Deleted text column, text ID 314912342016, for object ID 1993058136 on page (1:7790766), slot 7.Repair: Deleted text column, text ID 314909982720, for object ID 1993058136 on page (1:7790766), slot 8.Repair: Deleted text column, text ID 314910048256, for object ID 1993058136 on page (1:7790766), slot 8.Repair: Deleted text column, text ID 314910113792, for object ID 1993058136 on page (1:7790766), slot 8.Repair: Deleted text column, text ID 301509378048, for object ID 1993058136 on page (1:8331567), slot 8.Repair: Deleted text column, text ID 314907688960, for object ID 1993058136 on page (1:8470263), slot 17.Repair: Deleted text column, text ID 314907754496, for object ID 1993058136 on page (1:8470263), slot 17.Repair: Deleted text column, text ID 314907820032, for object ID 1993058136 on page (1:8470263), slot 17.Repair: Deleted text column, text ID 312662818816, for object ID 1993058136 on page (1:9907830), slot 14.Repair: Deleted text column, text ID 312662884352, for object ID 1993058136 on page (1:9907830), slot 14.Repair: Deleted text column, text ID 301568819200, for object ID 1993058136 on page (1:10138160), slot 1.Repair: Deleted text column, text ID 301568884736, for object ID 1993058136 on page (1:10138160), slot 1.Repair: Deleted text column, text ID 315290615808, for object ID 1993058136 on page (1:11937877), slot 1.Repair: Deleted text column, text ID 315290681344, for object ID 1993058136 on page (1:11937877), slot 1.Repair: Deleted text column, text ID 315292909568, for object ID 1993058136 on page (1:11946282), slot 10.Repair: Deleted text column, text ID 315292975104, for object ID 1993058136 on page (1:11946282), slot 10.Repair: Deleted text column, text ID 315293040640, for object ID 1993058136 on page (1:11946282), slot 10.Repair: Deleted text column, text ID 301522944000, for object ID 1993058136 on page (1:17738338), slot 7.Repair: Page (1:9583792) has been deallocated from object ID 1993058136, index ID 255.Repair: Page (1:10542555) has been deallocated from object ID 1993058136, index ID 255.There are 868438 rows in 78804 pages for object 'Docs'.CHECKDB found 0 allocation errors and 75 consistency errors in table 'Docs' (object ID 1993058136).CHECKDB fixed 0 allocation errors and 75 consistency errors in table 'Docs' (object ID 1993058136).DBCC results for 'DocVersions'.There are 4689 rows in 122 pages for object 'DocVersions'.DBCC results for 'Links'. The error has been repaired. The error has been repaired.There are 179168 rows in 11717 pages for object 'Links'.CHECKDB found 0 allocation errors and 2 consistency errors in table 'Links' (object ID 2121058592).CHECKDB fixed 0 allocation errors and 2 consistency errors in table 'Links' (object ID 2121058592).DBCC results for 'NavNodes'.There are 7064 rows in 240 pages for object 'NavNodes'.CHECKDB found 0 allocation errors and 77 consistency errors in database '<dbname>'.CHECKDB fixed 0 allocation errors and 77 consistency errors in database '<dbname>'.DBCC execution completed. If DBCC printed error messages, contact your system administrator.[/b]It is encouraging that all errors have been fixed, but is there any way to determine exactly which data loss has occurred following the repair?Also, we've seen various suggestions that DBCC REPAIR_ALLOW_DATA_LOSS should not be run on a SharePoint database, including here: http://support.microsoft.com/kb/841057/en-us , so we're currently debating whether this is even an option for us.Thanks very muchPGWed, 05 Jan 2011 07:14:30 GMTPhineas Gage