Thanks. I'm glad it was at all helpful. Keep an eye out for Thomas LaRock articles too. I know he's got a new one coming becuase he let me review...

Although, now that I think...

Usually we bump it up to 20 as a general rule.

Or, you might want to consider increasing the cost threshold for parallelism on your server. I've usually found the default is just too low, causing queries that don't need it...

Is it the log file? Maybe you're in Full Recovery mode and not running log backups?

Pick up a copy of Kalen Delaney's Inside SQL Server 2005: The Storage Engine. That will give you a lot of the kind of information that you're looking for.

The correlated sub-queries at the top of your select statement are going to give you coniptions as this scales. The more data it hits, the slower these will run:

...

You will get slightly better performance combining the two procedures. Avoiding the recompile and the waits that it entails will help.

Honestly though, it's not a solution to your problem. You're...

Log file full

Backup failed

Errors with a severity higher than 16

Those are the three most useful ones.

First, and most important, before you worry about a tool, you need to focus on your process. Discipline around how and when you deploy is more important than the tool...

More than a few of us on are Linked-In. It is like Gail said though, I would only recommend someone after a pretty long relationship that involves more than a...

You may need to post your code because that should work fine. As one of the previous posts said, you may have your PK improperly defined.

It sure makes the editorial I just read in SQL Server Magazine sound a little weird. He mentions the release "later this year" of 2008. I thought it sounded strange...

Thanks for all the responses.

I got one yesterday, I think it was maybe the third one I've received over the years (I'm hardly one of the "go-to" guys). It was...

Cool. Thanks for sharing.