This blogging thing sucks you in, doesn't it? Not content with having an ongoing series on disaster recovery and CHECKDB (with another 6 and 25 more posts planned respectively), I'm starting a new series on fragmentation. This will begin from first principles...

Ever see something like this in your SQL Errorlog? SQL Server has encountered 1 occurrence(s) of I/O requests taking longer than 15 seconds to complete on file [T:\MSSQL\DATA\tempdb.mdf] in database [tempdb] (2). The OS file handle is 0x00000838. The...

I'm sure you've been there - something causes corruption in the database. You blame the hardware, the hardware guys blame the software. There's no smoking gun and the hardware diagnostics come back clean. What can you do? SQLIOStress This is the...

If you're interested in a little background, I did an email interview with Steve Jones of sqlservercentral.com over the last few weeks. Check it out at http://www.sqlservercentral.com/columnists/sjones/spotlightonsqlserverwithpaulrandall.asp

Having multiple users each owning various objects is commonplace in the database world. When one user wants to give access of their object to another user -- that’s when administration of databases gets rather interesting. Consider the following...

Here is the summary and the link to the white papers. Working with TempDB This white paper describes how SQL Server 2005 uses tempdb . Many improvements in SQL Server 2005 optimize tempdb usage and make it easier to manage and to troubleshoot. A...

Sounds kinda funny, doesn't it? I mean, who here doesn't have someone breathing down your neck every time you go past your backup window? So why would you NOT optimize for fast backups? It just makes sense. You do backups every day, so they should be...

With the release of SQL Server 2005 comes a plethora of new security related features. Over time we will cover these in detail. To start, let's look at the world of encryption. When it comes to protecting data we can take a mile high view of this problem...

Hmmm - I sat for 5 minutes thinking of something amusing to say to start this one off and nothing came to mind, so I'm afraid this will be a humor-free post. Maybe I'm jet-lagged from being on the East coast all last week. As with all things related...

I just saw this on one of the forums - it's another wonderful piece of advice to studiously avoid. Scenario: Drive goes bad and causes a torn page error. User wants to fix the problems and move the database to a different drive. The advice given...

Emergency mode repair? In a couple of previous posts I explained how the two worst things you could do to your database are rebuilding your transaction log and running REPAIR_ALLOW_DATA_LOSS . Well, in SQL Server 2005, we combined them into a new documented...

I was asked this several times at TechEd so I'd like to answer it publicly. It's kind of complicated to explain so bear with me as I do it. Basically, NO! Earlier versions of SQL Server (for example, 6.5) had their problems but from 7.0 the storage...

TechEd's done and dusted for another year, and what a blast we had! It's incredible to think of the number of customers who stopped by the SQL Server DAT section of the Technical Learning Center to pepper us with questions, and even more so to think...

In my chalk/talk at TechEd yesterday, I asked the crowd "what's the purpose of repair?" One person got it right. The purpose is not to save data. Surprised? The purpose is to get the database back to a structurally and transactionally consistent state...

10 points if you answered "don't be daft, never! " and minus several million is you answered anything else. Yes, if you have no backups and your hardware has corrupted your transaction log then you have no choice but to rebuild it, but this should never...

So, I'd like to make a couple of assertions about backup and disaster recovery that will hopefully get you to thinking, and just might change the way you think about the topic. There are two distinct motivations for doing backups, and they imply differing...

This is a question that's come up several times at TechEd already and is a nice second part to the post I made late last night about shrink. The answer is usually a most emphatic 'no, its far better to manage the growth of your data files manually'. ...

.. this is an old one, but its poorly understood and it just surfaced again today so I thought I'd share it. Situation: customer keeps his indexes nicely defragemented during the day so that his range scan queries perform well. Every morning, he comes...

Luckily the 8.40am Alaska Airlines direct flight from Seattle>Boston was on time as I'm guessing it was 85% Microsoft! TechEd got off to a great start yesterday with the keynotes - pretty amazing to be in a conference room with 10000 other people...

Yes, finally I come clean and tell all. It's an open secret that there's an undocumented DBCC command called DBCC PAGE that you can use to look at the contents of database pages. I've recommended in forum postings that people use it and Product Support...

Collection Manager Starter Kit Overview The Collection Manager is a rich client application that enables you to create and manage any type of collection. A sample database is included, and you can create any additional number of custom...

As you can guess from the title, I'm planning a long series over the summer to go into the guts of how CHECKDB works (both the consistency checks part and the repair part). And as you can guess from 'CHECKDB', I'm already bored with putting DBCC in front...

Defines couple of ways to load UNIX data file...

Have you ever seen an error like: Process 51:0 (dbc) UMS Context 0x018DA930 appears to be non-yielding on Scheduler 0. Or in SQL Server 2005: Process 51:0:0 (0xdbc) Worker 0x036BA0E8 appears to be non-yielding on Scheduler 1. Thread creation...

I've just been itching to post this one. I'm doing a chalk-talk (AKA cabana session, this year AKA Technical Learning Centre session) at TechEd next Wednesday (8.30am 6/14) called 'DBCC CHECKDB: Magic, Monsters, and Myths'. A lot of the material in...