question

venkatreddy avatar image
venkatreddy asked

capacity planning specifications and guidelines needed.

I need guidelines for preparing capacity planning chart for the server which is already in production.Actually i just gone through Maximum Capacity Specifications for SQL Server but it is for maximum capacity.Im briefly giving my server and databases details below

1) SQL Server with 8 databases,all databases are in production. 2) daily growth rate on an average 300MB 3) Server is at client location,connecting to 150 machines. 4) On an average 3,50,000 records inserting into the databases.

here also few questions,

1)as a DBA how should i analyze the capacity planning for the given details?

2)What are intial set of things should i look into first before planning?

3)Hardware resources allocation?? will this comes under DBA tasks or this sould be taken care by the network admin?

4)what will be the best practices of effective memory management(CPU and Memory)?

5) How should i plan for disk space allocation and which RAID levels should i plan for?

6)should we consider the best data accessing methods to access the data from the databases? or this will not comes under tasks of DBA.

7)Last but not least as a middle level DBA what are the minimum things should i keep in mind while doing analysis on CP?

Can anybody provide me guidelines in preparing CP chart.For any details like no of database objects in each databse etc.,i can give details if you are interested for further analysys.thanks in advance..

configurationsubjectiveperformance-metricsdocumentationcapacity-planning
10 |1200
Toggle Comment visibility. Current Visibility: Viewable by all users

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

1 Answer

·
Fatherjack avatar image
Fatherjack answered

While there is a lot of info here there are still bits missing and you relly need to be talking with your 'customers', by which I mean the business owners of the data.

info point 1 - the number of databases is largely irrelevant, whether its 1 or 100 wont matter if the 1 is very busy and the 100 are rarely used.

info point 2 - is this 300MB per database or total? Regardless - work out how long you want the server to maintain the data and then work out how long it will take to fill the hard drive's remaining space - you probably need more storage space.

q1 - yes, especially if you would be responsible if it isnt done
q2 - business growth, disaster recovery and business continuity - these need to be scaled up as the production system grows
q3 - this depends on your employer and the team communications. I would hope to work with network admin and hardware teams, supplying them with info I have and discussing the best options for the business needs.
q4 - not sure how you want to manage these ... get as much as possible as early as possible. In my experience when you get to a point where CPU is an issue then is no cheaper to get extra CPUs than to buy completely new hardware. Vitrual environments excluded
q5 - you need to choose the RAID config to compliment your data usage
q6 - as dba you should recommend the best way to access your data, explaining security risks/benefits of different options, etc
q7 - not sure what you mean here

10 |1200
Toggle Comment visibility. Current Visibility: Viewable by all users

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

Write an Answer

Hint: Notify or tag a user in this post by typing @username.

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.