Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase

Multiple SQL servers Consolidation to one Single SQL 2012 Cluster Expand / Collapse
Author
Message
Posted Sunday, February 17, 2013 5:44 AM
Grasshopper

GrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopper

Group: General Forum Members
Last Login: Monday, November 11, 2013 1:14 AM
Points: 20, Visits: 260
Hi, Experts.

I have a project which includes different 180 databases on around 18 different SQL servers with different versions (2000,2005,2008,2008 R2...) and collations.

now i want to consolidate to sql 2012 cluster
how much cpu,ram and space need for the physical cluster server.

I would appreciate any help on this

Regards
Shafiq
Post #1420965
Posted Monday, February 18, 2013 5:15 AM
SSCrazy

SSCrazySSCrazySSCrazySSCrazySSCrazySSCrazySSCrazySSCrazy

Group: General Forum Members
Last Login: Today @ 5:34 AM
Points: 2,859, Visits: 3,187
You need to do some capacity planning.

The areas you need to work out are: a) CPU requirement, b) Memory requirements, c) IO Requirement d) Total disk space requirement.

To get CPU requirement, you need to normalise CPU usage to Total GHz Requirement, using the formula (number of CPU Cores * processor speed in GHz) / peak CPU use percentage. For example, if you have a 2-core server running at 2.1 GHz that has a peak use of 70%, then the total GHz requirement for that server is 2.94 GHz. Do this for all of your SQL Server workloads and add the numbers together and you know how big your new servers will need to be.

You can do a similar calculation for memory. Find out how much memory SQL Server is using on each of your instances. Then subtract 0.5GB for each instance as an overhead cost, giving you a rough figure of how much memory your new servers will need.

For IO requirement, you will need to look at what your monitoring tools can provide. If you already have monitoring in place for IO workload, then you have historical figures for each disk drive you can add together to get the IO requirement for your new servers. If you do not have any monitoring, then you need to get a Perfmon trace running, and collect figures over at least a 2-week period before you have anything you can rely on.

For disk space, add together the disk space used by all of your databases.

After you have done all of this, you should have enough information to specify your new production servers. You should not expect this specification to be a 100% match for the final workload as you will only know the final workload once it has gone live, but you should be within +/- 25% of what you need.

25% may seem a large margin, but even professional capacity planning experts will not give a level of accuracy any better than that.


Original author: SQL Server FineBuild 1-click install and best practice configuration of SQL Server 2014, 2012, 2008 R2, 2008 and 2005. 28 July 2014: now over 30,000 downloads.
Disclaimer: All information provided is a personal opinion that may not match reality.
Concept: "Pizza Apartheid" - the discrimination that separates those who earn enough in one day to buy a pizza if they want one, from those who can not.
Post #1421145
Posted Monday, February 25, 2013 10:17 PM
Grasshopper

GrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopper

Group: General Forum Members
Last Login: Monday, November 11, 2013 1:14 AM
Points: 20, Visits: 260
I really appreciate your nice conversation.

Thanks for your Comprehensive report.
shafiq.
Post #1423879
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse