SQL Clone
SQLServerCentral is supported by Redgate
 
Log in  ::  Register  ::  Not logged in
 
 
 


Multiple instances on a VM


Multiple instances on a VM

Author
Message
Sioban Krzywicki
Sioban Krzywicki
SSCommitted
SSCommitted (1.9K reputation)SSCommitted (1.9K reputation)SSCommitted (1.9K reputation)SSCommitted (1.9K reputation)SSCommitted (1.9K reputation)SSCommitted (1.9K reputation)SSCommitted (1.9K reputation)SSCommitted (1.9K reputation)

Group: General Forum Members
Points: 1867 Visits: 8090
We're trying to decide if we should use a single large instance of SQL Server or multiple instances on the same server. This is for a dev environment.
So far, I have these things to watch out for:
Have to limit max RAM per instance so no instance grabs it all
There will be I/O contention and CPU contention between instances since the different instances won't coordinate with each other.
It limits the available RAM for In-Memory tables
It sets lower limits to the amount of RAM available for any given query, causing artificial "contention" even when there's nothing else running at the time.

Anything I'm missing?

Anyone have strong feelings for or against?

--------------------------------------
When you encounter a problem, if the solution isn't readily evident go back to the start and check your assumptions.
--------------------------------------
It’s unpleasantly like being drunk.
What’s so unpleasant about being drunk?
You ask a glass of water. -- Douglas Adams
Greg Edwards-268690
Greg Edwards-268690
SSCommitted
SSCommitted (1.6K reputation)SSCommitted (1.6K reputation)SSCommitted (1.6K reputation)SSCommitted (1.6K reputation)SSCommitted (1.6K reputation)SSCommitted (1.6K reputation)SSCommitted (1.6K reputation)SSCommitted (1.6K reputation)

Group: General Forum Members
Points: 1574 Visits: 8495
Most of what you are describing are performance related considerations.
Less resources may not be a bad thing in some cases.
Tuning / load testing would likely be something done in an environment that may more closely mirror production.
Multiple Dev environments would tend to isolate work of developers, which could offer some advantages if a restore is needed.

So if just Dev / Prod, your considerations may be a bit different than if you have QA processes in between.
Rudyx - the Doctor
Rudyx - the Doctor
SSCarpal Tunnel
SSCarpal Tunnel (4.8K reputation)SSCarpal Tunnel (4.8K reputation)SSCarpal Tunnel (4.8K reputation)SSCarpal Tunnel (4.8K reputation)SSCarpal Tunnel (4.8K reputation)SSCarpal Tunnel (4.8K reputation)SSCarpal Tunnel (4.8K reputation)SSCarpal Tunnel (4.8K reputation)

Group: General Forum Members
Points: 4849 Visits: 2503
Do not 'over provision' - SQL does not like having memory and/or CPUs managed in and out.

Most applications can handle that but SQL Server really, really hates it.

In looking at one huge instance vs many smaller ones I would ask myself the following:
- can we take all of development down in one huge instance for patching
or
would it make sense to stagger the patching outages so not all of development is down at once

The more important question is licensing costs.

With one huge instance you could either license the entire ESX cluster by CPU pairs or the huge SQL instance by CPU pairs.
I am referring to SQL 'enterprise' edition - 20+ processors and 128 GB RAM on each (even a small ESX host has a couple of HP DL-380s with 2x12 CPU configurations) a total of 48 processors to license. That is 24 - 2 packs at about 16.5k per 2 pack or roughly $800,000.

Now if you had smaller instances with SQL 'standard' edition, the 2 pack licensing cost goes down to 3.6k or $173,000.
However you can only V-motion once every 90 days under the 'standard’ edition – 4 - 12 CPU and 64 GB RAM instances would fit.

Even more economical, since this is development, put developer 'edition' on there for $50. However each and every developer would need an MSDN Developer license - they start at about $650 and go all the way to about 3K. So if it is pure development, say you had 50 developers and you got them all average MSDN licenses for about 1 K per you'd be out roughly $50,000.

Regards
Rudy Komacsar
Senior Database Administrator

"Ave Caesar! - Morituri te salutamus."
Go


Permissions

You can't post new topics.
You can't post topic replies.
You can't post new polls.
You can't post replies to polls.
You can't edit your own topics.
You can't delete your own topics.
You can't edit other topics.
You can't delete other topics.
You can't edit your own posts.
You can't edit other posts.
You can't delete your own posts.
You can't delete other posts.
You can't post events.
You can't edit your own events.
You can't edit other events.
You can't delete your own events.
You can't delete other events.
You can't send private messages.
You can't send emails.
You can read topics.
You can't vote in polls.
You can't upload attachments.
You can download attachments.
You can't post HTML code.
You can't edit HTML code.
You can't post IFCode.
You can't post JavaScript.
You can post emoticons.
You can't post or upload images.

Select a forum

































































































































































SQLServerCentral


Search