Question regarding adding instances.

  • Scenario:

    We have 4 customers on a VM. There is only 1 DB per customer and each DB is about 10 to 12 GB in size. Only 2 customers are 24/7. 32 GB of RAM, 4 CPU, 4 customers.

    We are also thinking about adding 2 more instances for 2 more customers.

    Questions: What would be the best route to take with this situation? Adding 2 more instances or have another DB server? How do I even find out how busy they are? Is there any way to understand the load on our current DB Servers?

    "He who learns for the sake of haughtiness, dies ignorant. He who learns only to talk, rather than to act, dies a hyprocite. He who learns for the mere sake of debating, dies irreligious. He who learns only to accumulate wealth, dies an atheist. And he who learns for the sake of action, dies a mystic."[/i]

  • Create a baseline to see what current server utilization is. You may be able to add dozens more databases to the existing environment, or you may be already overloaded.

    Here is a good place to start: http://www.sqlservercentral.com/articles/baselines/94656/

  • tim_harkin (4/14/2014)


    Create a baseline to see what current server utilization is. You may be able to add dozens more databases to the existing environment, or you may be already overloaded.

    Here is a good place to start: http://www.sqlservercentral.com/articles/baselines/94656/%5B/quote%5D

    Thanks,

    "He who learns for the sake of haughtiness, dies ignorant. He who learns only to talk, rather than to act, dies a hyprocite. He who learns for the mere sake of debating, dies irreligious. He who learns only to accumulate wealth, dies an atheist. And he who learns for the sake of action, dies a mystic."[/i]

  • How many DBs are you going to add per new customer ? And why do you want to add 2 instances ?

    You can ask your VM admin to capture the server utilization metrics using Vcenter. Based on that you can decide .

    --

    SQLBuddy

  • sqlbuddy123 (4/14/2014)


    How many DBs are you going to add per new customer ? And why do you want to add 2 instances ?

    We are adding 2 instances for 2 more customers we have. Each instance will have 1 DB.

    "He who learns for the sake of haughtiness, dies ignorant. He who learns only to talk, rather than to act, dies a hyprocite. He who learns for the mere sake of debating, dies irreligious. He who learns only to accumulate wealth, dies an atheist. And he who learns for the sake of action, dies a mystic."[/i]

  • New Born DBA (4/15/2014)


    sqlbuddy123 (4/14/2014)


    How many DBs are you going to add per new customer ? And why do you want to add 2 instances ?

    We are adding 2 instances for 2 more customers we have. Each instance will have 1 DB.

    If only one DB per customer, you could probably put those 2 instances on the existing server itself. Before that check if that VM is having any resource contention issues. If yes, then you should put them on a different VM.

    --

    SQLBuddy

  • sqlbuddy123 (4/15/2014)


    If only one DB per customer, you could probably put those 2 instances on the existing server itself. Before that check if that VM is having any resource contention issues. If yes, then you should put them on a different VM.

    Thanks for your help.

    Since I mentioned, each DB is about 10 - 12 GB in size and we are not running into any issues since DBs are not heavily updated. Well, we can go either way but the idea is to prevent if we run into any issues later on.

    "He who learns for the sake of haughtiness, dies ignorant. He who learns only to talk, rather than to act, dies a hyprocite. He who learns for the mere sake of debating, dies irreligious. He who learns only to accumulate wealth, dies an atheist. And he who learns for the sake of action, dies a mystic."[/i]

Viewing 7 posts - 1 through 6 (of 6 total)

You must be logged in to reply to this topic. Login to reply