This was another fun filled week with new SQL issues I hadn’t experienced in smaller environments.
1. I installed the wrong version of SQL on a server. It was a miscommunication between the network guy and myself as I read the OS column which was supposed to be Enterprise – I assumed it was SQL version column – anyway that was a couple of hours of work to fix.
2. I had to document all the servers post installation which mainly focused on some standard settings and some user login information. I’m planning a separate post for these issues.
3. I was asked to tune a report that was using sys.dm_db_index_physical_stats on a large DB. It was taking 45 minutes to run – if it returned data or not. I plan to write a separate post on this as well.
4. I found this blog from a guy who’s got some pretty good tips.
It’s been a heckuva week…At my previous job, I went from working with one big beefy 64 bit, dual processor, with 4 GB of RAM and about 200 GB of total space. This week, I installed and configured SQL 2005 64 bit edition on two two-node clusters and three single node clusters. All of them had between 8 and 32 GB of ram, between 4 and 8 processors and one had almost 3 TB of disk space. It’s a bit of a different environment.
Here’s some good site I found on Clustering and SQL performance:
SQL-Server-Performance’s – SQL Server 2005 Clustering Best Practices
Microsoft’s – Clustered SQL Server do’s, don’ts, and basic warnings
Technet’s – Top Tips for SQL Server Clustering
And some more from Microsoft
SQL Server 2005 Failover Clustering
SQL Server 2000 Failover Clustering
Windows Server 2003 R2 Enterprise Edition–Cluster Server
Microsoft Cluster Server Administrator’s Guide
Microsoft Virtual Server 2005 R2
