sbs 2011 disks in hyper-v selection

I am in the process of migrating my old sbs 2003 server to a new sbs 2011 before I do the same for a SMB client.
I have already installed it into an expanding vhdx but have not done any data (Exchange, user, etc) yet.
Currently, the vhdx is at 55gb.
Should I convert this to a larger fixed vhdx with the exchange data all in the C: drive of the vhdx?
Should I just attach another vhdx (fixed or expanding) for the Exchange data.
Note: this server will not host any apps or file sharing just email and DC functions.
Planning for space is the concern.
Raid 1 300gb Intel SSD's for all.
Current SBS 2003 Exchange DB is less than 20gb.
My clients production environment is similar except their Exchange DB is about 35gb.
I have not built that server yet.
All file sharing and application serving will be handled by other servers in both environments.
smschulzIT Asked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

David Johnson, CD, MVPOwnerCommented:
if you can put the .vhdx on another physical drive then yes use a separate vhdx.
If the vhdx's are on the same physical drive you will not see any improvement.
Lee W, MVPTechnology and Business Process AdvisorCommented:
I prefer dynamically growing VHDs BUT putting each one on a separate partition will allow them to grow to a maximum (of the partition size) while starting small and preventing fragmentation as an issue - this is valuable if you need to move the files for some reason - a fixed VHD size could result in a 300 GB VHD drive taking an hour to copy vs. a dynamic 300GB VHD drive using only 40GB taking 10 minutes to copy (guestimating the times).

HOWEVER, fragmentation as I understand it on an SSD, should not be an issue, so if you are using SSDs (especially server class SSD), I wouldn't worry about multiple partitions and I'd just use dynamic VHDs.

If you use ONE LARGE PARTITION on the Hyper-V host to store your VHDs, then fragmentation could easily become an issue and you'd want fixed VHDs to optimize performance.
smschulzIT Author Commented:
I am using Intel Server Grade SSD's so how would fragmentation be an issue?
I could add another RAID 1 set and move the vhdx there but would it really be any benefit.
Currently the host machine drives are one big 300gb partition (less actual usable) with the expanding vhdx stored in a folder.
Also it appears that creating another vhdx just for Exchange data is no benefit over just leaving on the original vhdx?
Has Powershell sent you back into the Stone Age?

If managing Active Directory using Windows Powershell® is making you feel like you stepped back in time, you are not alone.  For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why.

David Johnson, CD, MVPOwnerCommented:
I am using Intel Server Grade SSD's so how would fragmentation be an issue?

It's not an issue

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Lee W, MVPTechnology and Business Process AdvisorCommented:
Intel is not a grade.  Are they desktop grade or server grade?  MLC or SLC type SSDs?  Server types are SLC.  Consumer stuff you'll put in your desktop or laptop are MLC.  SLC is more expensive and lasts longer.

The advantage of a separate VHDX for Exchange is that you can easily move it to another disk if it grows beyond current physical disk size constraints.
Cris HannaCommented:
Just as best practice on physical server is to put Exchange off on its own and data on its own the same applies to virtual setup.  if you have a crash/failure/etc on the OS partition then Exchange and data are unaffected
smschulzIT Author Commented:
Lee, I have been an Intel IPD a long time, I know what 'server grade' is.
These are DC S3500, and even though they are MLC they are a supported server SSD from Intel.
... and btw SLC or MLC is not the distinguishing feature  in servers.
I know the difference there too.
I haven't seen any SLC since the old original X25 50nm series.
I would refer you to Intel's for further data.
Lee W, MVPTechnology and Business Process AdvisorCommented:

I checked your profile and you don't have one so there is NO WAY I could know your background since you've decided not to share it.

When I learned SLC / MLC that was the difference for server - haven't kept up on it as perhaps I should have.  NEVERTHELESS, Intel is not a grade.  Had you mentioned the drives by model to begin with, this part of the conversation wouldn't exist.

As I stated before - "HOWEVER, fragmentation as I understand it on an SSD, should not be an issue" - that said, Dynamic VHDs are supposed to perform slightly worse than fixed, but the huge hit you would have been taking in 2008 (and POSSIBLY 2008 R2) should no longer be an issue with 2012 (and possibly 2008 R2 SP1, I don't recall when it was enhanced).
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.