Select Failures

Paul Randal walks us through a complicated scenario involving corruption:

An interesting corruption problem cropped up on the MCM distribution list yesterday and after I figured it out, I thought it would make a good blog post in case anyone hits a similar problem.

In a nutshell, the problem was corruption such that a simple SELECT * query failed, but a SELECT * query with an ORDER BY clause worked.

This is interesting, but hopefully you don’t encounter these types of problems very often in your environment.

Related Posts

CHECKDB For Read-Only Databases?

Erik Darling answers a reader’s question: So, can you run DBCC CHECKDB on a read only database? Should you run DBCC CHECKDB on a read only database? tl;dr: YES AND YES! Here’s why: Many forms of corruption that I’ve seen have come from storage. Sure, there have been bugs that were to blame, but yeah. […]

Read More

Getting Ahead Of Corruption

Mike Walsh has some recommendations before you have corrupt databases: So. Always. Always. ALWAYS choose to be proactive and prepared. Don’t wait for corruption to catch you! When we do our SQL Server health assessments, seeing the findings that together mean you aren’t prepared for corruption is a huge red flag. Partially it is because as a consultant, I […]

Read More

Categories

December 2015
MTWTFSS
« Nov Jan »
 123456
78910111213
14151617181920
21222324252627
28293031