SQL Database Capacity Planning
Capacity Planning
I have been tasked with the following for my department.
(1) Determining data grow over the past two or three years – for example using our contracts table as bench marking, dependencies and database to forecast capacity planning for the next five years.
(2) Capacity planning database wise to determine disk space sizes
Can somebody lead me in the right direction?
I have been tasked with the following for my department.
(1) Determining data grow over the past two or three years – for example using our contracts table as bench marking, dependencies and database to forecast capacity planning for the next five years.
(2) Capacity planning database wise to determine disk space sizes
Can somebody lead me in the right direction?
Brian Crowe
You can determine the number of contracts in the system at any given time. You know the current size of your database and based on the rate of increase you can extrapolate the number of contracts at any given time in the future. From this you can calculate the estimated size of your database at any given point. You are making a few assumptions in this process but it's workable.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
BriCrowe and Aneesh,
Do any of you have a script I can you to achieve your response?
Do any of you have a script I can you to achieve your response?
You would need to provide some schema information on your contracts table.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
The db has been growing since the past five years.
Current size plus log 83285.00 MB is the largest one I want to use as baseline to forecast capacity planning for the next five years.
See the attached
This-Database-size.docx
Current size plus log 83285.00 MB is the largest one I want to use as baseline to forecast capacity planning for the next five years.
See the attached
This-Database-size.docx
I wouldn't include the log file in your calculations. The log file shouldn't change much regardless of your data file size. The log file size is determined by your transaction rate and how often you are doing transaction log backups. Hopefully the example I provided above will give you what you need.
Another option is to implement Datacollector to monitor database size, you need to monitor for at least a month to get an idea of the database growth
ASKER
Thank you
