Home > SQL2008 > Changing Gears again.. it’s the life of a DBA

Changing Gears again.. it’s the life of a DBA

When I last wrote my big project was to upgrade our primary business systems to SQL 2008 while we sourced a new application to replace our legacy one.  At the same time I’m a resource for the new application sourcing.

As I began planning upgrading my existing windows 2003/sql 2005 cluster I realized that the resources I needed for my upgrade were already hip deep into the sourcing project.  This kind of resources contention is never a good thing, especially because we are all still on the hook to support the environment and take care of the day to day business needs.

Being a cautious DBA I was planning a side by side upgrade instead of an in-place upgrade and this meant that all of our client workstations, reports, Access routines (gasp!  I know, we have them and rely on them), SSIS packages, etc would need to be pointed to the new cluster and tested before we could cut over.  It sounds like a short list and my first reaction was that it would be easy – we know where all the reports, access routines, etc live so no problem…

Once we dug in and detailed out all the different places that the instance name would have to be changed it became quite daunting very quickly.  Especially considering these systems, reports, packages, and Access routines would all be scrapped in just about 12 months with the new software we are sourcing.
I made a quick couple of lists to help me decide if we should press on – it’s what I do as a first step when making a decision like this.
Pro’s to upgrading to 2008

* we’re back on a platform that  is supported under mainstream support

* I get to use page/row compression

Con’s to upgrading to 2008

* risk that we will miss something in testing and cause an outage for the business

* over allocation of people resources

* we have a stable system now, and upgrades introduce instability

I know there are more benefits to upgrading from 2005 to 2008 than I’ve listed, but to be honest, those are the two that we would have taken advantage of immediately.  After thinking a bit and talking to my team we made the decision to scrap the 2008 upgrade for these business systems.

So, it’s time to switch gears.  I’m focusing on gearing up with SQL 2012, evaluating Always On for HA, planning a new architecture for the new business systems, and keeping my old 2005 cluster running for the next 12 months.

My plan right now, is to make notes of what I’m learning as I go along here on my blog for my own reference – hopefully it will help you as well.

Advertisements
Categories: SQL2008
  1. No comments yet.
  1. No trackbacks yet.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: