December 11, 2014 at 6:01 am
Hi,
In general how much % of D & L drives free space required for a database.
I heard that D:/ Drive free space should be database mdf file size X 20% of mdf file size.
Is there any same calculations for Log Drive also?
Please let me know how you calculate the required empty spaces for drives
December 11, 2014 at 6:14 am
I calculate it based on what the database seems to need.
Are you creating new databases or trying to calculate this for existing databases?
Also, what you really need to know is how much the database is going to grow based on the largest or most frequent queries. Knowing how much information these queries will be pulling back will enable you to properly set up the auto-growth properties.
December 11, 2014 at 6:48 am
I need for existing database.
If database current size is about 350GB and growth is about 70GB/month. How do you calcaulate the D:/Drive free space and L:/Drive free space
December 11, 2014 at 6:55 am
I calculated the database growth based on the backup sizes for a month.
Is that ok? Do you have any another script to calculate database growth
December 11, 2014 at 6:59 am
Depends how often you want to add space to your drives.
There's no need to have free space on the drive, as long as there's free space in the database files.
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
December 11, 2014 at 6:59 am
I apparently am not understanding what your needs are. Do you need to size the database for auto-growth? Are you trying to add more space to the drive where your database files are? Or are you just trying to determine how much free space your database has right now?
It seems to me you already have the figures you need for determining how much extra space you'll need over a 3 or 6 or 12 month period of database growth, which is not the same thing as "free space."
December 11, 2014 at 7:00 am
GilaMonster (12/11/2014)
Depends how often you want to add space to your drives.There's no need to have free space on the drive, as long as there's free space in the database files.
I'm so glad someone else found a different way of interpreting the question. @=)
December 11, 2014 at 10:36 am
It is showing available free space is 20MB for that database.
December 11, 2014 at 10:40 am
So again, what are you trying to accomplish?
Without that context, your original question is rather meaningless to the rest of us.
December 11, 2014 at 11:28 am
Trying to findout the way that how to calculate the additional disk spaces required for the existing database?
December 11, 2014 at 11:37 am
If you are sure that your growth rate holds steady at 70 GB per month, then take that number multiplied by the number of months you're projecting. Add that to the current allocated size of the database (not the space used size). Then factor in a couple of percentage points (I usually go by 5%) to come up with a total.
When budget time comes around, I look at an 18 month growth curve so that I don't have to ask for space during the year, just at budget time. Using your numbers:
350GB and growth is about 70GB/month...
70 GB * 18 = 1260 GB + 350 GB = 1610 GB * 1.05 (5%) = 1690.50 GB. Subtracting the 350 GB from that, I would come up with needing about 1340 GB (rounding down) for my 18 month growth projections.
Yes, it looks like a high number. But no matter what number you come up with, someone in finance will try to argue it down. So estimate high and know your minimum (calculated for 12 months instead of 18, for example) as a hard minimum. Let them argue you down. Don't underestimate and lose even your hard minimum for the year's growth.
EDIT: You might also take into consideration how much drive space you already have that isn't being consumed by the database. For instance, if you already have 700 GB of hard drive space with only 350 GB consumed, you could subtract the difference from the 1340 to come up with a more reasonable number for the budget gurus.
December 11, 2014 at 2:44 pm
Don't forget the other side of the issue.
Have you compressed large indexes when useful?
Have you reviewed that you have the best clustered index on each table? After that, have you removed unused indexes (or no longer needed indexes)?
Do you have test tables you can remove? Logging tables you can remove/reduce?
SQL DBA,SQL Server MVP(07, 08, 09) "It's a dog-eat-dog world, and I'm wearing Milk-Bone underwear." "Norm", on "Cheers". Also from "Cheers", from "Carla": "You need to know 3 things about Tortelli men: Tortelli men draw women like flies; Tortelli men treat women like flies; Tortelli men's brains are in their flies".
December 12, 2014 at 5:19 am
ScottPletcher (12/11/2014)
Don't forget the other side of the issue.Have you compressed large indexes when useful?
Have you reviewed that you have the best clustered index on each table? After that, have you removed unused indexes (or no longer needed indexes)?
Do you have test tables you can remove? Logging tables you can remove/reduce?
In addition, there's also the possibility that the database is growing that quickly because of poorly written queries that pulling in much more data then they eventually keep, leaving a lot of tables allocated but unused. So it would be a really good idea to identify what is causing the 70GB monthly growth to verify that it is indeed real growth and not just nuisance growth.
December 12, 2014 at 6:28 am
ramana3327 (12/11/2014)
I need for existing database.If database current size is about 350GB and growth is about 70GB/month. How do you calcaulate the D:/Drive free space and L:/Drive free space
After making sure that the growth isn't due to simple waste and that you've accounted for the possible removal of data due to aging (archive process), as the others have suggested, and if you still end up with a predicted 70GB growth per month, my initial SWAG would be to multiply that number by at least 30 to plan the disk space need for the next 2 years (24 for the months... +6 for unexpected growth) for the "D:" drive.
Once you figure out what the monthly growth is on the log files, I'd do similar... that's provided that you're not doing something crazy like a scheduled or regular manual shrink.
--Jeff Moden
Change is inevitable... Change for the better is not.
December 12, 2014 at 8:27 am
Jeff Moden (12/12/2014)
ramana3327 (12/11/2014)
I need for existing database.If database current size is about 350GB and growth is about 70GB/month. How do you calcaulate the D:/Drive free space and L:/Drive free space
After making sure that the growth isn't due to simple waste and that you've accounted for the possible removal of data due to aging (archive process), as the others have suggested, and if you still end up with a predicted 70GB growth per month, my initial SWAG would be to multiply that number by at least 30 to plan the disk space need for the next 2 years (24 for the months... +6 for unexpected growth) for the "D:" drive.
Once you figure out what the monthly growth is on the log files, I'd do similar... that's provided that you're not doing something crazy like a scheduled or regular manual shrink.
I don't like the idea of buying excess disk two years out, as disks inevitably get better and cheaper over time. Unless you have an extremely delayed disk implementation process, I'd go out no more than one year. You have no realistic idea what disk growth/usage will look like 12 months from now, let alone two years out.
SQL DBA,SQL Server MVP(07, 08, 09) "It's a dog-eat-dog world, and I'm wearing Milk-Bone underwear." "Norm", on "Cheers". Also from "Cheers", from "Carla": "You need to know 3 things about Tortelli men: Tortelli men draw women like flies; Tortelli men treat women like flies; Tortelli men's brains are in their flies".
Viewing 15 posts - 1 through 15 (of 15 total)
You must be logged in to reply to this topic. Login to reply