Just a quick post about the fact that Microsoft has finally released the SQL Server 2008 R2 Service Pack 3 (Build 10.50.6000.34) few days ago. This will be the last Service Pack to the SQL Server 2008 R2 version and it is mainly just a roll up of all the previously released Cumulative Updates, with few additional fixes.
I just realized that it’s been a year since I started this blog. Here are some quick statistics about where are my readers from and what they are interested about.
When I’m dealing with a problem on a Failover Cluster (not very often, but sometimes) one of the first steps I do is to run the Validation Test. It’s a great tool that’ll usually show what might be the problem, but apparently not always…
For the last couple days I’ve been busy wrecking havoc on a cluster with a Microsoft Cluster PFE on a Cluster Disaster Recovery workshop. Among the scenarios we’ve gone through causing, fixing and then documenting there was one that had a small surprise in store for both of us.
I was reading this blog post by Thomas LaRock (@SQLRockstar) about a database design mistakes and I’ll warmly recommend that anyone who is involved with database design should read it as well. It also got me into thinking about one database design issue which, in my opinion, is not taken into consideration often enough; Database Administration.
A few days ago there was a question in Twitter about options to KILL (SPID) with a long running transaction that was causing a lot of blocking in a mission-critical system. The person asking the question got some helpful tips on how to fix the problem, such as looking at the tables and the indexes and some tools were pointed out to him, like Adam Machanics Sp_WhoIsActive.
I recently did a migration from one SAN to another and decided to write a quick blog post about the procedure I used. In this particular case the difficult part was handled by the SAN administrator as we were moving from one manufacturer to another. He had the pleasure of trying to add disks from two different storage systems to two nodes, which required not a small amount of dismantling features such as MPIO. We did have some problems with disks showing up multiple times, but nothing we couldn’t work around with.
Every once in a while I run into this little issue with cluster validation check that, while not a critical one, can lead to some confusion. When I deploy clusters to my customers one thing I keep telling them is that they need to update their cluster nodes regularly like any other Windows Server. The other thing I keep telling them is that once they’re all properly updated run the validation test that checks the Windows Updates. And yes, that’s a one way to use the validation tool after you’ve done the deployment :)