Always use notifications on your backup jobs. Backup t-logs quite frequently.
I’m presenting at 10:15 AM Saturday, at SQL Saturday in Boston, on “Building Your First SQL Cluster”. I really love presenting this topic–if you want to learn about high availability and disaster recovery concepts, and how they apply to SQL Server.I will cover clustering concepts and hardware requirements. Additionally, I will go over who in your organization needs to involved in this process, and what infrastructure components you need to plan to have in place.
After this session, you will be ready to try your hand at clustering. I’ll post the slides here when I’m done.
In my earlier post “Adding a New Disk to a SQL Cluster Instance“, I needed to clarify something based on a comment. Any drive that gets added to your cluster that is not a mount point, as in occupies a physical drive letter, needs to be dependent on the SQL Server service. I didn’t think to mention that, because I recommended using mount points.
Thanks to reader Shaun Archer in the West Indies for pointing that out in the comments. I’d offer to send him some rum, but I believe he has a better supply chain than I do.
If you’re still on the fence about going to SQL Rally, and need more rationale for why you should go, then check out the GREAT schedule at the website.
Below are the sessions I plan on attending when I’m not presenting my session—Using Data Tier Applications to Deploy Applications to SQL Azure (which I’ll discuss more in another upcoming post).
Aaron Nelson The Dirty Dozen: PowerShell Scripts for the Busy DBA
Wesley Brown – Understanding Storage Systems and SQL Server
Jennifer McCown – T-SQL Code Sins: The Worst Things We Do to Code, and Why
Tim Chapman – Writing faster queries
Edwin Sarmiento – DBA Disaster Recovery Techniques To Keep Handy
Kendra Little – Big and Tall: When to Partition
Devin Knight – Performance Tuning Analysis Services
Jonathan Kehayias Deadlocking for Mere Mortals
Bradley Ball – Page And Row Compression How, When, and Why
That is a wide variety of sessions presented by some of the leading SQL Server professionals in our community—and it’s under $400. You need to make it here!!!
Recently, we got a new SAN (yeah!!!), unfortunately, our SAN vendor’s migration utilities are priced at such a level, that there is no way we were going to use them. So we had to resort to manually moving the disks. Fortunately in this instance all of the directory names and data files were the same, so there was no need to do anything internal to SQL Server. What happens when you have to make those changes will be part II of this post.
I would feel remiss to not include a statement about discussing your storage layout and performance needs with you Storage Administrator, but that’s outside of the scope of this particular blog post.
Of course, with any all activity like this, the #1 rule is TAKE A BACKUP BEFORE DOING ANY OF THIS! This is a NON-destructive process, but better safe than sorry.
If you don’t need to change any directory names—the process is as simple:
- Mount the drives in your cluster (See my post here on how to do that)
- Make your SQL Server service offline–I used failover cluster manager to do this
- Copy the directories from your source drive to your target drive
- Remove the older drives from your cluster service and take them offline (This isn’t a necessity, but I do it to prevent any possible conflict). You can bring these drives back if needed–you are not destroying any data
- Select the drive you had chosen as the root drive (S:\) and change the drive letter to match what your SQL Server instance is expecting. The mount points underneath it should be maintained.
- Make the SQL Server service dependent on the root disk. In order to do this right click on the SQL Server service name > Dependencies Tab > Add. See screenshot below
- Restart your SQL Service–everything should be ready to go.
If anything fails investigate the alert log, for both Windows and SQL Server, and resolve any issues. A common problem would be the dependency or a directory not being copied (generally SQL binary files)
Of course, this is assuming you do not have to change directory names or move any databases. More on that next week.
For some reason this has been hot in my search options of late, and since I’m speaking on “Deploying Your Applications to SQL Azure” there, I needed to figure it out myself. So here’s a brief list of costs for the event.
Registration: $299+$199 for pre-con seminars–so $500
Flight: Orlando is one of the cheapest places one can fly in the US. So go ahead and budget $400, but you can probably get there for two.
Ground Transportation: Shuttles in Orlando seem pricey, so budget $60 round trip for shuttles.
Hotels: The convention hotel is a bit pricey at $159/night, but I found nearby hotels in the $70 range. If you can swing it-get a roommate and share costs. Even estimating 4 nights @$70, say $300.
Meals: Breakfast and lunch are covered by the conference, and if you’re trying to network hard, you can probably find some vendors to invite you to a night time party or a dinner. So you can really save some money there. I’ll include $100 for food, just in case things fall through.
So we’re up to $1400–it’s about half the cost of what going to Seattle for PASS would be, and it’s some really awesome SQL Server training.
More info about SQL Rally here.
Slides here. No comments about steaming piles of DAC, please 🙂
I have the good fortune to be presenting at upcoming events in Philadelphia, Boston, and Orlando.
This weekend at SQL Saturday #69 I will be presenting the following:
10:00 AM Building your first SQL Cluster
12:30 PM (Along with Mark Kromer from Microsoft) Migrate SQL Server Apps to SQL Azure Cloud DB
3:45 PM Deploying SQL Data Tier Applications using SQL 2008R2 and Visual Studio 2010
In Boston at SQL Saturday #71, on April 2, I will be presenting on Building your first SQL Cluster, again..
More details to come later on my presentation at SQL Rally Orlando!