10 days ago I upgraded several databases from an old, standalone, 32-bit Windows 2003/SQL Server 2000 server. I moved the databases onto a new SQL Server 2008 x64 SP1 instance, one of 6 running on our core 4-node cluster (4 x 2005 instances and 2 x 2008).
Shiny, spangly, highly available, modern, up-to-date, 64-bit, loads more memory and processing power… nothing could go wrong, right?
First problem was exposed by transactional data replication, into a subscribed table with triggers on it, and this was causing Access Violations and Stack Dumps, so frequently that the small(ish) system partition was soon filled with mini-dumps. We worked around this by changing the trigger (but the underlying issue remains unsolved).
But a more problematic issue is frequent, intermittent, connection problems and timeouts (in SSMS, the default timeout period is a mere 15 seconds). This server is used in my company’s factory, in assembling PCs. The timeouts have been causing so many problems to PCs being build and burn-in tested on the production line that I am getting serious heat.
So .. installed CU5 for SP1 at the weekend.. the timeouts went away for a tantalising 48 hours and I truly believed the issue was fixed, only for it to return with a vengeance this morning. Cue seriously unhappy users and senior managers. Severity A case logged with Microsoft Premier Support. No resolution yet … but a very tired DBA here after a pretty stressful 10 days at work. Christmas can’t come too soon.
MPS are really good and the service can’t be faulted, but I’d rather not have to talk to them at all (with the greatest of respect!)