Are you the publisher? Claim or contact us about this channel


Embed this content in your HTML

Search

Report adult content:

click to rate:

Account: (login)

More Channels


Channel Catalog


Channel Description:

SQLServerCentral

(Page 1) | 2 | 3 | .... | 11 | newer

    0 0
  • 01/26/12--00:26: DBCC CHECKDB error!
  • Following 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!

    0 0

    Hi,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.Gans

    0 0

    Hi 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.Adonia

    0 0
  • 05/07/12--17:58: database size
  • dear allwhat is production database size generally(500gb or 1tb) and how to monitor the databasewhat is step for monitoring production databaseThanks

    0 0

    Here'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?

    0 0

    The 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: drive

    0 0
  • 06/09/12--02:33: DATABASE CRASHED-Urgent Help
  • Hi My Database has crashed and I have lost only 2 ndf files out of 9 ..is there a Possible way to recover just those 2 files and also any way to decrease the downtime .Please Help

    0 0
  • 06/19/12--23:20: Model data base is corrupted
  • Hi I have to know some information regarding system databaseIf the model database is corruptedwhat is the necessary steps we need to followPlease kindly help me

    0 0

    here we are trying to connect the server which is in network.Here protocals,remote desktop option enabled, we can able to ping also.we are domain users and we have the access to server alsostill we are unable to connect.What could be the reason and what steps we need to follow

    0 0

    TITLE: Microsoft SQL Server Management Studio------------------------------Restore failed for Server 'VENKAT-PC\HA'. (Microsoft.SqlServer.SmoExtended)For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=10.50.1600.1+((KJ_RTM).100402-1539+)&EvtSrc=Microsoft.SqlServer.Management.Smo.ExceptionTemplates.FailedOperationExceptionText&EvtID=Restore+Server&LinkId=20476------------------------------ADDITIONAL INFORMATION:System.Data.SqlClient.SqlError: The media set has 2 media families but only 1 are provided. All members must be provided. (Microsoft.SqlServer.Smo)For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=10.50.1600.1+((KJ_RTM).100402-1539+)&LinkId=20476------------------------------BUTTONS:OK------------------------------

    0 0

    A client had a an old Dell T300 with a RAID 5, and ECC Memory.They had corruption in the Active Directory DB and in a SQL DB. Both from two different times. We quickly replaced their server with a newer HP in fear of not knowing why the disk corruption was taking place.The built in Dell diagnostics detect no issues. And while the server is "stable", the disk writes are not.I suspect its memory or maybe the RAID controller doesn't know the BBU is broken etc, or SMART on a disk is not reporting correctly.I wanted to test for the BBU problem by running a long running SQL query and unplugging the power.Any suggestions for a query that is likely to then after inspection after the restart, to have caused corruption if it happened mid transaction?EDIT: I am not looking for the queries that inspect the DB, I am looking for advice on what I query I can run that would write a lot of data that would also not deal well with an ungraceful shutdown.We would like to figure out the source of the issue, so we can make it a replica destination for Veeam (basically a backup ready to run).Thanks!

    0 0

    Hello,I virtualized with Hyper V MS Server 2008 R2 Enterprise and SQL Server 2008 R2 Enterprise.Then I attached for test purposes two older 'SQL 2000 mdfs and its log files.As recommended from Microsoft, I checked the consistency of the attached databases under SQL 2008 R2.So, I scripted the following:[code="sql"] DBCC CHECKDB ([i]'DB-1'[/i]).[/code]MS SQL Server reported an inconsistence in a table, which I tried to repair via[code="sql"] DBCC UPDATEUSAGE ([i]'DB-1'[/i]).[/code]I ran one more time CHECKDB over the entire db, resulting in 0 errors, now.But then I noticed, that the system databases are lost !?Is there a certified method of how to restore the system databases !?I tried this:Setup /QUIET /ACTION=REBUILDDATABASE /INSTANCENAME=InstanceName /SQLSYSADMINACCOUNTS=accounts [ /SAPWD= StrongPassword ] [ /SQLCOLLATION=CollationName]Though I must say, the result was not satisfying. ;(Maybe, one of you gurus does have another idea to restore the system databases (without re-attaching the SQL2000 databases) ?Thank you, in advance,Stephan

    0 0
  • 06/24/12--21:31: DBCC error message
  • One of our databases is reporting the following errors when I run DBCC CHECKDB:Object ID 773577794, index ID 1, partition ID 72057594040156160, alloc unit ID 72057594041729024 (type In-row data): Page (1:31189) could not be processed. See other errors for details.Table error: Object ID 773577794, index ID 1, partition ID 72057594040156160, alloc unit ID 72057594041729024 (type In-row data), page (1:31189). Test (IS_OFF (BUF_IOERR, pBUF->bstat)) failed. Values are 381814793 and -4.CHECKDB found 0 allocation errors and 2 consistency errors in table 'Address' (object ID 773577794).SQL Server is specifying that I should use repair_allow_data_loss to fix the issue. I have read Gail's [url=http://www.sqlservercentral.com/articles/Corruption/65804/]article[/url] about fixing corrupt databases so I think there is maybe some incorrect data in one of the columns.Is there anything else I can do to try and pinpoint this?The table is quite large so I don't really fancy trawlling through all the records. If there is any other information I can provide to help let me know.Thanks in advance

    0 0

    I am currently fighting an issue in which I'm looking for confirmation that this could be related to a bad backup or not.I have attempting to restore two seperate full backs for the same database.What I am seeing is the following error during the process in the sql logs:SQL Server has encountered 1 occurrence(s) of I/O requests taking longer than 15 seconds to complete on file [I:\database_name.mdf] in database [<Database name is not available>] (5). The OS file handle is 0x00000000000007EC. The offset of the latest long I/O is: 0x00001adda30000Then the process a little later fails with:Msg 3202, Level 16, State 1, Line 1Write on "???" failed: 1117(The request could not be performed because of an I/O device error.)Msg 3013, Level 16, State 1, Line 1RESTORE DATABASE is terminating abnormally.The system is virtual. One thing we have attempted to do is to remove the vdmk and recreated it in the same datastore and lun on the san within a share raid group.Backups are being performed by the standard backup maintenance plan. Compression is enabled and verfiy backup integrity is enabled.The server is running OS Windows Server 2008 R2 and SQL Server 2008 R2 SP1.I believe this is being cause due to an I/O issue with the disk subsystem. However, could this be cause due to a bad backup?

    0 0

    Please pardon any ignorance on my part...(brand-spanking-new-DBA)Running CheckDB returns the following error:Check Catalog Msg 3853, State 1: Attribute (object_id=1357963914) of row (object_id=1357963914,column_id=1) in sys.columns does not have a matching row (object_id=1357963914) in sys.objects. [SQLSTATE 42000] (Error 8992) CHECKDB found 0 allocation errors and 1 consistency errors not associated with any single object. [SQLSTATE 01000] (Error 8954) CHECKDB found 0 allocation errors and 1 consistency errors in database 'amtslab'. [SQLSTATE 01000] (Error 8989). The step failed.I found this article: http://www.sqlservercentral.com/articles/Corruption/69382/[quote]The method preferred by most of the SQL corruption gurus is to create another database, and copy the contents of the corrupted database into the new database. Depending on the size of your database, this could take quite some time.[/quote]Could you tell me...what is involved with "copying the contents of the corrupted db to the new db?" Is the article referring to manually transferring all the data and objects? If so, is there any tool that could assist?Also, this error apparently has been happening for quite some time (the server was upgraded some time ago and we just began recently to run CheckDB) and all copies of this db on our other intances and all backups copies appear to have this issue. Is it something that MUST be repaired? If it is something we can get by with, should and could we repress the errors so CheckDB could continue?Also, when I query sys.columns and sys.objects for object_id 1357963914 I do not get any records returned.Any information you have to offer would be greatly appreciated. TIA!

    0 0
  • 07/12/12--07:31: zhow to retrieve tables
  • My Sql server 2005 Database get corrupted coz of some virus infection. No tables are showing now. My database folder contains .mdf, .ldf and file (3 files) can I retrieve my tables using one of this. Any solution please? I don't have any other backups.Please get a solution.

    0 0
  • 07/27/12--20:42: Cant Attach Back Up File
  • Trying to repair database from Backup file giving errors .Restore failed for Server 'USER-PC\SQLEXPRESS'. (Microsoft.SqlServer.Express.Smo)The backup set holds a backup of a database other than the existing 'FLEX' I am using the backup of the same daabse tried many metods. All failedServer error messages as follows.Restore failed for Server 'USER-PC\SQLEXPRESS'. (Microsoft.SqlServer.Express.Smo)For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=9.00.2047.00&EvtSrc=Microsoft.SqlServer.Management.Smo.ExceptionTemplates.FailedOperationExceptionText&EvtID=Restore+Server&LinkId=20476 at Microsoft.SqlServer.Management.Smo.Restore.SqlRestore(Server srv) at Microsoft.SqlServer.Management.SqlManagerUI.SqlRestoreDatabaseOptions.RunRestore()System.Data.SqlClient.SqlError: The backup set holds a backup of a database other than the existing 'FLEX' database. (Microsoft.SqlServer.Express.Smo)For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=9.00.2047.00&LinkId=20476 at Microsoft.SqlServer.Management.Smo.ExecutionManager.ExecuteNonQueryWithMessage(StringCollection queries, ServerMessageEventHandler dbccMessageHandler, Boolean errorsAsMessages) at Microsoft.SqlServer.Management.Smo.BackupRestoreBase.ExecuteSql(Server server, StringCollection queries) at Microsoft.SqlServer.Management.Smo.Restore.SqlRestore(Server srv)

    0 0

    we face 3 exception when we connect through the client also slow down the performance.exceptions are a follows:1) System.Data.SqlClient.SqlException (0x80131904): A transport-level error has occurred when receiving results from the server. (provider: TCP Provider, error: 0 - The semaphore timeout period has expired.)2) System.Data.SqlClient.SqlException (0x80131904): A transport-level error has occurred when receiving results from the server. (provider: TCP Provider, error: 0 - An existing connection was forcibly closed by the remote host.)3) System.Data.SqlClient.SqlException (0x80131904): Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding.Windows Server 2008 R2 with SP1 (64-bit)RAM 16 GBSQL Server 2008 R2Client machine have Windows7Please help somebody

    0 0

    Hi AllI'm confused about the the topic of Deferred transactions (-spids) and database recoveryI read and tested the steps in this article by Paul Randal: [url]http://www.sqlskills.com/BLOGS/PAUL/post/Disaster-recovery-101-dealing-with-negative-SPIDS-(-2-and-3).aspx[/url]I was able to re-create the situationMy question is that why does the Database come up as suspect? Because the Database can't roll back/forward the transaction(s) because of the missing files, shouldn't the database go into a [i]Recovery Pending[/i] state?Thanks

    0 0

    Hi All,Just wanted to know what does this error mean? I do see a lot issues with this meta data corruption during upgrade of sql 2000 to sql 2008. What does happen during the upgrade ? What are the possible sceanori's we land up in such scenarios? As far as i know i if someone changes the system tables, this might cause this errrors. Just wanted to understand why upgrade to higher version causes this meta data corruption. I beilve we should run the checkdb on sql 2000 databases even before going for upgrade !!!Check Catalog Msg 3853, State 1: Attribute (object_id=1379457380) of row (object_id=1379457380,column_id=1) in sys.columns does not have a matching row (object_id=1379457380) in sys.objectsThanks in Advance

(Page 1) | 2 | 3 | .... | 11 | newer