Using undocumented DBCC WRITEPAGE to instigate SQL Server database corruption
In this tip we look at the undocumented command DBCC WRITEPAGE to corrupt a SQL Server database and then use the command to undo the corruption.
2018-10-01
2,109 reads
In this tip we look at the undocumented command DBCC WRITEPAGE to corrupt a SQL Server database and then use the command to undo the corruption.
2018-10-01
2,109 reads
2018-06-19
8,292 reads
Having already shown how to corrupt a database, and then how nonclustered indexes can be corrupted independently, in this post Brent Ozar explains how you can detect corruption.
2017-08-15
6,725 reads
This trigger will send mail notification once a row is written in the suspect pages table
2017-03-03 (first published: 2017-02-21)
503 reads
Corrupt SQL Server databases are the worst nightmare of any SQL Server professional. In any environment, from small business to enterprise, the compromise of integrity and availability of the data can constitute a business emergency. This is especially the case in those organizations reliant on an OLTP data model, for a high-volume website. SQL Server database corruption and disruption of the transaction processing system can cause business repercussions such as large financial losses, a drop in reputation or customer retention, or contractual SLA problems with the service provider, if not managed in-house.
2013-02-18
3,385 reads
How do you recover from corruption if your organization doesn't have a disaster recovery handbook? And how can you prevent the same corruption from recurring?
2013-01-29
8,619 reads
Explanation of how to repair a database in SQL 2005 Enterprise which is mirrored.
2010-05-10
4,383 reads
Returning author Wayne Sheffield recently had some database corruption - read about how it was fixed.
2010-03-03
8,796 reads
At times database corruption happens and no good recovery path is available. It is possible to salvage data from indexes using query hints.
2010-01-19
5,974 reads
Why does DBCC CHECKDB find corruption errors that disappear? Does tempdb really cause performance issues? Are there any drawbacks to using the FILESTREAM datatype? Paul Randal answers these reader questions and more.
2009-03-27
4,251 reads
It’s been forgotten about and neglected for few years but I’ve decided to dust...
I am honored to announce that I have been renewed as a Microsoft MVP...
By Rohit Garg
🔍 Demystifying KTLO: A Deep Dive into Keep The Lights On Work in IT...
Comments posted to this topic are about the item How a Legacy Logic Choked...
Comments posted to this topic are about the item Navigating Multi Platform Realities in...
I have tried a number of times to export and then import my SSMS...
For the Question of the day, I am going to go deep, but try to be more clear, as I feel like I didn't give enough info last time, leading folks to guess the wrong answer... :) For today's question: You’re troubleshooting a performance issue on a critical stored procedure. You notice that a previously efficient query now performs a full table scan instead of an index seek. Upon investigating, you find that an NVARCHAR parameter is being compared to a VARCHAR column in the WHERE clause. What is the most likely cause of the query plan regression?
See possible answers