Click here to monitor SSC
SQLServerCentral is supported by Redgate
Log in  ::  Register  ::  Not logged in
Home       Members    Calendar    Who's On

Add to briefcase

Migrating 6.5, 2000, and 2005 to SQL 2008 in a Virtual server environment Expand / Collapse
Posted Thursday, September 16, 2010 9:17 AM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Thursday, September 16, 2010 9:08 AM
Points: 1, Visits: 0
I'm looking to see if any one here has some advise about this topic. We have several SQL instances as mentioned in the topic and we'd like to create one SQL environment on the virtual server.

I'm thinking it's not necessary to separate the drives as you would on a hardware configuration. That said, I still think it makes sense to have the data on and log file an different virtual disks from the Operating system.

I'm curious about the migration to 2008.

I believe we can follow the same path as this KB, but wondered if someone here has a recommendation

Thank you for your time,


Post #987354
Posted Thursday, March 3, 2011 7:02 AM

SSC Veteran

SSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC Veteran

Group: General Forum Members
Last Login: Monday, April 21, 2014 10:39 AM
Points: 214, Visits: 568
We have just migrated our development and test environment to virtual. But we still follow the hardware configuration as how we did previously; OS and binaries are different from data and log, tempdb is totally separate and we also have backup drive separate.

Imagination is more important than knowledge-Albert Einstein
Post #1072516
Posted Thursday, June 16, 2011 1:21 PM



Group: General Forum Members
Last Login: Saturday, February 27, 2016 7:13 PM
Points: 137, Visits: 669
When you virtualize you still want to follow best practices (i.e. data, log, backups and tempdb on separate drives). However, this is where understanding the abstraction of resources becomes critical to understand.

When you virtualize you can create a separate VMDK/VHD (read also: virtual disk) for each drive. The OS sees each one as new drive, you mount them and letter them so now you have your C, D, E, F, T drives. The problem comes in is if all of those VMDK/VHD files were cut from the same LUN, then you haven't gained anything since they're all going to be sharing IO which is bad. Also if that one LUN goes out then you lose everything, again, negating your perceived benefit.

In order to truly "do it right", each VMDK/VHD should be on separate LUNS and those LUNS shouldn't be shared with any other IO-intensive applications (such as Exchange). This is where you need to become REALLY good friends with your SAN admin and come up with something that works. Hope this helps!

/* Backups are worthless, Restores are priceless */

Get your learn on at SQL University!
Follow me on Twitter | Connect on LinkedIn
My blog:
My book: Pro Server 2008 Policy-Based Management
Post #1126913
Posted Monday, August 11, 2014 5:59 AM



Group: General Forum Members
Last Login: Tuesday, November 29, 2016 5:40 AM
Points: 2,722, Visits: 1,219
You may want to check out the white paper for your upgrades.

Also some SQL 2008 R2 upgradfe info here, courtesy of Arron Bertrand. Some good points raised.


Who looks outside, dreams; who looks inside, awakes. – Carl Jung.
Post #1601812
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse