Post reply

SQL Capacity planning

  • May 5, 2019 at 11:41 am

    #3635800

    Hi,

    I am assigned to migrate the databases from SQL Standard 2012 /2014 to SQL Enterprise 2016.

    Around 20 production databases with different database sizes comes all togther 500gb. In these 20 dbs only 3 databases are having maximum IO.  In these 3 dbs one is around 300gb and other 2 dbs are 100gb and 50 gb. And rest of the database sizes are in MB & no such IO operations.

    To build the new server i need to give all CPU,HardDisk,Memory, etc details to my boss. so that he will create new VM. Once he creates the new VM then i will install SQL 2016. next i will take backups one by one and restore it in destination new server.

    For this how should i calculate capacity planning like (core,cpu,harddisk,storage etc.)

    Pls guide me follow some best practice to build new server. What are the things i need to takecare while suggesting the server and SQL capacity planning?

    Thanks in advance.

  • May 6, 2019 at 7:50 pm

    #3636646

    Step 1 would be to determine if you have any capacity problems with your existing system. 😉

    --Jeff Moden

    RBAR is pronounced "ree-bar" and is a "Modenism" for Row-By-Agonizing-Row.
    First step towards the paradigm shift of writing Set Based code:
    ________Stop thinking about what you want to do to a ROW... think, instead, of what you want to do to a COLUMN.

    Change is inevitable... Change for the better is not.

    Helpful Links:
    How to post code problems
    How to Post Performance Problems
    Create a Tally Function (fnTally)

  • May 6, 2019 at 8:57 pm

    #3636683

    Storage should be easy. You have ideas of the current size and can guess at growth by looking at metrics for the dbs of database size. Allow for data growth/pad in this.

    For CPU, do you have issues now? As Jeff noted, you don't want to have issues in the future, so if you have problems now, you will need to increase resources available. How many CPUs, what speed, how much in use are they and do they peak?

    For RAM, target server memory is a counter on the current machine. That will tell you what your existing instance would like. I tend to add lots of RAM if I can, as this is a cheap way to prevent performance issues.

     

    These are simple recommendations, and there is more to it, but it's a complex subject.

Viewing 3 posts - 1 through 2 (of 2 total)

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