CSS SQL Server Engineers

Huh? This is not meant to be a brain teaser. The purpose of this post is to help you avoid problems with SQL Server 2008 setup before you run..well setup. Why not take advantage of known fixes we have for setup to avoid the problem in the first place...

A few questions have come up about the differences between the features you can install on SQL Server 2008 called Management Tools - Basic   and Management Tools - Complete. So I thought I'd blog about these to resolve any questions you might have...

UPDATE TO THIS POST: We now have a fix for this problem as documented at 968829 FIX: Error message when you try to upgrade an instance of SQL Server 2005 to SQL Server 2008: "Wait on the Database Engine recovery handle failed. Check the SQL Server...

I have blogged on the various ways to determine the state of recovery but this week I was involved in an interesting discussion around rollback. The transaction has run for 14 hours and then a KILL SPID was issued. The SPID goes into rollback and happed...

We have posted the first cumulative update for SQL Server 2008 aptly named Cumulative Update 1 (CU1). I thought before you considered installing a patch for SQL Server 2008, you would like to see a tour of what it looks like compared to SQL Server 2005...

We have been seeing a few cases where the Windows Service for Reporting Services will not start after applying the following fix: MS08-052: Description of the security update for GDI+ for SQL Server 2005 Service Pack 2 GDR: September 9, 2008 ...

I ran across a teaser this week that makes for a interesting blog post.  SQL Server uses a common batch parser for the SQLCMD, OSQL, SSMS Query Window in Command mode and various other locations. The primary job of this parser is to identify GO delimited...

  SCENARIO SQL Server fails to install a WOW64 instance (x86) an on a computer with more than 32 CPUs.    During setup you will encounter a SQL Server failed to start message.      SQL Server is attempting to determine the...

Error 17888: All schedulers on Node ## appear deadlocked due to a large number of worker threads waiting on <<RESOURCE>>. Process Utilization ##%. SQL Server creates a Scheduler Monitor thread for each node.    One of the Scheduler...