Resource allocation between SQL Server instances

Tags:
SQL Server
Hi, My question is whether you bother with separate instances of SQL Server on a single box (for whatever reason), or whether you just run all the DBs in the same instance with just the one version/security model. In either case, how do you deal with resource-hungry apps hogging CPU, Mem etc on the server? Thanks, Dan.
1

Answer Wiki

Thanks. We'll let you know when a new response is added.

A lot of dependencies here.

Do you have a box that can handle multiple instances of SQL Server?

What kind of security model are you trying to accomplish here?

Are you setting up databases for one company/department, or multiple companies/departments?

One of the biggest considerations is the server that would house the multiple instances…

Discuss This Question: 1  Reply

 
There was an error processing your information. Please try again later.
Thanks. We'll let you know when a new response is added.
Send me notifications when members answer or reply to this question.
  • Bwartman
    I work for an organization that manages 500+ instances of SQL Server. We have no more than 4 instances/cluster, with those clusters running in an active/active configuration. Given your information, it's important to aggressively pursue your development team (if these are systems developed in-house) to optimize their DB and application design. We normally recommend that our "standard" servers (4-proc server with 16 GB of RAM running under W2K3) have no more than two instances (4 per cluster) due to the need of failover capacity. If you're running only one server you can run up to 4 instances. It's especially important to set memory limits on your instances if you plan on using AWE memory; failure to do so could result in memory starvation issues for the OS and/or 1 or more of your installed instances. Other than that, thorough monitoring of your server resources is your best guide on what limits your server will tolerate. We get a lot of requests from customers who want to know precisely what kind of memory/CPU/etc. usage they can expect from SQL Server. The best answer is that while we can give general estimates, the best advice is based on historical usage, therefore we advise proceeding carefully and cautiously when wanting to load multiple instances onto a server/cluster.
    0 pointsBadges:
    report

Forgot Password

No problem! Submit your e-mail address below. We'll send you an e-mail containing your password.

Your password has been sent to:

To follow this tag...

There was an error processing your information. Please try again later.

Thanks! We'll email you when relevant content is added and updated.

Following

Share this item with your network: