Hi All,Very long time since i was last here.Need some advice with this challenge, hopefully Gail or Paul might be around?.SQL 2005 SP2Dedicated NAS - about 8 years old3.5TB database split over multiple volumes, largest datafile is 2.3TB.operating system is windows 2003There have been issues with sql database consistency problems being reported for quite a while, checks on the storage indicate no problem, but I am not convinced. Database is still usable and is a production server, but the server is restarted/rebooted on what used to be weekly, to pretty much every day and recently 3-4 + times a day now.got about 200K messages like the following within the last 24 hours, although this has been ongoing for a long time.SQL Server detected a logical consistency-based I/O error: torn page (expected signature: 0xaaaaaaaa; actual signature: 0x75cac85e). It occurred during a read of page (6:91296219) in database ID 5 at offset 0x0000ae223b6000 in file 'I:\.ndf'. 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.SQL Server detected a logical consistency-based I/O error: incorrect checksum (expected: 0x784b5a48; actual: 0xe8681f5f). It occurred during a read of page (6:91088683) in database ID 5 at offset 0x0000adbce56000 in file 'I:\.ndf'. 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.SQL Server detected a logical consistency-based I/O error: incorrect pageid (expected 6:91296185; actual 2057:151455495). It occurred during a read of page (6:91296185) in database ID 5 at offset 0x0000ae22372000 in file 'I:df'. 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.basically error 824 serverity 24 state 2all within the same datafile, and ironically one that has autogrowth switched off.msdb..suspect_pages currently has 405 rows with the errorcount for each row varying from 1 to 100kwhen i try to run dbcc checkdb with any options i getMsg 1823, Level 16, State 2, Line 1A database snapshot cannot be created because it failed to start.Msg 5123, Level 16, State 1, Line 1CREATE FILE encountered operating system error 1450(error not found) while attempting to open or create the physical file 'H:\.mdf:MSSQL_DBCC11'.Msg 7928, Level 16, State 1, Line 1The database snapshot for online checks could not be created. Either the reason is given in a previous error or one of the underlying volumes does not support sparse files or alternate streams. Attempting to get exclusive access to run checks offline.Msg 5030, Level 16, State 12, Line 1The database could not be exclusively locked to perform the operation.Msg 7926, Level 16, State 1, Line 1Check statement aborted. The database could not be checked as a database snapshot could not be created and the database or table could not be locked. See Books Online for details of when this behavior is expected and what workarounds exist. Also see previous errors for more details.Is causing me a few headaches, no backups exist for this database, dont get me started :-Pdatabase is absolutely critical to the businessReally need advice from someone who understands DBCC CHECKDB extremely well, as I am not sure if the reason DBCC CHECKDB doesnt run, could be down to insufficent space to create the internal snapshot, if someone could give a rough estimate on how much space is required, for a 3.5 TB database, that would be great and bad in a way, as I cannot add any more storage to this server.Seriously hoping i dont need to go down the DBCC PAGE and IND route, with hex editior in hand but have endless supply of caffeine if required. ;-)Any helpful advice is always appreciated, if you need more info, just let me know.CheersDarrennew update, think i might be in new world of painmanaged to work with dbcc checktable briefly, still errors out but recommended repair is allow data loss.done it with estimateonly with main table, need close to 300GB for tempdb, that drive has 2GB free and cannot be increased.
↧