Solution : https://service.sap.com/sap/support/notes/142731 (SAP Service marketplace login required)
Summary :
This SAP Note outlines procedures for checking database consistency in Microsoft SQL Server, emphasizing the use of the DBCC CHECKDB command to identify logical and physical inconsistencies. Key recommendations include running checks during low-activity periods due to high I/O demand and potential for deadlocks in SQL Server 7. The note details structured approaches to address corruptions, categorizing them into transient, non-critical, and critical types, and suggests respective remedies from simple SQL commands to full database restoration depending on the severity and effects of the corruption. It also highlights the importance of investigating underlying hardware issues to prevent recurrent problems.
Key words :
\program files\microsoft sql server\mssql$<sid>\, \program files\microsoft sql server\mssql\, /pae switch set inthe boot, long checkdb requires free space, multi-processor 32-bit servers, relational database management systems, set single user mode, reset single user mode, dbcc printed error messages, windows server 2003 support package 1
Related Notes :
| 1597910 | Handling of database corruptions on SQL Server |
| 1420452 | FAQ: Restore and recovery with MS SQL Server |
| 1237674 | SQL Error 5128: Write to sparse file failed |
| 1006920 | DBCC Checks show 8914 Errors on SQL Server 2005 |
| 325443 | SQL error 9004 |
| 161189 | Stack overflow exception with CHECKDB |
| 139945 | SAP Database Monitor for MS SQL Server |