InstantForum.NET v2.9.0SQLServerCentralhttp://www.sqlservercentral.com/Forums/notifications@sqlservercentral.comThu, 24 May 2012 12:48:59 GMT20http://www.sqlservercentral.com/Forums/Topic1303812-2893-1.aspxDear master,I have risk:Tables current 150,000,000 rowsIf T-SQL with below then exec about more 3 hours and log file extent to 170GB capacityDELETE CashTransactionsWHERE CashTransYMD <= '201111231'How to delete by object of SSIS (SQL 2008 R2) ? Exec good time and extent log file Best,PhuongNHMon, 21 May 2012 20:47:14 GMTnhphuong76http://www.sqlservercentral.com/Forums/Topic1286664-2893-1.aspxThe db is working as normal, but in the SQL logs I see these 3 messagesThe operating system returned error incorrect checksum (expected: 0x1b0a0fbe; actual: 0x1b0a0fbe) to SQL Server during a read at offset 0x00000ae7e9c000 in file 'D:\Data\MyData.mdf'. Additional messages in the SQL Server error log and system event log may provide more detail. This is a severe system-level error condition that threatens database integrity and must be corrected immediately. Complete a full database consistency check (DBCC CHECKDB). This error can be caused by many factors; for more information, see SQL Server Books Online.Error: 823, Severity: 24, State: 7.Operating system error 'incorrect checksum (expected: 0x1b0a0fbe; actual: 0x1b0a0fbe)' resulted from attempt to read the following: sort run page (3:5717838), in file 'D:\Data\MuData_data.mdf', in database with ID 23. Sort is retrying the read.I've run dbcc checkdb(MyData) but that said 0 errors found 0 errors repaired.This is a sql 2005 instance and the DB page verify is set to checksumAny ideas from a SQL viewpoint? whilst I also ask the infrastructure team to check the D: driveThu, 19 Apr 2012 13:29:52 GMTsotnhttp://www.sqlservercentral.com/Forums/Topic1297659-2893-1.aspxHere's my situation: the files of a database someone was keeping locally on a SQL Express instance on their machine got deleted (somehow while the SQL instance was actually running--still haven't managed to figure out how that was even possible, but that's by the by). I managed to use an undelete tool to recover all but one of the files. The one missing file is a full-text index catalogue, and given the size of the data I should be able to rebuild that in seconds--but SQL server won't let me attach the database because of the missing file!Now, the chap assures me he doesn't really need this database anymore, but nonetheless the problem is bugging me; why would something as relatively unimportant, and easy to rebuild, as a full-text catalogue prevent reattaching the database? It seems ridiculous. Is there a workround for this?Thu, 10 May 2012 01:37:52 GMTpaul.knibbshttp://www.sqlservercentral.com/Forums/Topic1296249-2893-1.aspxdear allwhat is production database size generally(500gb or 1tb) and how to monitor the databasewhat is step for monitoring production databaseThanksTue, 08 May 2012 00:58:19 GMTsatvinder.atwalhttp://www.sqlservercentral.com/Forums/Topic1293589-2893-1.aspxHi AllSince the network engineer upgraded the virutal server SAN software two weeks ago the sharepoint database has been failing the nightly database integrity check. The error log and sqlserver log shows the following entries.-----BCC CHECKDB (WSS_Content_xxx) WITH no_infomsgs executed by dbadmin terminated abnormally due to error state 5. Elapsed time: 0 hours 2 minutes 17 seconds.-----Error number 1073548784-------------The database seems okay in that it can backup, etc, but it fails the Integrity Check.Any suggestions would be welcome.AdoniaTue, 01 May 2012 21:36:17 GMTAdonia Delavigne-521648http://www.sqlservercentral.com/Forums/Topic1273580-2893-1.aspxHi,My Database is running in Sql server 2008 R2, I am taking backup of all my user database(sharepoint database) in the night. All database backup went well, except one database. Getting following error:"Backup detected log corruption in database WSS_Content_8d4c986f-42d6-486c-a42f-9612a94620d9. Context is Bad Middle Sector. LogFile: 2 'D:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\DATA\WSS_Content_8d4c986f-42d6-486c-a42f-9612a94620d9_log.LDF' VLF SeqNo: x855 VLFBase: x32d80000 LogBlockOffset: x32e72000 SectorStatus: 4 LogBlock.StartLsn.SeqNo: x855 LogBlock.StartLsn.Blk: x730 Size: xe400 PrevSize: xe600"Could anyone help me to fix this error permanently.GansTue, 27 Mar 2012 09:03:55 GMTGanshttp://www.sqlservercentral.com/Forums/Topic1242225-2893-1.aspxFollowing error I am getting when I ran DBCC CHECKDB('databasename') WITH NO-INFOMSGS Msg 8939, Level 16, State 98, Line 1Table error: Object ID 0, index ID -1, partition ID 0, alloc unit ID 296997425053696 (type Unknown), page (0:-1069739771). Test (IS_OFF (BUF_IOERR, pBUF->bstat)) failed. Values are 12716041 and -1.Msg 8939, Level 16, State 98, Line 1Table error: Object ID 0, index ID -1, partition ID 0, alloc unit ID 317901150158848 (type Unknown), page (8481:555819297). Test (IS_OFF (BUF_IOERR, pBUF->bstat)) failed. Values are 12716041 and -10.Msg 8939, Level 16, State 98, Line 1Table error: Object ID 0, index ID -1, partition ID 0, alloc unit ID 317901150158848 (type Unknown), page (8481:555819297). Test (IS_OFF (BUF_IOERR, pBUF->bstat)) failed. Values are 12716041 and -12.Msg 8939, Level 16, State 98, Line 1Table error: Object ID 0, index ID -1, partition ID 0, alloc unit ID 317901150158848 (type Unknown), page (8481:555819297). Test (IS_OFF (BUF_IOERR, pBUF->bstat)) failed. Values are 12716041 and -12.Msg 8939, Level 16, State 98, Line 1Table error: Object ID 0, index ID -1, partition ID 0, alloc unit ID 317901150158848 (type Unknown), page (8481:555819297). Test (IS_OFF (BUF_IOERR, pBUF->bstat)) failed. Values are 12716041 and -14.Msg 8939, Level 16, State 98, Line 1Table error: Object ID 0, index ID -1, partition ID 0, alloc unit ID 317901150158848 (type Unknown), page (8481:555819297). Test (IS_OFF (BUF_IOERR, pBUF->bstat)) failed. Values are 12716041 and -10.Msg 8939, Level 16, State 98, Line 1Table error: Object ID 0, index ID -1, partition ID 0, alloc unit ID 317901150158848 (type Unknown), page (8481:555819297). Test (IS_OFF (BUF_IOERR, pBUF->bstat)) failed. Values are 12716041 and -14.Msg 8939, Level 16, State 98, Line 1Table error: Object ID 0, index ID -1, partition ID 0, alloc unit ID 317901150158848 (type Unknown), page (8481:555819297). Test (IS_OFF (BUF_IOERR, pBUF->bstat)) failed. Values are 12716041 and -10.Msg 8939, Level 16, State 98, Line 1Table error: Object ID 0, index ID -1, partition ID 0, alloc unit ID 317901150158848 (type Unknown), page (8481:555819297). Test (IS_OFF (BUF_IOERR, pBUF->bstat)) failed. Values are 12716041 and -4.Msg 8939, Level 16, State 98, Line 1Table error: Object ID 0, index ID -1, partition ID 0, alloc unit ID 317901150158848 (type Unknown), page (8481:555819297). Test (IS_OFF (BUF_IOERR, pBUF->bstat)) failed. Values are 12716041 and -10.Msg 8939, Level 16, State 98, Line 1Table error: Object ID 0, index ID -1, partition ID 0, alloc unit ID 317901150158848 (type Unknown), page (8481:555819297). Test (IS_OFF (BUF_IOERR, pBUF->bstat)) failed. Values are 12716041 and -10.Msg 8939, Level 16, State 98, Line 1Table error: Object ID 0, index ID -1, partition ID 0, alloc unit ID 317901150158848 (type Unknown), page (8481:555819297). Test (IS_OFF (BUF_IOERR, pBUF->bstat)) failed. Values are 12716041 and -4.Msg 8939, Level 16, State 98, Line 1Table error: Object ID 0, index ID -1, partition ID 0, alloc unit ID 317901150158848 (type Unknown), page (8481:555819297). Test (IS_OFF (BUF_IOERR, pBUF->bstat)) failed. Values are 12716041 and -10.Msg 8939, Level 16, State 98, Line 1Table error: Object ID 0, index ID -1, partition ID 0, alloc unit ID 317901150158848 (type Unknown), page (8481:555819297). Test (IS_OFF (BUF_IOERR, pBUF->bstat)) failed. Values are 12716041 and -4.Msg 8939, Level 16, State 98, Line 1Table error: Object ID 0, index ID -1, partition ID 0, alloc unit ID 317901150158848 (type Unknown), page (8481:555819297). Test (IS_OFF (BUF_IOERR, pBUF->bstat)) failed. Values are 12716041 and -1.Msg 8939, Level 16, State 98, Line 1Table error: Object ID 0, index ID -1, partition ID 0, alloc unit ID 317901150158848 (type Unknown), page (8481:555819297). Test (IS_OFF (BUF_IOERR, pBUF->bstat)) failed. Values are 12716041 and -4.CHECKDB found 0 allocation errors and 16 consistency errors not associated with any single object.Msg 8928, Level 16, State 1, Line 1Object ID 373576369, index ID 1, partition ID 72057594075611136, alloc unit ID 72057594040549376 (type LOB data): Page (1:35864) could not be processed. See other errors for details.Msg 8965, Level 16, State 1, Line 1Table error: Object ID 373576369, index ID 1, partition ID 72057594075611136, alloc unit ID 72057594040549376 (type LOB data). The off-row data node at page (1:35864), slot 0, text ID 94371840 is referenced by page (1:35555), slot 0, but was not seen in the scan.Msg 8928, Level 16, State 1, Line 1Object ID 373576369, index ID 1, partition ID 72057594075611136, alloc unit ID 72057594040549376 (type LOB data): Page (1:35865) could not be processed. See other errors for details.Msg 8965, Level 16, State 1, Line 1Table error: Object ID 373576369, index ID 1, partition ID 72057594075611136, alloc unit ID 72057594040549376 (type LOB data). The off-row data node at page (1:35865), slot 0, text ID 94371840 is referenced by page (1:35555), slot 0, but was not seen in the scan.Msg 8928, Level 16, State 1, Line 1Object ID 373576369, index ID 1, partition ID 72057594075611136, alloc unit ID 72057594040549376 (type LOB data): Page (1:35866) could not be processed. See other errors for details.Msg 8965, Level 16, State 1, Line 1Table error: Object ID 373576369, index ID 1, partition ID 72057594075611136, alloc unit ID 72057594040549376 (type LOB data). The off-row data node at page (1:35866), slot 0, text ID 94371840 is referenced by page (1:35555), slot 0, but was not seen in the scan.Msg 8928, Level 16, State 1, Line 1Object ID 373576369, index ID 1, partition ID 72057594075611136, alloc unit ID 72057594040549376 (type LOB data): Page (1:35867) could not be processed. See other errors for details.Msg 8965, Level 16, State 1, Line 1Table error: Object ID 373576369, index ID 1, partition ID 72057594075611136, alloc unit ID 72057594040549376 (type LOB data). The off-row data node at page (1:35867), slot 0, text ID 94371840 is referenced by page (1:35555), slot 0, but was not seen in the scan.Msg 8928, Level 16, State 1, Line 1Object ID 373576369, index ID 1, partition ID 72057594075611136, alloc unit ID 72057594040549376 (type LOB data): Page (1:35868) could not be processed. See other errors for details.Msg 8965, Level 16, State 1, Line 1Table error: Object ID 373576369, index ID 1, partition ID 72057594075611136, alloc unit ID 72057594040549376 (type LOB data). The off-row data node at page (1:35868), slot 0, text ID 94371840 is referenced by page (1:35555), slot 0, but was not seen in the scan.Msg 8928, Level 16, State 1, Line 1Object ID 373576369, index ID 1, partition ID 72057594075611136, alloc unit ID 72057594040549376 (type LOB data): Page (1:35869) could not be processed. See other errors for details.Msg 8965, Level 16, State 1, Line 1Table error: Object ID 373576369, index ID 1, partition ID 72057594075611136, alloc unit ID 72057594040549376 (type LOB data). The off-row data node at page (1:35869), slot 0, text ID 94371840 is referenced by page (1:35555), slot 0, but was not seen in the scan.Msg 8928, Level 16, State 1, Line 1Object ID 373576369, index ID 1, partition ID 72057594075611136, alloc unit ID 72057594040549376 (type LOB data): Page (1:35870) could not be processed. See other errors for details.Msg 8965, Level 16, State 1, Line 1Table error: Object ID 373576369, index ID 1, partition ID 72057594075611136, alloc unit ID 72057594040549376 (type LOB data). The off-row data node at page (1:35870), slot 0, text ID 94371840 is referenced by page (1:35555), slot 0, but was not seen in the scan.Msg 8928, Level 16, State 1, Line 1Object ID 373576369, index ID 1, partition ID 72057594075611136, alloc unit ID 72057594040549376 (type LOB data): Page (1:35871) could not be processed. See other errors for details.Msg 8965, Level 16, State 1, Line 1Table error: Object ID 373576369, index ID 1, partition ID 72057594075611136, alloc unit ID 72057594040549376 (type LOB data). The off-row data node at page (1:35871), slot 0, text ID 94371840 is referenced by page (1:35555), slot 0, but was not seen in the scan.Msg 8928, Level 16, State 1, Line 1Object ID 373576369, index ID 1, partition ID 72057594075611136, alloc unit ID 72057594040549376 (type LOB data): Page (1:86184) could not be processed. See other errors for details.Msg 8965, Level 16, State 1, Line 1Table error: Object ID 373576369, index ID 1, partition ID 72057594075611136, alloc unit ID 72057594040549376 (type LOB data). The off-row data node at page (1:86184), slot 0, text ID 1445199872 is referenced by page (1:85657), slot 0, but was not seen in the scan.Msg 8928, Level 16, State 1, Line 1Object ID 373576369, index ID 1, partition ID 72057594075611136, alloc unit ID 72057594040549376 (type LOB data): Page (1:86185) could not be processed. See other errors for details.Msg 8965, Level 16, State 1, Line 1Table error: Object ID 373576369, index ID 1, partition ID 72057594075611136, alloc unit ID 72057594040549376 (type LOB data). The off-row data node at page (1:86185), slot 0, text ID 1445199872 is referenced by page (1:85657), slot 0, but was not seen in the scan.Msg 8928, Level 16, State 1, Line 1Object ID 373576369, index ID 1, partition ID 72057594075611136, alloc unit ID 72057594040549376 (type LOB data): Page (1:86186) could not be processed. See other errors for details.Msg 8965, Level 16, State 1, Line 1Table error: Object ID 373576369, index ID 1, partition ID 72057594075611136, alloc unit ID 72057594040549376 (type LOB data). The off-row data node at page (1:86186), slot 0, text ID 1445199872 is referenced by page (1:85657), slot 0, but was not seen in the scan.Msg 8928, Level 16, State 1, Line 1Object ID 373576369, index ID 1, partition ID 72057594075611136, alloc unit ID 72057594040549376 (type LOB data): Page (1:86187) could not be processed. See other errors for details.Msg 8965, Level 16, State 1, Line 1Table error: Object ID 373576369, index ID 1, partition ID 72057594075611136, alloc unit ID 72057594040549376 (type LOB data). The off-row data node at page (1:86187), slot 0, text ID 1445199872 is referenced by page (1:85657), slot 0, but was not seen in the scan.Msg 8928, Level 16, State 1, Line 1Object ID 373576369, index ID 1, partition ID 72057594075611136, alloc unit ID 72057594040549376 (type LOB data): Page (1:86188) could not be processed. See other errors for details.Msg 8965, Level 16, State 1, Line 1Table error: Object ID 373576369, index ID 1, partition ID 72057594075611136, alloc unit ID 72057594040549376 (type LOB data). The off-row data node at page (1:86188), slot 0, text ID 1445199872 is referenced by page (1:85657), slot 0, but was not seen in the scan.Msg 8928, Level 16, State 1, Line 1Object ID 373576369, index ID 1, partition ID 72057594075611136, alloc unit ID 72057594040549376 (type LOB data): Page (1:86189) could not be processed. See other errors for details.Msg 8965, Level 16, State 1, Line 1Table error: Object ID 373576369, index ID 1, partition ID 72057594075611136, alloc unit ID 72057594040549376 (type LOB data). The off-row data node at page (1:86189), slot 0, text ID 1445199872 is referenced by page (1:85657), slot 0, but was not seen in the scan.Msg 8928, Level 16, State 1, Line 1Object ID 373576369, index ID 1, partition ID 72057594075611136, alloc unit ID 72057594040549376 (type LOB data): Page (1:86190) could not be processed. See other errors for details.Msg 8965, Level 16, State 1, Line 1Table error: Object ID 373576369, index ID 1, partition ID 72057594075611136, alloc unit ID 72057594040549376 (type LOB data). The off-row data node at page (1:86190), slot 0, text ID 1445199872 is referenced by page (1:85657), slot 0, but was not seen in the scan.Msg 8928, Level 16, State 1, Line 1Object ID 373576369, index ID 1, partition ID 72057594075611136, alloc unit ID 72057594040549376 (type LOB data): Page (1:86191) could not be processed. See other errors for details.Msg 8965, Level 16, State 1, Line 1Table error: Object ID 373576369, index ID 1, partition ID 72057594075611136, alloc unit ID 72057594040549376 (type LOB data). The off-row data node at page (1:86191), slot 0, text ID 1445199872 is referenced by page (1:85657), slot 0, but was not seen in the scan.Msg 8928, Level 16, State 1, Line 1Object ID 373576369, index ID 1, partition ID 72057594075611136, alloc unit ID 72057594040549376 (type LOB data): Page (1:283812) could not be processed. See other errors for details.Msg 8939, Level 16, State 98, Line 1Table error: Object ID 373576369, index ID 1, partition ID 72057594075611136, alloc unit ID 72057594040549376 (type LOB data), page (1:283812). Test (IS_OFF (BUF_IOERR, pBUF->bstat)) failed. Values are 12716041 and -4.Msg 8965, Level 16, State 1, Line 1Table error: Object ID 373576369, index ID 1, partition ID 72057594075611136, alloc unit ID 72057594040549376 (type LOB data). The off-row data node at page (1:283812), slot 0, text ID 529661952 is referenced by page (1:283534), slot 0, but was not seen in the scan.Msg 8928, Level 16, State 1, Line 1Object ID 373576369, index ID 1, partition ID 72057594075611136, alloc unit ID 72057594040549376 (type LOB data): Page (1:283813) could not be processed. See other errors for details.Msg 8965, Level 16, State 1, Line 1Table error: Object ID 373576369, index ID 1, partition ID 72057594075611136, alloc unit ID 72057594040549376 (type LOB data). The off-row data node at page (1:283813), slot 0, text ID 529661952 is referenced by page (1:283534), slot 0, but was not seen in the scan.Msg 8928, Level 16, State 1, Line 1Object ID 373576369, index ID 1, partition ID 72057594075611136, alloc unit ID 72057594040549376 (type LOB data): Page (1:283814) could not be processed. See other errors for details.Msg 8965, Level 16, State 1, Line 1Table error: Object ID 373576369, index ID 1, partition ID 72057594075611136, alloc unit ID 72057594040549376 (type LOB data). The off-row data node at page (1:283814), slot 0, text ID 529661952 is referenced by page (1:283534), slot 0, but was not seen in the scan.Msg 8928, Level 16, State 1, Line 1Object ID 373576369, index ID 1, partition ID 72057594075611136, alloc unit ID 72057594040549376 (type LOB data): Page (1:283815) could not be processed. See other errors for details.Msg 8965, Level 16, State 1, Line 1Table error: Object ID 373576369, index ID 1, partition ID 72057594075611136, alloc unit ID 72057594040549376 (type LOB data). The off-row data node at page (1:283815), slot 0, text ID 529661952 is referenced by page (1:283534), slot 0, but was not seen in the scan.Msg 8928, Level 16, State 1, Line 1Object ID 373576369, index ID 1, partition ID 72057594075611136, alloc unit ID 72057594040549376 (type LOB data): Page (1:283816) could not be processed. See other errors for details.Msg 8965, Level 16, State 1, Line 1Table error: Object ID 373576369, index ID 1, partition ID 72057594075611136, alloc unit ID 72057594040549376 (type LOB data). The off-row data node at page (1:283816), slot 0, text ID 529661952 is referenced by page (1:283534), slot 0, but was not seen in the scan.Msg 8928, Level 16, State 1, Line 1Object ID 373576369, index ID 1, partition ID 72057594075611136, alloc unit ID 72057594040549376 (type LOB data): Page (1:283817) could not be processed. See other errors for details.Msg 8965, Level 16, State 1, Line 1Table error: Object ID 373576369, index ID 1, partition ID 72057594075611136, alloc unit ID 72057594040549376 (type LOB data). The off-row data node at page (1:283817), slot 0, text ID 529661952 is referenced by page (1:283534), slot 0, but was not seen in the scan.Msg 8928, Level 16, State 1, Line 1Object ID 373576369, index ID 1, partition ID 72057594075611136, alloc unit ID 72057594040549376 (type LOB data): Page (1:283818) could not be processed. See other errors for details.Msg 8965, Level 16, State 1, Line 1Table error: Object ID 373576369, index ID 1, partition ID 72057594075611136, alloc unit ID 72057594040549376 (type LOB data). The off-row data node at page (1:283818), slot 0, text ID 529661952 is referenced by page (1:283534), slot 0, but was not seen in the scan.Msg 8928, Level 16, State 1, Line 1Object ID 373576369, index ID 1, partition ID 72057594075611136, alloc unit ID 72057594040549376 (type LOB data): Page (1:283819) could not be processed. See other errors for details.Msg 8965, Level 16, State 1, Line 1Table error: Object ID 373576369, index ID 1, partition ID 72057594075611136, alloc unit ID 72057594040549376 (type LOB data). The off-row data node at page (1:283819), slot 0, text ID 529661952 is referenced by page (1:283534), slot 0, but was not seen in the scan.Msg 8928, Level 16, State 1, Line 1Object ID 373576369, index ID 1, partition ID 72057594075611136, alloc unit ID 72057594040549376 (type LOB data): Page (1:283820) could not be processed. See other errors for details.Msg 8965, Level 16, State 1, Line 1Table error: Object ID 373576369, index ID 1, partition ID 72057594075611136, alloc unit ID 72057594040549376 (type LOB data). The off-row data node at page (1:283820), slot 0, text ID 529661952 is referenced by page (1:283534), slot 0, but was not seen in the scan.Msg 8929, Level 16, State 1, Line 1Object ID 373576369, index ID 1, partition ID 72057594075611136, alloc unit ID 72057594087014400 (type In-row data): Errors found in off-row data with ID 94371840 owned by data record identified by RID = (1:11921:2)Msg 8929, Level 16, State 1, Line 1Object ID 373576369, index ID 1, partition ID 72057594075611136, alloc unit ID 72057594087014400 (type In-row data): Errors found in off-row data with ID 1445199872 owned by data record identified by RID = (1:11924:23)Msg 8929, Level 16, State 1, Line 1Object ID 373576369, index ID 1, partition ID 72057594075611136, alloc unit ID 72057594087014400 (type In-row data): Errors found in off-row data with ID 529661952 owned by data record identified by RID = (1:11944:13)CHECKDB found 0 allocation errors and 54 consistency errors in table 'AllDocStreams' (object ID 373576369).CHECKDB found 0 allocation errors and 70 consistency errors in database 'WSS_Content_5ce5ed6d-52b4-4eb9-a134-45fb513127fb'.repair_allow_data_loss is the minimum repair level for the errors found by DBCC CHECKDB (WSS_Content_5ce5ed6d-52b4-4eb9-a134-45fb513127fb).Kindly help me to fix this error!Thu, 26 Jan 2012 08:26:42 GMTGanshttp://www.sqlservercentral.com/Forums/Topic1187785-2893-1.aspxHi All,Recently our company had a server change, and therefore the computer domain name changed.Because of this, I can no longer access a database that was under the other domain name.Any idea how to go about solving this? I've checked for results on google from others with the same problem, but reinstalling/deleting the database isn't really helpful. And the other methods do not work.Here is the error message:The database TestDB is not accessible. (ObjectExplorer)------------------------------Program Location: at Microsoft.SqlServer.Management.UI.VSIntegration.ObjectExplorer.DatabaseNavigableItem.get_CanGetChildren() at Microsoft.SqlServer.Management.UI.VSIntegration.ObjectExplorer.NavigableItem.RequestChildren(IGetChildrenRequest request) at Microsoft.SqlServer.Management.UI.VSIntegration.ObjectExplorer.ExplorerHierarchyNode.BuildChildren(WaitHandle quitEvent)Many thanks for your help. Let me know if anything is unclear.CheersRixxe.Mon, 10 Oct 2011 03:42:46 GMTRixxehttp://www.sqlservercentral.com/Forums/Topic1287966-2893-1.aspxHI For AllI Upgrade Sql Server 2005 to Sql Server 2008R2When I Execute Drop Table Command I Give this Error:No catalog entry found for partition ID 281474980577280 in database 5. The metadata is inconsistent. Run DBCC CHECKDB to check for a metadata corruption.When I Run DBCC CHECKDB Again Give this Errorplease Help me.thanksMon, 23 Apr 2012 01:27:48 GMTfaravanihttp://www.sqlservercentral.com/Forums/Topic1280061-2893-1.aspxHi , A trigger that has been added by someone else before, also I've done on, modify, I get the following error.The error is as follows:Attempt to retrieve data for object failed for Server (name of server) (Microsoft.SQLServer.SMo)Additional Information:The database (database name) does not exist on the server. (Microsoft.SQLServer.SMo)Mon, 09 Apr 2012 03:18:29 GMTlsuersoyhttp://www.sqlservercentral.com/Forums/Topic1262060-2893-1.aspxHi, am new to SQL server. We recently had a drive failure on on of our SQL servers. SQLdump kept on putting out a backup file, each day, but this file had the same name. Our backup process kept on copying the file and so didn't generate an error. By the time we realised what was happening, the server had died. I was wondering if anyone might be able to shine some light on what exactly happened? Apart from the obvious :-)Thanks.Tue, 06 Mar 2012 04:29:22 GMTjamie.worsleyhttp://www.sqlservercentral.com/Forums/Topic1277353-2893-1.aspxHi, I am facing the issue on one of my database which is in suspect mode and in the error log following error is captured"Could not redo log record (6273:252:2), for transaction ID (0:1992992), on page (1:9), database 'xxxx' (database ID 10). Page: LSN = (6273:238:1), type = 13. Log: OpCode = 4, context 20, PrevPageLSN: (6273:250:1). Restore from a backup of the database, or repair the database."I followed these steps:1. Brought the DB on emergency state2. Single_user mode3. DBCC CHECKDB('xxxx', REPAIR_REBUILD)GObut that gives the following error "Msg 7901, Level 16, State 1, Line 1The repair statement was not processed. This level of repair is not supported when the database is in emergency mode."Please suggest what action need to be done.RohitTue, 03 Apr 2012 08:30:07 GMTgupta.rohithttp://www.sqlservercentral.com/Forums/Topic1210818-2893-1.aspxHi. I have a problem with transaction logs backup (SQL 2008 R2 Web edition). Full database backup completes fine, but transaction log backups started failing at some point with the following error:[quote]Failed:(-1073548784) Executing the query "BACKUP LOG [myDB] TO DISK = N'D:\\\\myDB\\myDB_backu..." failed with the following error: "BACKUP detected corruption in the database log. Check the errorlog for more information.BACKUP LOG is terminating abnormally.10 percent processed.20 percent processed.30 percent processed.". Possible failure reasons: Problems with the query, "ResultSet" property not set correctly, parameters not set correctly, or connection not established correctly.[/quote]I've done DBCC CHECKDB and it completed without errors (also tried DBCC CHECKDB WITH ALL_ERRORMSGS,NO_INFOMSGS).I've had this problem couple days ago and switching the DB from Full to Simple recovery mode and back helped for some time, but the problem reappeared.I'm not a DBA and from what I've read, most online articles seem to deal with corruption in the database, not in the log.Any hints on how to diagnose/remedy this further?ThanksWed, 23 Nov 2011 02:58:07 GMTRamblerhttp://www.sqlservercentral.com/Forums/Topic1267053-2893-1.aspxDB was originally a 2k5 version, but was restored to 2k8 well over a year ago and changed to compatibility of 10 at that time. It has been running fine up until a few days ago. Our maintenance plan does not error on the checkdb, but SQLdumps are created.Msg 8914, Level 16, State 1, Line 1Incorrect PFS free space information for page (1:1895363) in object ID 1998630163, index ID 0, partition ID 72057594045071360, alloc unit ID 72057594049200128 (type In-row data). Expected value 80_PCT_FULL, actual value 100_PCT_FULLPut the db in SUM and ran DBCC CHECKDB ('db', REPAIR_ALLOW_DATA_LOSS) Came back no errors reported.Ran DBCC CHECKDB WITH all_errormsgs, no_infomsgs again, and the same error came up. Did the process again, no errors either time. Ran the checkdb one more time after coming out of SUM and the error was back. I know that this is a benign error, but it's disconcerting that it comes back. Has anyone else come across this and found a resolution?Wed, 14 Mar 2012 13:51:27 GMTcheetah2399http://www.sqlservercentral.com/Forums/Topic1268055-2893-1.aspxHi,We tested the Trace Flag 610, and when only this one is activated, we got an error from a SSIS job:Error Description: SSIS Error Code DTS_E_OLEDBERROR. An OLE DBerror has occurred. Error code: 0x80004005.An OLE DB record is available. Source: "Microsoft SQL Server NativeClient 10.0" Hresult: 0x80004005 Description: "During undoing of alogged operation in database 'XXXX', an error occurred at log recordID (82254385:1023360:1). Typically, the specific failure is loggedpreviously as an error in the Windows Event Log service. Restore thedatabase or file from a backup, or repair the database.".An OLE DB record is available. Source: "Microsoft SQL Server NativeClient 10.0" Hresult: 0x80004005 Description: "The log for database'XXXX' is not available. Check the event log for related errormessages. Resolve any errors and restart the database.".An OLE DB record is available. Source: "Microsoft SQL Server NativeClient 10.0" Hresult: 0x80004005 Description: "During undoing of alogged operation in database 'XXXX', an error occurred at log recordID (82254385:3868989:319). Typically, the specific failure is loggedpreviously as an error in the Windows Event Log service. Restore thedatabase or file from a backup, or repair the database.".An OLE DB record is available. Source: "Microsoft SQL Server NativeClient 10.0" Hresult: 0x80004005 Description: "The log for database'XXXX' is not available. Check the event log for related errormessages. Resolve any errors and restart the database.".An OLE DB record is available. Source: "Microsoft SQL Server NativeClient 10.0" Hresult: 0x80004005 Description: "During undoing of alogged operation in database 'XXXX', an error occurred at log recordID (82254385:1024028:195). Typically, the specific failure is loggedpreviously as an error in the Windows Event Log service. Restore thedatabase or file from a backup, or repair the database.".An OLE DB record is available. Source: "Microsoft SQL Server NativeClient 10.0" Hresult: 0x80004005 Description: "An inconsistency wasdetected during an internal operation. Please contact technicalsupport.".An OLE DB record is available. Source: "Microsoft SQL Server NativeClient 10.0" Hresult: 0x80004005 Description: "Time-out occurredwhile waiting for buffer latch type 4 for page (9:1538572), databaseID 5.".The database cannot be opened. It has been marked SUSPECT by recovery.We got it on the Production Environment + Test Env., that means with different hardware.Then, is it possible it's a bug? Or do you have an idea?Thank youFri, 16 Mar 2012 01:41:14 GMThtiteufhttp://www.sqlservercentral.com/Forums/Topic1264872-2893-1.aspxcan any body help us to resolve the following problem with sql server 2008 sp2:The operating system returned error 21( failed to retrieve text fro this error. Reason:15105) to SQL server during a read at offset 0x0000000100e000 in file ' mdf file location' Additional messages in the SQL server error log and system event log may provide more detail. this is a severe system-level error condition that threatens database integrity and must be corrected immediately. complete a full database consistency check (DBCC CHECKDB). this error can be caused by many factors for more info see SQL server books.EventID: 823Sun, 11 Mar 2012 09:32:00 GMTrami izhimanhttp://www.sqlservercentral.com/Forums/Topic1260782-2893-1.aspxI got this error a couple of days ago and have tried some basic things to correct it, system restore, updating to new Service pack neither of which has worked. I've posted this problem on several other forums and I am not getting any feedback. I am using MS Sql server 2008 express edition with asp.net/visual web developer 2008 express edition. The website which is on a stand alone computer has been working just fine until this came up and now I'm stuck. Any help would be greatly appreciated. I am very new to this so I don't understand a lot of the below.Server Error in '/WebSite2' Application. ________________________________________Unable to translate Unicode character \uD8FF at index 0 to specified code page. Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code. Exception Details: System.Text.EncoderFallbackException: Unable to translate Unicode character \uD8FF at index 0 to specified code page.Source Error: An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below. Stack Trace: [EncoderFallbackException: Unable to translate Unicode character \uD8FF at index 0 to specified code page.] System.Text.EncoderExceptionFallbackBuffer.Fallback(Char charUnknown, Int32 index) +155 System.Text.EncoderFallbackBuffer.InternalFallback(Char ch, Char*& chars) +275 System.Text.UTF8Encoding.GetByteCount(Char* chars, Int32 count, EncoderNLS baseEncoder) +7680574 System.Text.UTF8Encoding.GetByteCount(String chars) +43 System.IO.BinaryWriter.Write(String value) +38 System.Web.UI.ObjectStateFormatter.SerializeValue(SerializerBinaryWriter writer, Object value) +1281[ArgumentException: Error serializing value '�က䙊䙉Āā怀怀硅晩䥉*ĎĖďĢĐĨĒ ĚĴěļĨ ıńIJŖȓ 蝩 Ųꐁ ꐂ ꐃ ꐄŪꐅ Fꐆ ꐇ ꐈ ꐉ ꐊ ꐌ ۀ†††††需䥎佋N佃䱏䥐⁘ㅌ退ĬĬ佃䱏䥐⁘ㅌ†ㅖ㌮頀〲〱ㄺ㨱㘰〠㨳㈱㔺8d芚ʌ芝ʔ蠢 ԅ蠧 2ԅ退 ㈰〲逃ʜ逄ʰ鄁 ȁ 鄂˄鈄ˌ鈅˔鈇 鈈 鈉 Y鈊˜鉼͜ˤ銆€ـꀀ ㄰〰ꀁ Ćꀂ ଀ꀃ ࡀꌀḃ⻳ꌁࠁDž#〲〱ㄺ㨱㘰〠㨳㈱㔺8〲〱ㄺ㨱㘰〠㨳㈱㔺8 s楎潫n䥉* Ȁ ņ ŌŔŢŪŲźƂ ̜(Ɗ€Ʋ‚ǀ…ǎ†ǖˆ ਁЀǞ”•Ǯ—ĀǴ› œ˴ ž ̈Ÿ佃佌R低䵒䱁啁佔††††啁佔†䙁䌭†䕒ⵄ奅EᰳϨ啁佔†††††††††† ††††††††† 啁佔†††† 䙏⁆††††dd佐呒䅒呉††† 䙏⁆㄰〰䅆䕃倭䥒剏呉⁙䙁† ă ĚͶě;Ĩ ȁ ††††††††††††††††††††††††††††††††††††††††††††††††††††††††††† ă Ě܎ěܖĨ ȁ ܞȂ აĬĬ��萀ᄀഌഏᄋฏᐏᄓᨕᴬ᠚ᨘ✶
䀬䐹㽃㸹䜽材䝗慌㵍夾婺橡獭獴噅蝾災枆獱Ůᐓᨔᨗᴴ㐝䥮䤾湮湮湮湮湮湮湮湮湮湮湮湮湮湮湮湮湮湮湮湮湮湮湮湮湮샿ᄀxΠ℁Ȁđᄃ！DŽ¢ĀąāāĀ̂...' of type 'System.String.'] System.Web.UI.ObjectStateFormatter.SerializeValue(SerializerBinaryWriter writer, Object value) +3319 System.Web.UI.ObjectStateFormatter.Serialize(Stream outputStream, Object stateGraph) +110 System.Web.UI.ObjectStateFormatter.Serialize(Object stateGraph) +57 System.Web.UI.ObjectStateFormatter.System.Web.UI.IStateFormatter.Serialize(Object state) +4 System.Web.UI.Util.SerializeWithAssert(IStateFormatter formatter, Object stateGraph) +37 System.Web.UI.HiddenFieldPageStatePersister.Save() +79 System.Web.UI.Page.SavePageStateToPersistenceMedium(Object state) +105 System.Web.UI.Page.SaveAllState() +236 System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +1099Fri, 02 Mar 2012 07:16:53 GMTmary.canestorphttp://www.sqlservercentral.com/Forums/Topic1261610-2893-1.aspxMonday greeted me with a lovely message from a production cluster:DBCC CHECKDB ([master]) WITH NO_INFOMSGS, ALL_ERRORMSGS, DATA_PURITYMsg 2570, Level 16, State 2, Line 1Page (1:450), slot 51 in object ID 58, index ID 1, partition ID281474980511744, alloc unit ID 281474980511744(type "In-row data"). Column "name" value is out of range for datatype "nvarchar". Update column to a legal value.CHECKDB found 0 allocation errors and 1 consistency errors in table'sys.sysbinobjs' (object ID 58).CHECKDB found 0 allocation errors and 1 consistency errors in database 'master'.This is in a system table. Is there a way to fix the value of the field or otherwise resolve without going to the trouble of restoring master from backup?Thanks!Mon, 05 Mar 2012 08:23:11 GMTGaius Baltarhttp://www.sqlservercentral.com/Forums/Topic1256378-2893-1.aspxHi, can anyone help me how to handle if there any change in source field name and table name without changing my package. I heard that there facade concept, but not sure how it works.Wed, 22 Feb 2012 19:59:39 GMTkdinukhttp://www.sqlservercentral.com/Forums/Topic1254255-2893-1.aspxOur nightly check db failed last night because of a corrupted page in one of the table. Following are the details:DBCC results for 'TableX'.Msg 8928, Level 16, State 1, Line 1Object ID 1211151360, index ID 1, partition ID 72057606682378240, alloc unit ID 72057606848970752 (type In-row data): Page (1:13175266) could not be processed. See other errors for details.Msg 8939, Level 16, State 98, Line 1Table error: Object ID 1211151360, index ID 1, partition ID 72057606682378240, alloc unit ID 72057606848970752 (type In-row data), page (1:13175266). Test (IS_OFF (BUF_IOERR, pBUF->bstat)) failed. Values are 12716041 and -4.Msg 8976, Level 16, State 1, Line 1Table error: Object ID 1211151360, index ID 1, partition ID 72057606682378240, alloc unit ID 72057606848970752 (type In-row data). Page (1:13175266) was not seen in the scan although its parent (1:4790005) and previous (1:13175265) refer to it. Check any previous errors.Msg 8978, Level 16, State 1, Line 1Table error: Object ID 1211151360, index ID 1, partition ID 72057606682378240, alloc unit ID 72057606848970752 (type In-row data). Page (1:13175267) is missing a reference from previous page (1:13175266). Possible chain linkage problem.There are 109395 rows in 42212 pages for object 'TableX'CHECKDB found 0 allocation errors and 4 consistency errors in table 'TableX' (object ID 1211151360).This is a SQL 2008 R2 server and we do have the option to restore the damaged page from backup. Paul Randal has this beautiful blog on that:http://blogs.msdn.com/b/sqlserverstorageengine/archive/2007/01/18/fixing-damaged-pages-using-page-restore-or-manual-inserts.aspx We have the full backup of the DB from a couple of days with teh clean page, we also have all the T log backups from that full backup until this point to successfully complete the page restore. I even tested this on my test server and it works fine.But the concern I have to do a page restore on my production database is that this table on my production database is replicated (Transactional) to our reporting instance. I am not sure what impact the page restore and applying all the T Logs has on replication. Does any one know of any possible impact on replication??Fri, 17 Feb 2012 17:58:10 GMTsqlsatyamhttp://www.sqlservercentral.com/Forums/Topic1253118-2893-1.aspxI just to the log shipping for the CnSx database, I get the below errors in the reporting server,*** Error: The log backup file '\\islrptsql\log-ship-backups\CnSx_20120214143000.trn' was verified but could not be applied to secondary database 'CnSx'.(Microsoft.SqlServer.Management.LogShipping) ***The restore operation completed with errors. Secondary ID: 'ab6bda6f-24fe-4065-b2d6-876acf911efd'Thanks,DevThu, 16 Feb 2012 07:18:08 GMTdsohalhttp://www.sqlservercentral.com/Forums/Topic1239942-2893-1.aspxHi, we've recently encountered a corruption situation and I'm testing the latest backup to make sure it is okay. Based on the output, I think we can just restore table 'xxx' (by restoring the database on another server and they copying the table over) since most of the errors refer to it, but I'm not positive if that would fix the two consistency errors mentioned. Below is the DBCC output. Any help would be greatly appreciated!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 (27:59906942) 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 (27:59906943) 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.Msg 8928, Level 16, State 1, Line 1Object ID 754101727, index ID 1, partition ID 72057594043170816, alloc unit ID 72057594047365120 (type In-row data): Page (27:59906941) could not be processed. See other errors for details.Msg 8939, Level 16, State 98, Line 1Table error: Object ID 754101727, index ID 1, partition ID 72057594043170816, alloc unit ID 72057594047365120 (type In-row data), page (27:59906941). Test (IS_OFF (BUF_IOERR, pBUF->bstat)) failed. Values are 12716041 and -4.Msg 8976, Level 16, State 1, Line 1Table error: Object ID 754101727, index ID 1, partition ID 72057594043170816, alloc unit ID 72057594047365120 (type In-row data). Page (27:59906941) was not seen in the scan although its parent (27:59907053) and previous (27:59906940) refer to it. Check any previous errors.Msg 8928, Level 16, State 1, Line 1Object ID 754101727, index ID 1, partition ID 72057594043170816, alloc unit ID 72057594047365120 (type In-row data): Page (27:59906942) could not be processed. See other errors for details.Msg 8980, Level 16, State 1, Line 1Table error: Object ID 754101727, index ID 1, partition ID 72057594043170816, alloc unit ID 72057594047365120 (type In-row data). Index node page (27:59907053), slot 152 refers to child page (27:59906942) and previous child (27:59906941), but they were not encountered.Msg 8928, Level 16, State 1, Line 1Object ID 754101727, index ID 1, partition ID 72057594043170816, alloc unit ID 72057594047365120 (type In-row data): Page (27:59906943) could not be processed. See other errors for details.Msg 8980, Level 16, State 1, Line 1Table error: Object ID 754101727, index ID 1, partition ID 72057594043170816, alloc unit ID 72057594047365120 (type In-row data). Index node page (27:59907053), slot 153 refers to child page (27:59906943) and previous child (27:59906942), but they were not encountered.Msg 8978, Level 16, State 1, Line 1Table error: Object ID 754101727, index ID 1, partition ID 72057594043170816, alloc unit ID 72057594047365120 (type In-row data). Page (27:59906944) is missing a reference from previous page (27:59906943). Possible chain linkage problem.CHECKDB found 0 allocation errors and 8 consistency errors in table 'xxx' (object ID 754101727).CHECKDB found 0 allocation errors and 10 consistency errors in database 'yyy'.repair_allow_data_loss is the minimum repair level for the errors found by DBCC CHECKDB (yyy)Sun, 22 Jan 2012 12:10:30 GMTGary Hineshttp://www.sqlservercentral.com/Forums/Topic1218872-2893-1.aspxI am running SQL Server 2008 R2 on a machine that we have set up a Data Collector MDW on. All of the other servers sending data back are either 2008 R2 SP1 or 2008 SP2.This morning I found that some jobs on the MDW server were hung. When I fixed the issue, I noticed that I have a huge time gap in my Data Collector window from the night before until I fixed the issue this morning.Is there a way to reprocess the missing data or reconfigure Data Collector so this doesn't happen again? I'd like to know that if the MDW server is tied up or unavailable that the other servers will retain the data until it can be successfully processed.Just a note, the other servers did not report a failure in their upload jobs. Does this mean the data was successfully sent and it's sitting in the MDW database somewhere?Thanks,John*** UPDATE ***It looks like all of the collection jobs were cancelled. That would explain why the data wasn't getting processed. I had to re-run them all and the data started coming in. I have gaps for the duration that the jobs didn't run. The strange part is, on all of my servers almost every collection job was marked cancelled after approximately 23 hours.*************Any reason why the collection jobs would all be cancelled after about 23 hours?Is there any way to make sure if this happens again I can reprocess the data?Thu, 08 Dec 2011 12:01:29 GMTJohnnyDBAhttp://www.sqlservercentral.com/Forums/Topic1235195-2893-1.aspxI've looked for the last two days trying to figure this out and no other solutions or posts seem to work or apply to my problem.I have recreated this SQL Express database three times. The first time, I scripted it from another database, and the last two times, I started from scratch and still get the same error.I am using this query:SELECT dbo.shops.bizID, dbo.shops.bizName, dbo.shops.bizPhone, dbo.shops.bizURL, dbo.shops.bizLogoFROM dbo.bizInCat INNER JOIN dbo.Category ON (dbo.bizInCat.catID = dbo.Category.catID) INNER JOIN dbo.shops ON (dbo.bizInCat.bizID = dbo.shops.bizID)WHERE dbo.shops.bizState = @state AND dbo.shops.bizCity = @city AND dbo.shops.bizActive = 'True' AND dbo.Category.catName = @categoryI KNOW that the columns bizState and bizCity exist. If I run the query in SSMS either on my local machine, or on the server, it works. It also worked when I plugged it into MS SQL Code Factory. But it will not work when ran in visual web developer, or running the application in the production environment. I always get the Invalid Column Name error for bizState and bizCity. If I remove those two constraints from the where clause, it works in both web developer and live on the production server.Can anyone explain to me what is going on with these two columns? I've tried Ctrl+Shift+R, rebooting the server, recreating the DataSet in developer and nothing seems to work. This is driving me nuts! It's a pretty simple app and database query!Thanks in advance...Thu, 12 Jan 2012 13:06:24 GMTdcwhitsonhttp://www.sqlservercentral.com/Forums/Topic1232926-2893-1.aspxHi,Two months back Installed SQL server 2008 enterprise edition in PC based server.. Now database running with consistency error.. Could anyone suggestion me, how to resolve this error? DBCC Checkdb 'dbname' with data_purityResultMsg 8928, Level 16, State 1, Line 1Object ID 485576768, index ID 0, partition ID 72057594040745984, alloc unit ID 72057594041794560 (type In-row data): Page (1:425) could not be processed. See other errors for details.Msg 8939, Level 16, State 98, Line 1Table error: Object ID 485576768, index ID 0, partition ID 72057594040745984, alloc unit ID 72057594041794560 (type In-row data), page (1:425). Test (IS_OFF (BUF_IOERR, pBUF->bstat)) failed. Values are 12716041 and -4.SQL Error Log and system Event ViewerMessageSQL Server detected a logical consistency-based I/O error: incorrect checksum (expected: 0xbfc9c6fa; actual: 0x9fc9c6fa). It occurred during a read of page (1:425) in database ID 5 at offset 0x00000000352000 in file 'D:\Program Files\Microsoft SQL Server\MSSQL10.MSSQLSERVER\MSSQL\DATA\HWDATA7.mdf'. Additional messages in the SQL Server error log or system event log may provide more detail. This is a severe error condition that threatens database integrity and must be corrected immediately. Complete a full database consistency check (DBCC CHECKDB). This error can be caused by many factors; for more information, see SQL Server Books Online.ThanksanandaMon, 09 Jan 2012 23:26:44 GMTananda.murugesanhttp://www.sqlservercentral.com/Forums/Topic1228577-2893-1.aspxHi All,I am just curious to know is there anyway we can track down who has truncated a particular table in SQL Server 2008 R2? I would require this information as part of some need in my project.Thanks,SriniFri, 30 Dec 2011 19:58:45 GMTMSBI Learnerhttp://www.sqlservercentral.com/Forums/Topic1218332-2893-1.aspxHi-- Thanks in advance for the help!I'm getting integrity issues after I migrate a DB from SQL Server 2000 to SQL Server 2008 R2.When I run DBCC CHECKDB on the original 2K db, I get no errors. Then I tried DBCC CHECKCATALOG and got a bunch of objects that do "not match between 'SYSREFERENCES' and 'SYSINDEXES'." I'm not sure how far the backups go. Assuming I don't have any non-corrupt backups, what are my options here? I've read that it's easier to fix the issues on 2k?Thanks!2KR2 DBCC CHECKDB outpout: Msg 8992, Level 16, State 1, Line 1 Check Catalog Msg 3853, State 1: Attribute (referenced_object_id=27147142,key_index_id=2) of row (object_id=1052582838) in sys.foreign_keys does not have a matching row (object_id=27147142,index_id=2) in sys.indexes. Msg 8992, Level 16, State 1, Line 1 Check Catalog Msg 3853, State 1: Attribute (referenced_object_id=748581755,key_index_id=2) of row (object_id=828582040) in sys.foreign_keys does not have a matching row (object_id=748581755,index_id=2) in sys.indexes. Msg 8992, Level 16, State 1, Line 1 Check Catalog Msg 3853, State 1: Attribute (referenced_object_id=748581755,key_index_id=2) of row (object_id=844582097) in sys.foreign_keys does not have a matching row (object_id=748581755,index_id=2) in sys.indexes. Msg 8992, Level 16, State 1, Line 1 Check Catalog Msg 3853, State 1: Attribute (referenced_object_id=914154352,key_index_id=2) of row (object_id=506133244) in sys.foreign_keys does not have a matching row (object_id=914154352,index_id=2) in sys.indexes. Msg 8992, Level 16, State 1, Line 1 Check Catalog Msg 3853, State 1: Attribute (referenced_object_id=914154352,key_index_id=2) of row (object_id=522133301) in sys.foreign_keys does not have a matching row (object_id=914154352,index_id=2) in sys.indexes. Msg 8992, Level 16, State 1, Line 1 Check Catalog Msg 3853, State 1: Attribute (referenced_object_id=914154352,key_index_id=2) of row (object_id=1010154694) in sys.foreign_keys does not have a matching row (object_id=914154352,index_id=2) in sys.indexes. Msg 8992, Level 16, State 1, Line 1 Check Catalog Msg 3853, State 1: Attribute (referenced_object_id=914154352,key_index_id=2) of row (object_id=1042154808) in sys.foreign_keys does not have a matching row (object_id=914154352,index_id=2) in sys.indexes. Msg 8992, Level 16, State 1, Line 1 Check Catalog Msg 3853, State 1: Attribute (referenced_object_id=914154352,key_index_id=2) of row (object_id=1723921263) in sys.foreign_keys does not have a matching row (object_id=914154352,index_id=2) in sys.indexes. Msg 8992, Level 16, State 1, Line 1 Check Catalog Msg 3853, State 1: Attribute (referenced_object_id=964914509,key_index_id=2) of row (object_id=686989874) in sys.foreign_keys does not have a matching row (object_id=964914509,index_id=2) in sys.indexes. Msg 8992, Level 16, State 1, Line 1 Check Catalog Msg 3853, State 1: Attribute (referenced_object_id=1778821399,key_index_id=2) of row (object_id=1084582952) in sys.foreign_keys does not have a matching row (object_id=1778821399,index_id=2) in sys.indexes. Msg 8992, Level 16, State 1, Line 1 Check Catalog Msg 3853, State 1: Attribute (referenced_object_id=1904061869,key_index_id=2) of row (object_id=1936061983) in sys.foreign_keys does not have a matching row (object_id=1904061869,index_id=2) in sys.indexes. Msg 8992, Level 16, State 1, Line 1 Check Catalog Msg 3853, State 1: Attribute (referenced_object_id=2092586543,key_index_id=2) of row (object_id=73103351) in sys.foreign_keys does not have a matching row (object_id=2092586543,index_id=2) in sys.indexes. Msg 8992, Level 16, State 1, Line 1 Check Catalog Msg 3853, State 1: Attribute (referenced_object_id=2092586543,key_index_id=2) of row (object_id=1739921320) in sys.foreign_keys does not have a matching row (object_id=2092586543,index_id=2) in sys.indexes. CHECKDB found 0 allocation errors and 13 consistency errors not associated with any single object. Msg 2508, Level 16, State 3, Line 1 The In-row data RSVD page count for object "tblUnit_bak2", index ID 0, partition ID 32571823816704, alloc unit ID 32571823816704 (type In-row data) is incorrect. Run DBCC UPDATEUSAGE. CHECKDB found 0 allocation errors and 1 consistency errors in table 'tblUnit_bak2' (object ID 497006589). CHECKDB found 0 allocation errors and 14 consistency errors in database 'XXXXXX'.Wed, 07 Dec 2011 18:34:42 GMTjacobbdrewhttp://www.sqlservercentral.com/Forums/Topic1206445-2893-1.aspxDear All,Today morning, i have encountered this type of error message when i try to delete one record. I check all the foreign key integrity. The Query is as below: [code="plain"]Delete from Table1 Where Id = 1234[/code] [b]Msg 407, Level 16, State 1, Line 1Internal error. The string routine in file e:\sql10_main_t\sqltdbms\storeng\dfs\startup\dstream.cpp, line 792 failed with HRESULT 0x8007007a.Msg 8630, Level 16, State 1, Line 1Internal Query Processor Error: The query processor encountered an unexpected error during execution.[/b]I don't know what to do now.Wed, 16 Nov 2011 00:33:24 GMTKrishnrajhttp://www.sqlservercentral.com/Forums/Topic1205520-2893-1.aspx[b]Use this at your own risk![/b]My issue happened in a test enviroment of mine where I could restore, so use with caution! I am not sure if this was the best solution or not, but I ran across did the folowing steps to resolve this issue:"Table error: The orphaned file "00096072-00000068-0003" was found in the FILESTREAM directory ID 8bdded92-3be3-46ed-8fc6-7e2c862b5bc1 for object ID 2036970383, index ID 1, partition ID 72057594459521024, column ID 4Generic error: Table error: The orphaned file 'FILE' was found in the Filestream directory for object ID O_ID, index ID I_ID, partition ID PN_ID, column ID C_IDThe issue is there are files left over in the FileStream directory that are not in the database for this particular table. I did the following and it worked:1. Backed up the database2. Scripted all the data in the FILESTREAM table and saved an insert statement to recreate the data.3. Moved the contents of the "8bdded92-3be3-46ed-8fc6-7e2c862b5bc1" directory to a backup location.4. Deleted all the contents in the FILESTREAM directory "8bdded92-3be3-46ed-8fc6-7e2c862b5bc1"5. Reran the insert script.Thankfully, I only have one table that has FILESTREAM enabled. If you have multiple tables, I am not sure if they are put into a separte directory or not, so use caution with this workaround!Mon, 14 Nov 2011 12:59:53 GMTbpportman 52825http://www.sqlservercentral.com/Forums/Topic1202511-2893-1.aspxI have DBCC consistency check failure on one my DB since it was migrated from 2k. It boils down to the following :[code="sql"]Msg 3853, Level 16, State 1, Line 1Attribute (object_id=780685979) of row (object_id=780685979,column_id=1) in sys.columns does not have a matching row (object_id=780685979) in sys.objects.Msg 3853, Level 16, State 1, Line 1Attribute (object_id=780685979) of row (object_id=780685979,column_id=2) in sys.columns does not have a matching row (object_id=780685979) in sys.objects.Msg 3853, Level 16, State 1, Line 1Attribute (object_id=780685979) of row (object_id=780685979,column_id=3) in sys.columns does not have a matching row (object_id=780685979) in sys.objects.Msg 3853, Level 16, State 1, Line 1Attribute (object_id=780685979) of row (object_id=780685979,column_id=4) in sys.columns does not have a matching row (object_id=780685979) in sys.objects.Msg 3853, Level 16, State 1, Line 1Attribute (object_id=780685979) of row (object_id=780685979,column_id=5) in sys.columns does not have a matching row (object_id=780685979) in sys.objects.Msg 3853, Level 16, State 1, Line 1Attribute (object_id=780685979) of row (object_id=780685979,column_id=6) in sys.columns does not have a matching row (object_id=780685979) in sys.objects.Msg 3853, Level 16, State 1, Line 1Attribute (parent_object_id=780685979) of row (object_id=796686036) in sys.objects does not have a matching row (object_id=780685979) in sys.objects.Msg 3853, Level 16, State 1, Line 1Attribute (parent_object_id=780685979) of row (object_id=812686093) in sys.objects does not have a matching row (object_id=780685979) in sys.objects.DBCC execution completed. If DBCC printed error messages, contact your system administrator.[/code]More exactly 6 of the sys.columns rows refer to a parent object ID called 780685979 which apparently does not exist in sys.objects.So I tried the following [code="sql"]INSERT INTO sys.objects VALUES('myobjectname',780685979,NULL,1,0,'U','USER_TABLE','2002-01-02 10:17:42.247','2002-01-02 10:17:42.247',0,0,0)Msg 259, Level 16, State 1, Line 1Ad hoc updates to system catalogs are not allowed.sp_configure "Allow Updates", 1GO--Configuration option 'allow updates' changed from 1 to 1. Run the RECONFIGURE statement to install.reconfigure with override GO--Command(s) completed successfully.[/code]The thing is when I configure the server to allow updates , it says successfully completed, but when I to re-run the insert statement it errors out again with same error[code="sql"]Msg 259, Level 16, State 1, Line 1Ad hoc updates to system catalogs are not allowed.[/code]What are my options here, how do I get this row inserted into sys.objects so that it passes the consistency check ?I heard we can do it thru a dedicated admin connection, is it so ? if so how? Tue, 08 Nov 2011 15:07:18 GMTMinnesota - Viking http://www.sqlservercentral.com/Forums/Topic1197653-2893-1.aspxI'm not sure if the database is corrupted but am having issues getting a backups to work. Error: The driver detected a controller error on \device\harddisk0\DR0.In SQL log: The operating system returned error 1117(the request could not be performed because of an i/o device error) to SQL Server during a read at offset 0x....And: Read on 'D:\...mdf' failed 1117(the request could not be performed because of an i/o device error)Our server administrator found an error with the drive and swapped it out. I'm still haveing i/o errors for two of the databases though. Are they corrupt? How can I tell if they should be restored? I there a setting somewhere that would have to be set after the drive swap?I ran dbcc checkdb on the 2 databases and they also have a 1117 error.Any help or advice on this? Thanks very much.Fri, 28 Oct 2011 13:41:52 GMTDenise McMillanhttp://www.sqlservercentral.com/Forums/Topic1194122-2893-1.aspxHello,I am working on a corrupt database I downloaded it from Sqlskills.com named "CorruptDemoRestoreOrRepair.bak." Below is the errors returned from DBCC CHECKDB WITH ALL_ERRORMSGS, NO_INFOMSGS. Am using SQL Server 2008 R2.I've read articles where people extract/copy data from the corrupt table into a new one/database. I've tried doing an EXPORT Data, COPY Database, INSERT Into, but they all bomb due I:O error messages. How did they accomplish this?Running a DBCC repair_allow_data_loss fixes things, but this is a last resort[quote]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:158) contains an incorrect page ID in its page header. The PageId in the page header = (0:0).CHECKDB found 0 allocation errors and 1 consistency errors not associated with any single object.Msg 8928, Level 16, State 1, Line 1Object ID 2073058421, index ID 1, partition ID 72057594038386688, alloc unit ID 72057594042384384 (type In-row data): Page (1:158) could not be processed. See other errors for details.Msg 8976, Level 16, State 1, Line 1Table error: Object ID 2073058421, index ID 1, partition ID 72057594038386688, alloc unit ID 72057594042384384 (type In-row data). Page (1:158) was not seen in the scan although its parent (1:154) and previous (1:157) refer to it. Check any previous errors.Msg 8978, Level 16, State 1, Line 1Table error: Object ID 2073058421, index ID 1, partition ID 72057594038386688, alloc unit ID 72057594042384384 (type In-row data). Page (1:159) is missing a reference from previous page (1:158). Possible chain linkage problem.CHECKDB found 0 allocation errors and 3 consistency errors in table 'sales' (object ID 2073058421).CHECKDB found 0 allocation errors and 4 consistency errors in database 'Demo'.repair_allow_data_loss is the minimum repair level for the errors found by DBCC CHECKDB (Demo).[/quote]Thu, 20 Oct 2011 23:38:51 GMTinvulnarable27http://www.sqlservercentral.com/Forums/Topic1194301-2893-1.aspxI searched almost everything in google on Heat Spot reports using SSRS 2008 but did'nt find any good tutorials.Can anyone help me to get tutorials on HeatSpot report using SSRS 2008.Fri, 21 Oct 2011 05:59:23 GMTsandippanihttp://www.sqlservercentral.com/Forums/Topic1190683-2893-1.aspxHi AllGetting this error running an INSERT statement with (TABLOCK). Resulting in a Stack dump. The table is NOT compressed/replicated, however, it is partitioned. Works if you remove TABLOCK hint. CHECKDB does not reveal any errorsUsing SQL Server 2008 R2 build 10.50.1600.1 (no Service Packs).Error log excerpts :A system assertion check has failed. Check the SQL Server error log for details. Typically, an assertion failure is caused by a software bug or data corruption. To check for database corruption, consider running DBCC CHECKDB. If you agreed to send dumps to Microsoft during setup, a mini dump will be sent to Microsoft. An update might be available from Microsoft in the latest Service Pack or in a QFE from Technical Support.SQL Server Assertion: File: <pageref.cpp>, line=922 Failed Assertion = 'IS_OFF (BUF_MINLOGGED, m_buf->bstat) || pageModifyType != PageModifyType_Contents || GetPagePtr ()->IsTextPage ()'. This error may be timing-related. If the error persists after rerunning the statement, use DBCC CHECKDB to check the database for structural integrity, or restart the server to ensure in-memory data structures are not corrupted. Anybody got any ideas ?CheersPreetFri, 14 Oct 2011 10:35:34 GMTPreet_Shttp://www.sqlservercentral.com/Forums/Topic1175985-2893-1.aspxHello All,I have a nice small database that I have recently moved from 2000 to 2008 R2, and as part of our process I have run DBCC CHECKDB with DATA_PURITY to look for problems. On this particular database I have found a few, which shouldn't be a big deal to clean out. However, I am looking for a little better understanding of exactly what I am seeing.Note that this is a third party app, so nothing I can do about the design!Here is the DDL for the table (Heap, no indexes, no keys):[code="sql"]CREATE TABLE [dbo].[FORMLAYOUTSPECS]( [TABLENAME] [char](25) NOT NULL, [FIELDNAME] [char](25) NOT NULL, [FIELDISKEYFIELD] [numeric](2, 0) NOT NULL, [FIELDAUTONUMBER] [numeric](3, 0) NULL, [FIELDTABSTOP] [numeric](2, 0) NULL, [FIELDTABINDEX] [numeric](10, 0) NULL, [FIELDTYPE] [char](10) NULL, [FIELDTAG] [char](25) NULL, [FIELDLENGTH] [numeric](10, 0) NULL, [FIELDMASK] [char](25) NULL, [FIELDSAVEASMASK] [numeric](2, 0) NULL, [FIELDTOP] [numeric](10, 0) NULL, [FIELDLEFT] [numeric](10, 0) NULL, [FIELDWIDTH] [numeric](10, 0) NULL, [FIELDHEIGHT] [numeric](10, 0) NULL, [FIELDCOLOR] [varchar](10) NULL, [FIELDTOOLTIP] [varchar](100) NULL, [FIELDQUERYTYPE] [varchar](10) NULL, [FIELDPRIORITY] [numeric](2, 0) NULL, [FIELDVARIANCE] [numeric](3, 0) NULL, [FIELDUSED] [numeric](2, 0) NULL, [FIELDVISIBLE] [numeric](2, 0) NULL, [FIELDENABLED] [numeric](3, 0) NULL, [FIELDLOCKED] [numeric](3, 0) NULL, [FIELDALIGNMENT] [varchar](10) NULL, [FIELDMULTILINE] [numeric](2, 0) NULL, [FIELDSCROLLBAR] [numeric](2, 0) NULL, [FIELDBOLD] [numeric](3, 0) NULL, [FIELDFONT] [varchar](25) NULL, [FIELDFONTSIZE] [numeric](3, 0) NULL, [FIELDLOOKUPTABLENAME] [varchar](25) NULL, [FIELDLOOKUPCODE] [varchar](25) NULL, [FIELDLOOKUPDESC] [varchar](100) NULL, [FIELDDATASOURCE] [varchar](100) NULL, [FIELDQUERY] [varchar](25) NULL, [FIELDQUERYMIN] [varchar](25) NULL, [FIELDQUERYMAX] [varchar](25) NULL, [FIELDLABEL] [varchar](25) NULL, [FIELDLABELVISIBLE] [numeric](2, 0) NULL, [FIELDLABELTOP] [numeric](10, 0) NULL, [FIELDLABELLEFT] [numeric](10, 0) NULL, [FIELDLABELWIDTH] [numeric](10, 0) NULL, [FIELDLABELCOLOR] [numeric](10, 0) NULL, [FIELDRECORDSOURCE] [varchar](25) NULL, [FIELDSHOWINGRID] [numeric](3, 0) NULL, [FIELDROW] [numeric](3, 0) NULL, [FIELDALTKEY] [numeric](3, 0) NULL, [FIELDALTKEYPOSITION] [numeric](3, 0) NULL, [FIELDMUSTENTER] [varchar](10) NULL, [FIELDBLANKMASKVALUE] [varchar](25) NULL, [FIELDCOPYNEW] [numeric](2, 0) NULL, [FIELDLINKTABLE] [varchar](50) NULL, [FIELDLINKKEY] [varchar](50) NULL, [FIELDLINKDISPLAY] [varchar](50) NULL, [FIELDUCASE] [numeric](2, 0) NULL, [FIELDSTOREASCODE] [varchar](25) NULL, [FIELDNAMETOSTORE] [varchar](25) NULL) ON [PRIMARY][/code]Here is the relevant portion of DBCC CHECKDB with DATA_PURITY:You'll have to imagine it in red, I can't get the font color working :-)[quote]Msg 2570, Level 16, State 3, Line 2Page (1:2064), slot 9 in object ID 706101556, index ID 0, partition ID 46275071574016, alloc unit ID 46275071574016 (type "In-row data"). Column "FIELDTABSTOP" value is out of range for data type "numeric". Update column to a legal value.Msg 2570, Level 16, State 3, Line 2Page (1:2064), slot 10 in object ID 706101556, index ID 0, partition ID 46275071574016, alloc unit ID 46275071574016 (type "In-row data"). Column "FIELDTABSTOP" value is out of range for data type "numeric". Update column to a legal value.Msg 2570, Level 16, State 3, Line 2Page (1:2068), slot 1 in object ID 706101556, index ID 0, partition ID 46275071574016, alloc unit ID 46275071574016 (type "In-row data"). Column "FIELDISKEYFIELD" value is out of range for data type "numeric". Update column to a legal value.Msg 2570, Level 16, State 3, Line 2Page (1:2068), slot 2 in object ID 706101556, index ID 0, partition ID 46275071574016, alloc unit ID 46275071574016 (type "In-row data"). Column "FIELDLABELVISIBLE" value is out of range for data type "numeric". Update column to a legal value.Msg 2570, Level 16, State 3, Line 2Page (1:2068), slot 4 in object ID 706101556, index ID 0, partition ID 46275071574016, alloc unit ID 46275071574016 (type "In-row data"). Column "FIELDLABELVISIBLE" value is out of range for data type "numeric". Update column to a legal value.Msg 2570, Level 16, State 3, Line 2Page (1:2068), slot 8 in object ID 706101556, index ID 0, partition ID 46275071574016, alloc unit ID 46275071574016 (type "In-row data"). Column "FIELDISKEYFIELD" value is out of range for data type "numeric". Update column to a legal value.Msg 2570, Level 16, State 3, Line 2Page (1:2068), slot 9 in object ID 706101556, index ID 0, partition ID 46275071574016, alloc unit ID 46275071574016 (type "In-row data"). Column "FIELDTABSTOP" value is out of range for data type "numeric". Update column to a legal value.Msg 2570, Level 16, State 3, Line 2Page (1:2068), slot 10 in object ID 706101556, index ID 0, partition ID 46275071574016, alloc unit ID 46275071574016 (type "In-row data"). Column "FIELDTABSTOP" value is out of range for data type "numeric". Update column to a legal value.Msg 2570, Level 16, State 3, Line 2Page (1:2070), slot 0 in object ID 706101556, index ID 0, partition ID 46275071574016, alloc unit ID 46275071574016 (type "In-row data"). Column "FIELDTABSTOP" value is out of range for data type "numeric". Update column to a legal value.Msg 2570, Level 16, State 3, Line 2Page (1:2070), slot 2 in object ID 706101556, index ID 0, partition ID 46275071574016, alloc unit ID 46275071574016 (type "In-row data"). Column "FIELDTABSTOP" value is out of range for data type "numeric". Update column to a legal value.Msg 2570, Level 16, State 3, Line 2Page (1:2070), slot 10 in object ID 706101556, index ID 0, partition ID 46275071574016, alloc unit ID 46275071574016 (type "In-row data"). Column "FIELDTABSTOP" value is out of range for data type "numeric". Update column to a legal value.Msg 2570, Level 16, State 3, Line 2Page (1:3425), slot 8 in object ID 706101556, index ID 0, partition ID 46275071574016, alloc unit ID 46275071574016 (type "In-row data"). Column "FIELDTABSTOP" value is out of range for data type "numeric". Update column to a legal value.There are 60 rows in 5 pages for object "FORMLAYOUTSPECS".[/quote]Here is the output of DBCC PAGE, and I want to look at the first bad value, in slot 9 on page 2064.Note that I have omitted slots 0-8.[code="plain"]DBCC TRACEON (3604)DBCC Page(6,1,2064,1)/*********************************/--HeaderPAGE: (1:2064)BUFFER:BUF @0x00000000E4FB8900bpage = 0x00000000E4418000 bhash = 0x0000000000000000 bpageno = (1:2064)bdbid = 6 breferences = 0 bcputicks = 0bsampleCount = 0 bUse1 = 2756 bstat = 0xc00009blog = 0x21432159 bnext = 0x0000000000000000 PAGE HEADER:Page @0x00000000E4418000m_pageId = (1:2064) m_headerVersion = 1 m_type = 1m_typeFlagBits = 0x0 m_level = 0 m_flagBits = 0x8000m_objId (AllocUnitId.idObj) = 706101556 m_indexId (AllocUnitId.idInd) = 0Metadata: AllocUnitId = 46275071574016 Metadata: PartitionId = 46275071574016Metadata: IndexId = 0 Metadata: ObjectId = 706101556 m_prevPage = (0:0)m_nextPage = (0:0) pminlen = 309 m_slotCnt = 17m_freeCnt = 1243 m_freeData = 6915 m_reservedCnt = 0m_lsn = (7075:2036:2) m_xactReserved = 0 m_xdesId = (0:0)m_ghostRecCnt = 0 m_tornBits = 1836289 Allocation StatusGAM (1:2) = ALLOCATED SGAM (1:3) = NOT ALLOCATED PFS (1:1) = 0x63 MIXED_EXT ALLOCATED 95_PCT_FULL DIFF (1:6) = CHANGEDML (1:7) = NOT MIN_LOGGED DATA:--Skipping ahead to slot 9Slot 9, Offset 0xab1, Length 455, DumpStyle BYTERecord Type = PRIMARY_RECORD Record Attributes = NULL_BITMAP VARIABLE_COLUMNSRecord Size = 455 Memory Dump @0x000000001FF3AAB10000000000000000: 30003501 74626c53 4d542020 20202020 †0.5.tblSMT 0000000000000010: 20202020 20202020 20202020 20534d54 † SMT 0000000000000020: 20202020 20202020 20202020 20202020 † 0000000000000030: 20202020 20200100 00000001 00000000 † .......... 0000000000000040: 02010000 00010300 00000000 00004c69 †..............Li 0000000000000050: 73742020 20202020 20202020 20202020 †st 0000000000000060: 20202020 20202020 20202020 20202020 † 0000000000000070: 20010500 00000000 00002020 20202020 † ......... 0000000000000080: 20202020 20202020 20202020 20202020 † 0000000000000090: 20202001 00000000 01230000 00000000 † ......#...... 00000000000000A0: 0001b004 00000000 00000180 0c000000 †..°............. 00000000000000B0: 00000001 2c010000 00000000 01000000 †....,........... 00000000000000C0: 00010100 00000201 00000002 01000000 †................ 00000000000000D0: 01000000 00010100 00000100 00000001 †................ 00000000000000E0: 00000000 01000000 00010000 00000201 †................ 00000000000000F0: 00000001 23000000 00000000 01200300 †....#........ .. 0000000000000100: 00000000 0001ee02 00000000 00000100 †......î......... 0000000000000110: 00000000 00000001 00000000 01040000 †................ 0000000000000120: 00010000 00000100 00000001 00000000 †................ 0000000000000130: 02010000 00390000 8001101a 08020015 †.....9.......... 0000000000000140: 006b016b 016f0173 0173017f 0183018e †.k.k.o.s.s...ƒ.Ž 0000000000000150: 018e0199 01990199 019d019d 019e019e †.Ž...........ž.ž 0000000000000160: 01b001b6 01c101c3 01c7014c 6973744c †.°.¶.Á.Ã.Ç.ListL 0000000000000170: 6566744c 5574626c 534d5454 79706543 †eftLUtblSMTTypeC 0000000000000180: 6f646544 65736372 69707469 6f6e4465 †odeDescriptionDe 0000000000000190: 73637269 7074696f 6e547970 65304c55 †scriptionType0LU 00000000000001A0: 74626c53 4d544465 73637269 70746f72 †tblSMTDescriptor 00000000000001B0: 4c554e61 6d654465 73637269 7074696f †LUNameDescriptio 00000000000001C0: 6e2d3143 6f6465††††††††††††††††††††††n-1Code [/code]So, now I have the row data, and I know I can replace the bad col with a proper value, but I really just want to understand... So, just looking at the first bits (bytes!):[code="plain"]0000000000000000: 30003501 74626c53 4d542020 20202020 †0.5.tblSMT 0000000000000010: 20202020 20202020 20202020 20534d54 † SMT 0000000000000020: 20202020 20202020 20202020 20202020 † 0000000000000030: 20202020 20200100 00000001 00000000 † .......... 0000000000000040: 02010000 00010300 00000000 00004c69 †..............Li 0000000000000050: 73742020 20202020 20202020 20202020 †st 0000000000000060: 20202020 20202020 20202020 20202020 † [/code]Assuming I understand correctly, the first four bytes is the row header: 30003501Then we start the fixed length cols, which is where we will find the field in question, at offset 0x40.The five bytes found there are : 0201000000Based on everything I found regarding numeric storage: - the first byte stores precision, in this case 02, which matches the ddl - the second byte stores scale, in this case 01, which does not match the ddl - the third byte I don't know - the fourth byte has the sign (00 for neg, 01 for pos) - the fifth byte has the valueIs this an accurate description?The number returned in queries for this row is -1. But that doesn't look like what is on the page, unless I take the next byte as well, which would be six for this col - that CAN'T be right... :-)Is the problem here that the engine sees this defined as numeric(2,1) when in reality it is (2,0)?If you specify negative with the fourth byte, can you still have zero? Or, does negative require a non-zero number? Perhaps I have missed a byte of overhead?Can anyone help clear this up for me? Am I looking at the right bytes for this column? Did I overlook the NULL Bitmap, or am I right that it is at 0x135?I'll attach a DBCC Page type 3 for more detail for those that want it.Remember, nothing is down. No outage, I can re-enter the bad data.And, thanks!-Dan BThu, 15 Sep 2011 12:16:38 GMTskrilla99http://www.sqlservercentral.com/Forums/Topic1169776-2893-1.aspxI have DB Backup file that couldn't restore as it showing me error msg that is [b]Msg 3154, Level 16, State 4, Line 1The backup set holds a backup of a database other than the existing 'TEST_DB' database.Msg 3013, Level 16, State 1, Line 1RESTORE DATABASE is terminating abnormally.[/b]I tried [b]Restore FilesListonly[/b] which give me two files like this [b]C:\Program Files\Microsoft SQL Server\MSSQL10.MSSQLSERVER\MSSQL\DATA\TEJ_DATA.mdf C:\Program Files\Microsoft SQL Server\MSSQL10.MSSQLSERVER\MSSQL\DATA\TEJ_DATA.ldf [/b][b]Restore VerifyOnly [/b][b]Msg 3242, Level 16, State 2, Line 1The file on device 'D:\New Folder\TEJ06082011.BAK' is not a valid Microsoft Tape Format backup set.Msg 3013, Level 16, State 1, Line 1VERIFY DATABASE is terminating abnormally.[/b]It was corrupted when i Zip the BAKUP File ,While extracting the Backup it says that 'CRC Corrupted' and it partially Repaired using WINRAR Repair Tool.Is there any way to restore the Backup without lose data?Please help me thanks in advance,Sun, 04 Sep 2011 13:23:21 GMTmemanafhttp://www.sqlservercentral.com/Forums/Topic1169751-2893-1.aspxDear All,Could you Please help me if can resolve error below Once execute DBCC CHECKDB Command?Is there anyway to resolve this ?DBCC results for 'My_Data'.Service Broker Msg 9675, State 1: Message Types analyzed: 14.Service Broker Msg 9676, State 1: Service Contracts analyzed: 6.Service Broker Msg 9667, State 1: Services analyzed: 3.Service Broker Msg 9668, State 1: Service Queues analyzed: 3.Service Broker Msg 9669, State 1: Conversation Endpoints analyzed: 0.Service Broker Msg 9674, State 1: Conversation Groups analyzed: 0.Service Broker Msg 9670, State 1: Remote Service Bindings analyzed: 0.Service Broker Msg 9605, State 1: Conversation Priorities analyzed: 0.DBCC results for 'sys.sysrscols'.There are 638 rows in 8 pages for object "sys.sysrscols".DBCC results for 'sys.sysrowsets'.There are 92 rows in 1 pages for object "sys.sysrowsets".DBCC results for 'sys.sysallocunits'.There are 104 rows in 2 pages for object "sys.sysallocunits".DBCC results for 'sys.sysfiles1'.There are 2 rows in 1 pages for object "sys.sysfiles1".DBCC results for 'sys.syspriorities'.There are 0 rows in 0 pages for object "sys.syspriorities".DBCC results for 'sys.sysfgfrag'.There are 2 rows in 1 pages for object "sys.sysfgfrag".DBCC results for 'sys.sysphfg'.There are 1 rows in 1 pages for object "sys.sysphfg".DBCC results for 'sys.sysprufiles'.There are 3 rows in 1 pages for object "sys.sysprufiles".DBCC results for 'sys.sysftinds'.There are 0 rows in 0 pages for object "sys.sysftinds".DBCC results for 'sys.sysowners'.There are 14 rows in 1 pages for object "sys.sysowners".DBCC results for 'sys.sysprivs'.There are 130 rows in 1 pages for object "sys.sysprivs".DBCC results for 'sys.sysschobjs'.There are 54 rows in 1 pages for object "sys.sysschobjs".DBCC results for 'sys.syscolpars'.There are 488 rows in 9 pages for object "sys.syscolpars".DBCC results for 'sys.sysnsobjs'.There are 1 rows in 1 pages for object "sys.sysnsobjs".DBCC results for 'sys.syscerts'.There are 0 rows in 0 pages for object "sys.syscerts".DBCC results for 'sys.sysxprops'.There are 0 rows in 0 pages for object "sys.sysxprops".DBCC results for 'sys.sysscalartypes'.There are 34 rows in 1 pages for object "sys.sysscalartypes".DBCC results for 'sys.systypedsubobjs'.There are 0 rows in 0 pages for object "sys.systypedsubobjs".DBCC results for 'sys.sysidxstats'.There are 167 rows in 2 pages for object "sys.sysidxstats".DBCC results for 'sys.sysiscols'.There are 318 rows in 3 pages for object "sys.sysiscols".DBCC results for 'sys.sysbinobjs'.There are 23 rows in 1 pages for object "sys.sysbinobjs".DBCC results for 'sys.sysaudacts'.There are 0 rows in 0 pages for object "sys.sysaudacts".DBCC results for 'sys.sysobjvalues'.There are 168 rows in 33 pages for object "sys.sysobjvalues".DBCC results for 'sys.sysclsobjs'.There are 16 rows in 1 pages for object "sys.sysclsobjs".DBCC results for 'sys.sysrowsetrefs'.There are 0 rows in 0 pages for object "sys.sysrowsetrefs".DBCC results for 'sys.sysremsvcbinds'.There are 0 rows in 0 pages for object "sys.sysremsvcbinds".DBCC results for 'sys.sysxmitqueue'.There are 0 rows in 0 pages for object "sys.sysxmitqueue".DBCC results for 'sys.sysrts'.There are 1 rows in 1 pages for object "sys.sysrts".DBCC results for 'sys.sysconvgroup'.There are 0 rows in 0 pages for object "sys.sysconvgroup".DBCC results for 'sys.sysdesend'.There are 0 rows in 0 pages for object "sys.sysdesend".DBCC results for 'sys.sysdercv'.There are 0 rows in 0 pages for object "sys.sysdercv".DBCC results for 'sys.syssingleobjrefs'.There are 147 rows in 1 pages for object "sys.syssingleobjrefs".DBCC results for 'sys.sysmultiobjrefs'.There are 106 rows in 1 pages for object "sys.sysmultiobjrefs".DBCC results for 'sys.sysguidrefs'.There are 0 rows in 0 pages for object "sys.sysguidrefs".DBCC results for 'sys.syscompfragments'.There are 0 rows in 0 pages for object "sys.syscompfragments".DBCC results for 'sys.sysftstops'.There are 0 rows in 0 pages for object "sys.sysftstops".DBCC results for 'sys.sysqnames'.There are 97 rows in 1 pages for object "sys.sysqnames".DBCC results for 'sys.sysxmlcomponent'.There are 99 rows in 1 pages for object "sys.sysxmlcomponent".DBCC results for 'sys.sysxmlfacet'.There are 112 rows in 1 pages for object "sys.sysxmlfacet".DBCC results for 'sys.sysxmlplacement'.There are 18 rows in 1 pages for object "sys.sysxmlplacement".DBCC results for 'sys.sysobjkeycrypts'.There are 0 rows in 0 pages for object "sys.sysobjkeycrypts".DBCC results for 'sys.sysasymkeys'.There are 0 rows in 0 pages for object "sys.sysasymkeys".DBCC results for 'sys.syssqlguides'.There are 0 rows in 0 pages for object "sys.syssqlguides".DBCC results for 'sys.sysbinsubobjs'.There are 3 rows in 1 pages for object "sys.sysbinsubobjs".DBCC results for 'sys.syssoftobjrefs'.There are 0 rows in 0 pages for object "sys.syssoftobjrefs".DBCC results for 'sys.filestream_tombstone_1522104463'.There are 0 rows in 0 pages for object "sys.filestream_tombstone_1522104463".DBCC results for 'sys.syscommittab'.There are 0 rows in 0 pages for object "sys.syscommittab".DBCC results for 'Data_Table1'.[b]Msg 8928, Level 16, State 1, Line 1Object ID 1685581043, index ID 0, partition ID 72057594042974208, alloc unit ID 72057594049855488 (type In-row data): Page (1:1524) could not be processed. See other errors for details.Msg 8939, Level 16, State 98, Line 1Table error: Object ID 1685581043, index ID 0, partition ID 72057594042974208, alloc unit ID 72057594049855488 (type In-row data), page (1:1524). Test (IS_OFF (BUF_IOERR, pBUF->bstat)) failed. Values are 29493257 and -4.Msg 8928, Level 16, State 1, Line 1Object ID 1685581043, index ID 0, partition ID 72057594042974208, alloc unit ID 72057594049855488 (type In-row data): Page (1:1525) could not be processed. See other errors for details.Msg 8939, Level 16, State 98, Line 1Table error: Object ID 1685581043, index ID 0, partition ID 72057594042974208, alloc unit ID 72057594049855488 (type In-row data), page (1:1525). Test (IS_OFF (BUF_IOERR, pBUF->bstat)) failed. Values are 29493257 and -4.Msg 8928, Level 16, State 1, Line 1Object ID 1685581043, index ID 0, partition ID 72057594042974208, alloc unit ID 72057594049855488 (type In-row data): Page (1:3125) could not be processed. See other errors for details.Msg 8939, Level 16, State 98, Line 1Table error: Object ID 1685581043, index ID 0, partition ID 72057594042974208, alloc unit ID 72057594049855488 (type In-row data), page (1:3125). Test (IS_OFF (BUF_IOERR, pBUF->bstat)) failed. Values are 29493257 and -4.Msg 8928, Level 16, State 1, Line 1Object ID 1685581043, index ID 0, partition ID 72057594042974208, alloc unit ID 72057594049855488 (type In-row data): Page (1:5820) could not be processed. See other errors for details.Msg 8939, Level 16, State 98, Line 1Table error: Object ID 1685581043, index ID 0, partition ID 72057594042974208, alloc unit ID 72057594049855488 (type In-row data), page (1:5820). Test (IS_OFF (BUF_IOERR, pBUF->bstat)) failed. Values are 29493257 and -4.Msg 8928, Level 16, State 1, Line 1Object ID 1685581043, index ID 0, partition ID 72057594042974208, alloc unit ID 72057594049855488 (type In-row data): Page (1:5821) could not be processed. See other errors for details.Msg 8939, Level 16, State 98, Line 1Table error: Object ID 1685581043, index ID 0, partition ID 72057594042974208, alloc unit ID 72057594049855488 (type In-row data), page (1:5821). Test (IS_OFF (BUF_IOERR, pBUF->bstat)) failed. Values are 29493257 and -4.Msg 8928, Level 16, State 1, Line 1Object ID 1685581043, index ID 0, partition ID 72057594042974208, alloc unit ID 72057594049855488 (type In-row data): Page (1:6077) could not be processed. See other errors for details.Msg 8939, Level 16, State 98, Line 1Table error: Object ID 1685581043, index ID 0, partition ID 72057594042974208, alloc unit ID 72057594049855488 (type In-row data), page (1:6077). Test (IS_OFF (BUF_IOERR, pBUF->bstat)) failed. Values are 29493257 and -4.Msg 8928, Level 16, State 1, Line 1Object ID 1685581043, index ID 0, partition ID 72057594042974208, alloc unit ID 72057594049855488 (type In-row data): Page (1:12285) could not be processed. See other errors for details.Msg 8939, Level 16, State 98, Line 1Table error: Object ID 1685581043, index ID 0, partition ID 72057594042974208, alloc unit ID 72057594049855488 (type In-row data), page (1:12285). Test (IS_OFF (BUF_IOERR, pBUF->bstat)) failed. Values are 29493257 and -4.Msg 8928, Level 16, State 1, Line 1Object ID 1685581043, index ID 0, partition ID 72057594042974208, alloc unit ID 72057594049855488 (type In-row data): Page (1:20317) could not be processed. See other errors for details.Msg 8939, Level 16, State 98, Line 1Table error: Object ID 1685581043, index ID 0, partition ID 72057594042974208, alloc unit ID 72057594049855488 (type In-row data), page (1:20317). Test (IS_OFF (BUF_IOERR, pBUF->bstat)) failed. Values are 29493257 and -4.Msg 8928, Level 16, State 1, Line 1Object ID 1685581043, index ID 0, partition ID 72057594042974208, alloc unit ID 72057594049855488 (type In-row data): Page (1:22044) could not be processed. See other errors for details.Msg 8939, Level 16, State 98, Line 1Table error: Object ID 1685581043, index ID 0, partition ID 72057594042974208, alloc unit ID 72057594049855488 (type In-row data), page (1:22044). Test (IS_OFF (BUF_IOERR, pBUF->bstat)) failed. Values are 29493257 and -4.Msg 8928, Level 16, State 1, Line 1Object ID 1685581043, index ID 0, partition ID 72057594042974208, alloc unit ID 72057594049855488 (type In-row data): Page (1:22045) could not be processed. See other errors for details.Msg 8939, Level 16, State 98, Line 1Table error: Object ID 1685581043, index ID 0, partition ID 72057594042974208, alloc unit ID 72057594049855488 (type In-row data), page (1:22045). Test (IS_OFF (BUF_IOERR, pBUF->bstat)) failed. Values are 29493257 and -4.Msg 8928, Level 16, State 1, Line 1Object ID 1685581043, index ID 0, partition ID 72057594042974208, alloc unit ID 72057594049855488 (type In-row data): Page (1:22940) could not be processed. See other errors for details.Msg 8939, Level 16, State 98, Line 1Table error: Object ID 1685581043, index ID 0, partition ID 72057594042974208, alloc unit ID 72057594049855488 (type In-row data), page (1:22940). Test (IS_OFF (BUF_IOERR, pBUF->bstat)) failed. Values are 29493257 and -4.Msg 8928, Level 16, State 1, Line 1Object ID 1685581043, index ID 0, partition ID 72057594042974208, alloc unit ID 72057594049855488 (type In-row data): Page (1:27677) could not be processed. See other errors for details.Msg 8939, Level 16, State 98, Line 1Table error: Object ID 1685581043, index ID 0, partition ID 72057594042974208, alloc unit ID 72057594049855488 (type In-row data), page (1:27677). Test (IS_OFF (BUF_IOERR, pBUF->bstat)) failed. Values are 29493257 and -4.Msg 8928, Level 16, State 1, Line 1Object ID 1685581043, index ID 0, partition ID 72057594042974208, alloc unit ID 72057594049855488 (type In-row data): Page (1:28253) could not be processed. See other errors for details.Msg 8939, Level 16, State 98, Line 1Table error: Object ID 1685581043, index ID 0, partition ID 72057594042974208, alloc unit ID 72057594049855488 (type In-row data), page (1:28253). Test (IS_OFF (BUF_IOERR, pBUF->bstat)) failed. Values are 29493257 and -4.Msg 8928, Level 16, State 1, Line 1Object ID 1685581043, index ID 0, partition ID 72057594042974208, alloc unit ID 72057594049855488 (type In-row data): Page (1:29276) could not be processed. See other errors for details.Msg 8939, Level 16, State 98, Line 1Table error: Object ID 1685581043, index ID 0, partition ID 72057594042974208, alloc unit ID 72057594049855488 (type In-row data), page (1:29276). Test (IS_OFF (BUF_IOERR, pBUF->bstat)) failed. Values are 29493257 and -4.Msg 8928, Level 16, State 1, Line 1Object ID 1685581043, index ID 0, partition ID 72057594042974208, alloc unit ID 72057594049855488 (type In-row data): Page (1:34389) could not be processed. See other errors for details.Msg 8939, Level 16, State 98, Line 1Table error: Object ID 1685581043, index ID 0, partition ID 72057594042974208, alloc unit ID 72057594049855488 (type In-row data), page (1:34389). Test (IS_OFF (BUF_IOERR, pBUF->bstat)) failed. Values are 29493257 and -4.Msg 8928, Level 16, State 1, Line 1Object ID 1685581043, index ID 0, partition ID 72057594042974208, alloc unit ID 72057594049855488 (type In-row data): Page (1:34390) could not be processed. See other errors for details.Msg 8939, Level 16, State 98, Line 1Table error: Object ID 1685581043, index ID 0, partition ID 72057594042974208, alloc unit ID 72057594049855488 (type In-row data), page (1:34390). Test (IS_OFF (BUF_IOERR, pBUF->bstat)) failed. Values are 29493257 and -4.Msg 8928, Level 16, State 1, Line 1Object ID 1685581043, index ID 0, partition ID 72057594042974208, alloc unit ID 72057594049855488 (type In-row data): Page (1:40088) could not be processed. See other errors for details.Msg 8939, Level 16, State 98, Line 1Table error: Object ID 1685581043, index ID 0, partition ID 72057594042974208, alloc unit ID 72057594049855488 (type In-row data), page (1:40088). Test (IS_OFF (BUF_IOERR, pBUF->bstat)) failed. Values are 29493257 and -4.Msg 8928, Level 16, State 1, Line 1Object ID 1685581043, index ID 0, partition ID 72057594042974208, alloc unit ID 72057594049855488 (type In-row data): Page (1:42513) could not be processed. See other errors for details.Msg 8939, Level 16, State 98, Line 1Table error: Object ID 1685581043, index ID 0, partition ID 72057594042974208, alloc unit ID 72057594049855488 (type In-row data), page (1:42513). Test (IS_OFF (BUF_IOERR, pBUF->bstat)) failed. Values are 29493257 and -4.Msg 8928, Level 16, State 1, Line 1Object ID 1685581043, index ID 0, partition ID 72057594042974208, alloc unit ID 72057594049855488 (type In-row data): Page (1:43509) could not be processed. See other errors for details.Msg 8939, Level 16, State 98, Line 1Table error: Object ID 1685581043, index ID 0, partition ID 72057594042974208, alloc unit ID 72057594049855488 (type In-row data), page (1:43509). Test (IS_OFF (BUF_IOERR, pBUF->bstat)) failed. Values are 29493257 and -4.Msg 8928, Level 16, State 1, Line 1Object ID 1685581043, index ID 0, partition ID 72057594042974208, alloc unit ID 72057594049855488 (type In-row data): Page (1:43700) could not be processed. See other errors for details.Msg 8939, Level 16, State 98, Line 1Table error: Object ID 1685581043, index ID 0, partition ID 72057594042974208, alloc unit ID 72057594049855488 (type In-row data), page (1:43700). Test (IS_OFF (BUF_IOERR, pBUF->bstat)) failed. Values are 29493257 and -4.Msg 8928, Level 16, State 1, Line 1Object ID 1685581043, index ID 0, partition ID 72057594042974208, alloc unit ID 72057594049855488 (type In-row data): Page (1:43765) could not be processed. See other errors for details.Msg 8939, Level 16, State 98, Line 1Table error: Object ID 1685581043, index ID 0, partition ID 72057594042974208, alloc unit ID 72057594049855488 (type In-row data), page (1:43765). Test (IS_OFF (BUF_IOERR, pBUF->bstat)) failed. Values are 29493257 and -4.Msg 8939, Level 16, State 98, Line 1Table error: Object ID 1685581043, index ID 0, partition ID 72057594042974208, alloc unit ID 72057594049855488 (type In-row data), page (1:48229). Test (IS_OFF (BUF_IOERR, pBUF->bstat)) failed. Values are 29493257 and -4.Msg 8928, Level 16, State 1, Line 1Object ID 1685581043, index ID 0, partition ID 72057594042974208, alloc unit ID 72057594049855488 (type In-row data): Page (1:48245) could not be processed. See other errors for details.Msg 8928, Level 16, State 1, Line 1Object ID 1685581043, index ID 0, partition ID 72057594042974208, alloc unit ID 72057594049855488 (type In-row data): Page (1:52989) could not be processed. See other errors for details.Msg 8939, Level 16, State 98, Line 1Table error: Object ID 1685581043, index ID 0, partition ID 72057594042974208, alloc unit ID 72057594049855488 (type In-row data), page (1:52989). Test (IS_OFF (BUF_IOERR, pBUF->bstat)) failed. Values are 29493257 and -4.[/b]There are 2989145 rows in 49756 pages for object "Data_table1".CHECKDB found 0 allocation errors and 46 consistency errors in table 'Data_table1' (object ID 1685581043).DBCC results for 'sys.queue_messages_1977058079'.There are 0 rows in 0 pages for object "sys.queue_messages_1977058079".DBCC results for 'sys.queue_messages_2009058193'.There are 0 rows in 0 pages for object "sys.queue_messages_2009058193".DBCC results for 'sys.queue_messages_2041058307'.There are 0 rows in 0 pages for object "sys.queue_messages_2041058307".CHECKDB found 0 allocation errors and 46 consistency errors in database 'My_data'.repair_allow_data_loss is the minimum repair level for the errors found by DBCC CHECKDB (My_data).DBCC execution completed. If DBCC printed error messages, contact your system administrator.Sun, 04 Sep 2011 09:45:23 GMTmemanafhttp://www.sqlservercentral.com/Forums/Topic1163986-2893-1.aspxIf DBCC CHECKDB Yields errors what is the next step?Tue, 23 Aug 2011 07:39:47 GMTvenugopal.machinahttp://www.sqlservercentral.com/Forums/Topic1116704-2893-1.aspxHi All,I have a problem in SQL Server 2008 R2.I was running a query that updated huge data in database, therefore it takes a lot of time to finish.And before the query has been finished (after 1 hour processing), I got error message "Cannot open database "XXX" requested by the login. The login failed". And then I tried to connect to that database again, and the Database became XXX(In Recovery). After 5 hours, the database has recovered on its own.Does anybody know what is the problem that might cause this issues(database became In Recovery)?Thanks in advanceSat, 28 May 2011 19:56:25 GMTratna_ainhttp://www.sqlservercentral.com/Forums/Topic1117202-2893-1.aspxHi Guys,Recently I have been recieving 832 errors on my sql server. One time it actually corrupted my database and I needed to do a restore.We have been talking to Microsoft who have looked at many things (sqlio, logs etc). One of the last things they suggested was getting the vendor to do a hardware check. Our hardware guys are sure that there is not a hardware problem Anyway I did some looking around and found that trace 815 and 818 could help diagnose. The doco I read was that I should not do without consulting microsoft - so I asked them about it and they seem to think it is a good idea.The thing I need to ask and could not claridy with microsoft is:If a dump is caused from a result of trace 815, does that prevent an external process from writing into sql server's memory?Mon, 30 May 2011 23:36:20 GMTdjordan 4543