I have inherited a database which started life under SQL 7 (where Torn page Detection was OFF by default), and I'd like to turn it on. Will this reshuffle all the pages to make room for the extra check-sum, or is that stored in a single block somewhere else such that it can easily be added?
Is the change going to block access for long? (DB = between 2~5GB)
Hi, We recently had one of our drives (RAID5) replaced because of failure. This has resulted in a torn page being detected on one of our smaller SQL 2000 databases. We have one or two larger SQL databases (30-70GB) on the same drive amongst several others and are now concerned that we may have a problem with these databases also. (The original torn page only came to light when a query was run on one of the tables). Is there anyway I can run a procedure on each of the databases to find out if we have any problems with torn pages? I obviously don't want to restore the databases as this will take a substantial amount of time that we just don't have at the moment. Any ideas that could put our minds at rest would be much appreciated. Many thanks.
I want to switch this setting off on all db's - that's easy.
But I presume that means the problem could occur without me knowing for weeks (maybe due to a defective disk driver). So is there a way I can schedule a maintainance task that will check for this problem out of hours? (Maybe by switching the DB option on for a while and then back off? If you switch the option on, does it check the whole database? Or does it just do checks during the actual update?) Hopefully there is a better way than that to do it...
Also, am I right in saying that CHECKSUM is new to 2005? And what do you guys use: Checksum, Torn Page Detection or None?
Hello everybody,First: SQL Server 2000 sp3a, HP cluster server, MS 2003 server,database recovery model simpleTorn page detection:When I have this option turned on, processes conected with updating andwriting in database, was MUCH more slower, than if I've this optionturned off.It seams to me, that when this option is turned on, the sqlserver ismuch more slower by any operation connected with writing, than withoutthis option.This option is required for ensurance, that the data are writtenproperly on the media.My question is:if I have my database running under cluster, with RAID hd system, whichcontains write cache, with additional checking, that the data will bewritten correctly, is it necessary for me to keep this option turnedon?Auto shrink:When it is turned on, does it affect performance?Personaly, I don't think so, but somebody is insysting on it, and Iwould like to have an information from independent source about that.Best regardsMatik
Hello, I'm wondering if anyone has any insight as to what happened here. We had a DBCC checkdb error as follows:
Server: Msg 8946, Level 16, State 12, Line 2 Table error: Allocation page (16:3769008) has invalid PFS_PAGE page header values. Type is 0. Check type, object ID and page ID on the page.
So we then ran: dbcc traceon(3604) go dbcc page (<dbname>,16,3769008,1,0) go dbcc traceoff(3604) go
and got: Server: Msg 8939, Level 16, State 98, Line 1 Table error: Object ID 99, index ID 0, page (16:3769008). Test (IS_ON (BUF_IOERR, bp->bstat) &&bp->berrcode) failed. Values are 2057 and -1.
Allocation Status ----------------- GAM (16:3578624) = NOT ALLOCATED SGAM (16:3578625) = NOT ALLOCATED PFS (16:3769008) = 0x0 0_PCT_FULL DIFF (16:3578630) = NOT CHANGED ML (16:3578631) = NOT MIN_LOGGED
DATA: -----
Slot 0, Offset 0x4040 ---------------------
Row at offset 16448 may be corrupt. Hex dump of remaining -8258 bytes:
The database is not marked suspect and we have backups to restore, if necessary, but I'm wondering if anyone can interpret what the dbcc commands are telling us and how we can diagnosis what's happening...
Hi all. I'm getting an error mssage which tells me I have a torn page:ODBC error 823 (HY000) I/O error (torn page) detected during read atoffset 0x00000080b5c000 in file 'D:WINSUPPORTDATAWin SupportDatabase_2_Data.NDF'.I ran DBCC CHECKDB and it returned no errors:CHECKDB found 0 allocation errors and 0 consistency errors in database'WIN Support Database'.I really don't know what to do at this point. I'm not a databaseadministrator, just a programmer, and our DBA is not here. Anysuggestions?Thanks,Jennifer
1) Error: 823, Severity: 24, State: 2) I/O error (torn page) detected during read at offset 0x0000001455a000..erc
Network team thinks this was caused by low disk space. I was running a database shrink last night, and someone had transferred a file to server prior to my job that took 90% of disk. My shrink job failed and then 20 minutues later we satrted to recieve the two above mentioined.
Can a failed shrink job - which failed due to low disk space cause a torn page to occur? I have not heard of this...
hi all... my prod database facing the problem i mention. it show this error when i run some of the query.
Error: 823, Severity: 24, State: 2 I/O error (torn page) detected during read at offset 0x000000ffd0e000 in file 'F:dsUnit'.
i running dbcc checkdb on it. this is the result
DBCC results for 'dsActive3'. DBCC results for 'sysobjects'. There are 472 rows in 8 pages for object 'sysobjects'. DBCC results for 'sysindexes'. There are 728 rows in 39 pages for object 'sysindexes'. DBCC results for 'syscolumns'. There are 4243 rows in 106 pages for object 'syscolumns'. DBCC results for 'systypes'. There are 26 rows in 1 pages for object 'systypes'. DBCC results for 'syscomments'. There are 281 rows in 66 pages for object 'syscomments'. DBCC results for 'sysfiles1'. There are 7 rows in 1 pages for object 'sysfiles1'. DBCC results for 'syspermissions'. There are 49 rows in 1 pages for object 'syspermissions'. DBCC results for 'sysusers'. There are 13 rows in 1 pages for object 'sysusers'. DBCC results for 'sysproperties'. There are 0 rows in 0 pages for object 'sysproperties'. DBCC results for 'sysdepends'. There are 2776 rows in 18 pages for object 'sysdepends'. DBCC results for 'sysreferences'. There are 26 rows in 1 pages for object 'sysreferences'. DBCC results for 'sysfulltextcatalogs'. There are 0 rows in 0 pages for object 'sysfulltextcatalogs'. DBCC results for 'sysfulltextnotify'. There are 0 rows in 0 pages for object 'sysfulltextnotify'. DBCC results for 'sysfilegroups'. There are 4 rows in 1 pages for object 'sysfilegroups'. DBCC results for 'INSTRUCTION'. There are 0 rows in 0 pages for object 'INSTRUCTION'. DBCC results for 'DATASWEEP_CODES'. There are 180 rows in 4 pages for object 'DATASWEEP_CODES'. DBCC results for 'DATASWEEP_SEQUENCE'. There are 7 rows in 1 pages for object 'DATASWEEP_SEQUENCE'. DBCC results for 'OPERATION'. There are 52 rows in 1 pages for object 'OPERATION'. DBCC results for 'Results'. There are 2 rows in 1 pages for object 'Results'. DBCC results for 'DC_BLOB'. There are 8 rows in 1 pages for object 'DC_BLOB'. DBCC results for 'PRODUCTION_LINE'. There are 2 rows in 1 pages for object 'PRODUCTION_LINE'. DBCC results for 'DS_PERSISTENT_OBJECT'. There are 5 rows in 1 pages for object 'DS_PERSISTENT_OBJECT'. DBCC results for 'EQUIPMENT'. There are 0 rows in 0 pages for object 'EQUIPMENT'. DBCC results for 'RESOURCE_CONDITION'. There are 2 rows in 1 pages for object 'RESOURCE_CONDITION'. DBCC results for 'IMAGE_BLOB'. There are 0 rows in 0 pages for object 'IMAGE_BLOB'. DBCC results for 'ROUTE'. There are 125 rows in 2 pages for object 'ROUTE'. DBCC results for 'JOB_CONFIG'. There are 19 rows in 1 pages for object 'JOB_CONFIG'. DBCC results for 'UNIT_CHECKLIST'. There are 0 rows in 0 pages for object 'UNIT_CHECKLIST'. DBCC results for 'JOB_SCHEDULE'. There are 10 rows in 1 pages for object 'JOB_SCHEDULE'. DBCC results for 'LOCATION'. There are 1 rows in 1 pages for object 'LOCATION'. DBCC results for 'WORK_ORDER_ITEMS'. There are 4375 rows in 139 pages for object 'WORK_ORDER_ITEMS'. DBCC results for 'NOTE_BLOB'. There are 0 rows in 0 pages for object 'NOTE_BLOB'. DBCC results for 'ROUTE_STEP'. There are 599 rows in 13 pages for object 'ROUTE_STEP'. DBCC results for 'PART'. There are 1827 rows in 69 pages for object 'PART'. Server: Msg 8928, Level 16, State 1, Line 1 Object ID 475148738, index ID 0: Page (5:610106) could not be processed. See other errors for details. Server: Msg 8939, Level 16, State 1, Line 1 Table error: Object ID 475148738, index ID 0, page (5:610106). Test (IS_ON (BUF_IOERR, bp->bstat) &&bp->berrcode) failed. Values are 2057 and -1. Server: Msg 8928, Level 16, State 1, Line 1 Object ID 475148738, index ID 0: Page (5:610107) could not be processed. See other errors for details. Server: Msg 8939, Level 16, State 1, Line 1 Table error: Object ID 475148738, index ID 0, page (5:610107). Test (IS_ON (BUF_IOERR, bp->bstat) &&bp->berrcode) failed. Values are 2057 and -1. Server: Msg 8928, Level 16, State 1, Line 1 Object ID 475148738, index ID 0: Page (5:610165) could not be processed. See other errors for details. Server: Msg 8939, Level 16, State 1, Line 1 Table error: Object ID 475148738, index ID 0, page (5:610165). Test (IS_ON (BUF_IOERR, bp->bstat) &&bp->berrcode) failed. Values are 2057 and -1. Server: Msg 8928, Level 16, State 1, Line 1 Object ID 475148738, index ID 0: Page (5:610166) could not be processed. See other errors for details. Server: Msg 8935, Level 16, State 1, Line 1 Table error: Object ID 475148738, index ID 1. The previous link (5:611693) on page (5:610224) does not match the previous page (5:610106) that the parent (5:614865), slot 80 expects for this page. DBCC results for 'DS_TABLESPACE_MAP'. There are 6 rows in 1 pages for object 'DS_TABLESPACE_MAP'. DBCC results for 'BOM_PART_LIST'. There are 9927 rows in 196 pages for object 'BOM_PART_LIST'. DBCC results for 'SITE_INFO'. There are 1 rows in 1 pages for object 'SITE_INFO'. DBCC results for 'RESOURCE_ARC'. There are 2 rows in 1 pages for object 'RESOURCE_ARC'. DBCC results for 'CARRIER_COMPARTMENT'. There are 0 rows in 0 pages for object 'CARRIER_COMPARTMENT'. DBCC results for 'RESOURCE_QUEUE'. There are 2 rows in 1 pages for object 'RESOURCE_QUEUE'. DBCC results for 'TRX_BASE'. Server: Msg 8936, Level 16, State 1, Line 1 Table error: Object ID 475148738, index ID 1. B-tree chain linkage mismatch. (5:610618)->next = (5:610224), but (5:610224)->Prev = (5:611693). Server: Msg 8981, Level 16, State 1, Line 1 Table error: Object ID 475148738, index ID 1. The next pointer of (5:610619) refers to page (5:610343). Neither (5:610343) nor its parent were encountered. Possible bad chain linkage. Server: Msg 8934, Level 16, State 1, Line 1 Table error: Object ID 475148738, index ID 1. The high key value on page (5:610616) (level 0) is not less than the low key value in the parent (0:1), slot 0 of the next page (5:610618). Server: Msg 8935, Level 16, State 1, Line 1 Table error: Object ID 475148738, index ID 1. The previous link (5:611693) on page (5:610618) does not match the previous page (5:610616) that the parent (5:614865), slot 94 expects for this page. Server: Msg 8936, Level 16, State 1, Line 1 Table error: Object ID 475148738, index ID 1. B-tree chain linkage mismatch. (5:610616)->next = (5:610618), but (5:610618)->Prev = (5:611693). Server: Msg 8935, Level 16, State 1, Line 1 Table error: Object ID 475148738, index ID 1. The previous link (5:611693) on page (5:610619) does not match the previous page (5:610618) that the parent (5:614865), slot 95 expects for this page. Server: Msg 8978, Level 16, State 1, Line 1 Table error: Object ID 475148738, index ID 1. Page (5:610619) is missing a reference from previous page (5:611693). Possible chain linkage problem. Server: Msg 8935, Level 16, State 1, Line 1 Table error: Object ID 475148738, index ID 1. The previous link (5:611693) on page (5:610620) does not match the previous page (5:610619) that the parent (5:614865), slot 96 expects for this page. Server: Msg 8978, Level 16, State 1, Line 1 Table error: Object ID 475148738, index ID 1. Page (5:610620) is missing a reference from previous page (5:611693). Possible chain linkage problem. Server: Msg 8978, Level 16, State 1, Line 1 Table error: Object ID 475148738, index ID 1. Page (5:610622) is missing a reference from previous page (5:610620). Possible chain linkage problem. Server: Msg 8928, Level 16, State 1, Line 1 Object ID 587149137, index ID 0: Page (4:523911) could not be processed. See other errors for details. Server: Msg 8939, Level 16, State 1, Line 1 Table error: Object ID 587149137, index ID 0, page (4:523911). Test (IS_ON (BUF_IOERR, bp->bstat) &&bp->berrcode) failed. Values are 2057 and -1. There are 67236767 rows in 2321938 pages for object 'TRX_BASE'. CHECKDB found 0 allocation errors and 18 consistency errors in table 'TRX_BASE' (object ID 475148738). DBCC results for 'CHECKLIST_ITEM'. There are 0 rows in 0 pages for object 'CHECKLIST_ITEM'. DBCC results for 'DCS_LIST'. There are 0 rows in 0 pages for object 'DCS_LIST'. DBCC results for 'DCS_PARM'. There are 253 rows in 7 pages for object 'DCS_PARM'. DBCC results for 'RESOURCE_QUEUE_LINK'. There are 2 rows in 1 pages for object 'RESOURCE_QUEUE_LINK'. DBCC results for 'RESOURCE_ROUTE'. There are 1 rows in 1 pages for object 'RESOURCE_ROUTE'. DBCC results for 'DS_OBJECT_BLOB'. There are 45 rows in 1 pages for object 'DS_OBJECT_BLOB'. DBCC results for 'TEST_INSTANCE'. There are 5836487 rows in 159046 pages for object 'TEST_INSTANCE'. DBCC results for 'FORM_BLOB'. There are 647 rows in 4 pages for object 'FORM_BLOB'. DBCC results for 'ROUTE_ARC'. There are 1047 rows in 9 pages for object 'ROUTE_ARC'. DBCC results for 'UNIT'. There are 5139230 rows in 309518 pages for object 'UNIT'. CHECKDB found 0 allocation errors and 2 consistency errors in table 'UNIT' (object ID 587149137). DBCC results for 'INSTRUCTION_BLOB'. There are 0 rows in 0 pages for object 'INSTRUCTION_BLOB'. DBCC results for 'ROUTE_QUEUE'. There are 599 rows in 5 pages for object 'ROUTE_QUEUE'. DBCC results for 'INSTRUCTION_LIST'. There are 0 rows in 0 pages for object 'INSTRUCTION_LIST'. DBCC results for 'LOT'. There are 313 rows in 12 pages for object 'LOT'. DBCC results for 'ROUTE_QUEUE_LINK'. There are 599 rows in 9 pages for object 'ROUTE_QUEUE_LINK'. DBCC results for 'SCHEMA_VERSION'. There are 2 rows in 1 pages for object 'SCHEMA_VERSION'. DBCC results for 'PRODUCT_ROUTE_P_LINE_REL'. There are 0 rows in 0 pages for object 'PRODUCT_ROUTE_P_LINE_REL'. DBCC results for 'SERIAL_NUMBER'. There are 1 rows in 1 pages for object 'SERIAL_NUMBER'. DBCC results for 'PRODUCT_RS_WC_REL'. There are 0 rows in 0 pages for object 'PRODUCT_RS_WC_REL'. DBCC results for 'RESOURCE_STEP'. There are 2 rows in 1 pages for object 'RESOURCE_STEP'. DBCC results for 'STATION'. There are 53 rows in 1 pages for object 'STATION'. DBCC results for 'SUBROUTINE_BLOB'. There are 354 rows in 2 pages for object 'SUBROUTINE_BLOB'. DBCC results for 'TMPL_TBOM'. There are 2 rows in 1 pages for object 'TMPL_TBOM'. DBCC results for 'TBOM_PART_LIST'. There are 0 rows in 0 pages for object 'TBOM_PART_LIST'. DBCC results for 'TMPL_TBOM_PART_LIST'. There are 0 rows in 0 pages for object 'TMPL_TBOM_PART_LIST'. DBCC results for 'TRX_CARRIER'. There are 0 rows in 0 pages for object 'TRX_CARRIER'. DBCC results for 'TRACKED_OBJECT_HISTORY'. There are 18576505 rows in 922365 pages for object 'TRACKED_OBJECT_HISTORY'. DBCC results for 'TRX_CONSUMPTION'. There are 0 rows in 0 pages for object 'TRX_CONSUMPTION'. DBCC results for 'TRACKED_OBJECT_STATUS'. There are 5461496 rows in 587509 pages for object 'TRACKED_OBJECT_STATUS'. DBCC results for 'TRX_GENEALOGY'. There are 0 rows in 0 pages for object 'TRX_GENEALOGY'. DBCC results for 'XFR_DELETION_LOG'. There are 21699 rows in 279 pages for object 'XFR_DELETION_LOG'. DBCC results for 'UNIT_CHECKLIST_ITEM'. There are 0 rows in 0 pages for object 'UNIT_CHECKLIST_ITEM'. DBCC results for 'XFR_EXTRACT_LOG'. There are 7150 rows in 289 pages for object 'XFR_EXTRACT_LOG'. DBCC results for 'DS_LIST_ITEM'. There are 800 rows in 11 pages for object 'DS_LIST_ITEM'. DBCC results for 'HIERARCHY_LEVEL'. There are 10 rows in 5 pages for object 'HIERARCHY_LEVEL'. DBCC results for 'XFR_LOAD_LOG'. There are 0 rows in 0 pages for object 'XFR_LOAD_LOG'. DBCC results for 'XFR_SCHEMA_OBJECT'. There are 87 rows in 2 pages for object 'XFR_SCHEMA_OBJECT'. DBCC results for 'XFR_UPDATE_RELATIONSHIPS'. There are 37 rows in 1 pages for object 'XFR_UPDATE_RELATIONSHIPS'. DBCC results for 'BOX'. There are 305676 rows in 7968 pages for object 'BOX'. DBCC results for 'USER_SEQUENCE'. There are 0 rows in 0 pages for object 'USER_SEQUENCE'. DBCC results for 'DC_dst_CorrectiveAction'. There are 0 rows in 0 pages for object 'DC_dst_CorrectiveAction'. DBCC results for 'ACCOUNT'. There are 1 rows in 1 pages for object 'ACCOUNT'. DBCC results for 'DC_dst_ShiftDefinition'. There are 0 rows in 0 pages for object 'DC_dst_ShiftDefinition'. DBCC results for 'DC_dst_5DX'. There are 0 rows in 0 pages for object 'DC_dst_5DX'. DBCC results for 'XFR_INTERVAL_ID'. There are 10327 rows in 27 pages for object 'XFR_INTERVAL_ID'. DBCC results for 'DC_dst_ComponentLocation'. There are 0 rows in 0 pages for object 'DC_dst_ComponentLocation'. DBCC results for 'PROCESS_CONTROL'. There are 0 rows in 0 pages for object 'PROCESS_CONTROL'. DBCC results for 'DC_dst_Account'. There are 0 rows in 0 pages for object 'DC_dst_Account'. DBCC results for 'REFERENCE_DESIGNATOR'. There are 9927 rows in 51 pages for object 'REFERENCE_DESIGNATOR'. DBCC results for 'DC_dst_PasteMeasurement'. There are 0 rows in 0 pages for object 'DC_dst_PasteMeasurement'. DBCC results for 'TEST_DEFINITION'. There are 4 rows in 1 pages for object 'TEST_DEFINITION'. DBCC results for 'DC_dst_ReportActionLog'. There are 0 rows in 0 pages for object 'DC_dst_ReportActionLog'. DBCC results for 'DC_dst_CAR_NCR'. There are 0 rows in 0 pages for object 'DC_dst_CAR_NCR'. DBCC results for 'TEST_RESULT'. There are 10376737 rows in 199778 pages for object 'TEST_RESULT'. DBCC results for 'DC_dst_NonConObject'. There are 0 rows in 0 pages for object 'DC_dst_NonConObject'. DBCC results for 'DEFECT_REPAIR_ENTRY'. There are 3240433 rows in 169991 pages for object 'DEFECT_REPAIR_ENTRY'. DBCC results for 'DC_dstr_UserFormAndReports'. There are 4 rows in 1 pages for object 'DC_dstr_UserFormAndReports'. DBCC results for 'SITE_CONFIG'. There are 1 rows in 1 pages for object 'SITE_CONFIG'. DBCC results for 'DC_dst_NonConformance'. There are 0 rows in 0 pages for object 'DC_dst_NonConformance'. DBCC results for 'BOM'. There are 173 rows in 4 pages for object 'BOM'. DBCC results for 'DC_dstr_GroupSecurity'. There are 1 rows in 1 pages for object 'DC_dstr_GroupSecurity'. DBCC results for 'DC_dst_RMA_SerialNumber'. There are 82197 rows in 7129 pages for object 'DC_dst_RMA_SerialNumber'. DBCC results for 'SUBROUTINE'. There are 354 rows in 10 pages for object 'SUBROUTINE'. DBCC results for 'DC_dst_DPMO_Information'. There are 0 rows in 0 pages for object 'DC_dst_DPMO_Information'. DBCC results for 'TBOM'. There are 5139874 rows in 64048 pages for object 'TBOM'. DBCC results for 'DC_dst_LineSchedule'. There are 0 rows in 0 pages for object 'DC_dst_LineSchedule'. DBCC results for 'DC_dst_ECO_Details'. There are 0 rows in 0 pages for object 'DC_dst_ECO_Details'. DBCC results for 'HN_dst_PartDimension'. There are 1053 rows in 19 pages for object 'HN_dst_PartDimension'. DBCC results for 'DC_dst_ECO_Header'. There are 0 rows in 0 pages for object 'DC_dst_ECO_Header'. DBCC results for 'WORK_CENTER'. There are 0 rows in 0 pages for object 'WORK_CENTER'. DBCC results for 'ICT_Tester_Name'. There are 39 rows in 1 pages for object 'ICT_Tester_Name'. DBCC results for 'WORK_ORDER'. There are 4397 rows in 164 pages for object 'WORK_ORDER'. DBCC results for 'DS_LIST'. There are 72 rows in 2 pages for object 'DS_LIST'. DBCC results for 'HN_dst_StationDimension'. There are 1 rows in 1 pages for object 'HN_dst_StationDimension'. DBCC results for 'HIERARCHY'. There are 2 rows in 1 pages for object 'HIERARCHY'. DBCC results for 'CARRIER'. There are 0 rows in 0 pages for object 'CARRIER'. DBCC results for 'CHECKLIST'. There are 1 rows in 1 pages for object 'CHECKLIST'. DBCC results for 'DBPS'. There are 1 rows in 1 pages for object 'DBPS'. DBCC results for 'DCS'. There are 17 rows in 1 pages for object 'DCS'. DBCC results for 'APP_USER'. There are 2078 rows in 197 pages for object 'APP_USER'. DBCC results for 'DS_OBJECT'. There are 45 rows in 2 pages for object 'DS_OBJECT'. DBCC results for 'dtproperties'. There are 0 rows in 0 pages for object 'dtproperties'. DBCC results for 'CHECKOUT_ITEM'. There are 0 rows in 0 pages for object 'CHECKOUT_ITEM'. DBCC results for 'FORM'. There are 647 rows in 15 pages for object 'FORM'. DBCC results for 'CONSUMED_PART'. There are 0 rows in 0 pages for object 'CONSUMED_PART'. CHECKDB found 0 allocation errors and 20 consistency errors in database 'dsActive3'. repair_allow_data_loss is the minimum repair level for the errors found by DBCC CHECKDB (dsActive3 ). DBCC execution completed. If DBCC printed error messages, contact your system administrator.
now the main problem is when i restore the latest backup i have. it also facing the problem. the other backup i got is one more week older than this.
can anyone help me? i cant affort to has 2 week data loss
HiWhen trying to create an SqlServer job, clicking OK' I got the message"Error 823: I/O error (torn page) detected during read at offset..... infile 'd:sqlserverMSSQLdatamsdata.mdf'. The job was not saved"I asked about the problem a little to find out that I need to restore abackup of MSdb because the job definitions are there. I rrad some otherplace (I can't remember where) that in order to restore MSdb I need torestore a backup of Master as well.Can anyone give me some more information on this.Is there any way else to do it besides restoring the backup ?To restore, do I need to recreate the database or just restore theappropiate backup file ?David Greenberg
Hi all,One of my database was suspected, So I try to recover database then itgives this errorErr. 823 Torn Page Detected823, ... 24, spid51 i/o error Torn Page (Detected)during read at offset 0x0000000040e0000 in file .........How can I recover my SQL Server 2000 Database? Please helpThanks
I have inherited a poorly administered/maintained database thatcontains the following error:"I/O error (torn page) detected during read at offset 0x000018ee23e000in file 'F:Program FilesISSRealSecure SiteProtectorSiteDatabaseDataRealSecureDB.mdf"I do not have database backups and so therefore cannot restore fromthem. I want to move the database to a new platform and somehowrepair the torn page. Is this possible?
we are running a maintainance plan on sql 2000 standard edition, got the error,
[2] Database db_source: Check Data Linkage... [Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 8928: [Microsoft][ODBC SQL Server Driver][SQL Server]Object ID 1221579390, index ID 0: Page (1:197116) could not be processed. See other errors for details. [Microsoft][ODBC SQL Server Driver][SQL Server]Table error: Object ID 1221579390, index ID 0, page (1:197116). Test (IS_ON (BUF_IOERR, bp->bstat) &&bp->berrcode) failed. Values are 2057 and -1. [Microsoft][ODBC SQL Server Driver][SQL Server]CHECKDB found 0 allocation errors and 2 consistency errors in table 'xxx'(object ID 1221579390). [Microsoft][ODBC SQL Server Driver][SQL Server]CHECKDB found 0 allocation errors and 2 consistency errors in database 'db_source'. [Microsoft][ODBC SQL Server Driver][SQL Server]repair_allow_data_loss is the minimum repair level for the errors found by DBCC CHECKDB (db_source noindex).
when i run query on anlyzer select * from xxx, i got the error Server: Msg 823, Level 24, State 2, Line 1 I/O error (torn page) detected during read at offset 0x000000603f8000 in file 'F:Program FilesMicrosoft SQL ServerMSSQLdatadb_Data.MDF'.
I got help from Dan Guzman on how to set single-user-mode.Thank you very much.After seting single-user-mode, I run DBCC CHECKDB('MYDATABASE',REPAIR_REBUILD)Tehre are error messages.How can I repair torn page problem?Thanks.*** Sent via Developersdex http://www.developersdex.com ***Don't just participate in USENET...get rewarded for it!
Does anyone have any experience detecting and repairing torn pages? Does Optimization repair Torn Pages ? Any help or resources would be much appriciated.
Hello faculties,i'm encountering a strange a deadlock problem on my remote serverwhich is used to give application demo to the client. It has happenedthat on one of the databases a deadlock situation is taking place.What is the most detailed way to detect such the cause of such adeadlock to the innermost level of detail, like what statements, storedprocedures and locks are causing the deadlock to occur.Guys! please help me out!Thanks in advanceDebian*** Sent via Developersdex http://www.developersdex.com ***
I have been trying to use the Clustering algorithm for Anomaly Detection, but it has been quite difficult to get correct results for PredictCaseLikelihood. Using a very large number of clusters helped, but there are other problems. The algorithm does not take into account all the columns in my nested table, but only uses Exists/Not Exists for the nested table key column. In my case the nested table contains also a column with a count of key attribute.
I am about to abandon the Sql Data Mining.
Does anyone have more insights into tuning the Clustering algorithm for anomaly detection?
I have created one reports but all the records are displaying on one page.find a solution to display the records page by page. I created the same report without group so the records are displaying in page by page.
The following was found as a solution to detecting non-printable characters in a string. I can find no explanation of how the COLLATE function is used.
how the COLLATE function affects the search string to find the non-printable characters?
patindex('%[^ !-~]%' COLLATE Latin1_General_BIN, titlel) as [Position]
what are the best ways to action on the Deadlock issues. I am aware how a deadlock is occurred and we can get the queries causing by the Trace, and Profiler. What will en best steps to Investigate from DBA end later collecting the stats.What steps will ensure to get these deadlocks addressed.
Hi, I'm would like know if the analysis service data mining enables to detect anomalies from "normal" behavior/patterns of data (1), and alert about such anomalies when detected (2). both above sql server relational DB (3).
I'm using the Service Broker to parallize my processes (I know that the Service Broker was not designed for that purpose), however it's working quite well.
I use the broker procedure to start procedures which all process all a part of the workload. When the procedure fails because of a lock timeout (or for that concern, for whatever reason), I rollback the transaction (which also roll back my message received on the queue so that it can be retried at a later time.). And this is where my problem lies, if there are 5 sequential rollbacks of messages then the poison message detection kicks in and disables the queue, stopping all the processing. :(
Is there a way to disable poison message detection? I have implemented my own stop-mechanism through a counter system on a per sub-task system so if I could disable poison message detection that would be ideal.
If this is not possible is there a way to turn the queue back on automatically so that it will continue processing the messages on the queue?
I am trying to install RS on Vista. I notice that the list of IIS features to turn on, listed in the KB article and blog entries, mentions a "Windows Authentication" IIS feature to check under Security. I don't have that (although I have one labeled "Basic Authentication") -- I'm on a "workgroup" computer at home.
Does this mean that you simply can't install RS on Vista unless you're joined to a domain? Thanks,
I am monitoring my replication process and I have a problem with the loop detection, I can see origined transacctions in the server, executed in the same for the replication.
The subscriptions configuration is sp_helpsubscription
I am trying to return a 0 when there is a NULL as a result, I thought that Sum(ISNULL(Payment,0) would do the trick, I was wrong...any ideas: MonthlyCredit = (Select Sum(ISNULL(Payment,0)) from transaction as t Where AccountNumber = @AccountNumber and Month(t.PayDate) = @Month )