November 29, 2016 at 6:44 am
Is it possible to estimate database capacity based on following details?
Volume of records held in the database- 18000000
Volume of updates per day thru overnight batch- 50k
Database growth expected to be 5% per annum
Thanks
November 29, 2016 at 6:52 am
Sqlsavy (11/29/2016)
Is it possible to estimate database capacity based on following details?Volume of records held in the database- 18000000
Volume of updates per day thru overnight batch- 50k
Database growth expected to be 5% per annum
Thanks
Define "capacity" in this scenario.
Best,
Kevin G. Boles
SQL Server Consultant
SQL MVP 2007-2012
TheSQLGuru on googles mail service
November 29, 2016 at 7:01 am
Is it possible roughly to calculate size of the database based on just the details that I've provided?
If not, then what are criteria that should be considered?
November 29, 2016 at 7:10 am
Sqlsavy (11/29/2016)
Is it possible to estimate database capacity based on following details?Volume of records held in the database- 18000000
Volume of updates per day thru overnight batch- 50k
Database growth expected to be 5% per annum
Thanks
Further on Kevin's question, please refine the figures provided as those do not make too much sense; 5% of 18x10^6 is 9x10^5 while 365x50000 is 18.25x10^6 or more than 100% of the initial size, leaving the difference of the predicted growth and the aggregated daily batches for a year in the ratio of roughly 1:20.
😎
November 29, 2016 at 7:12 am
Sqlsavy (11/29/2016)
Is it possible roughly to calculate size of the database based on just the details that I've provided?
No.
18 million rows means nothing when a row can be anything from about 3 bytes up to GB in size (with LOBs)
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
November 29, 2016 at 7:21 am
Sqlsavy (11/29/2016)
Is it possible to estimate database capacity based on following details?Volume of records held in the database- 18000000
Rows, not records. And who cares. 300,000,000 rows at 2k/row is 585,937.5 kb or 572mb or .55gb. In short, the number of rows doesn't mean a darned thing. You care about how much data you have stored. So counting up your rows, to 18,000,000, presumably across multiple different tables with different numbers of columns of all different sorts of data types equates to... Something. That's measured by the data size, not the row count.
Volume of updates per day thru overnight batch- 50k
Transactions? Updates, inserts and deletes? Just pure addition to the size of the data being stored? It really depends. If it's a measure of the transactions, then no, this isn't any way to tell about database growth. It's a good way to measure your log growth and understand what's needed there, but that's all. If it's literal data growth, yeah, that's a useful measure for understanding how big your database is and how it's likely to grow in the future.
Database growth expected to be 5% per annum
Thanks
Only if you literally measure data growth can you make these predictions. Also, it's going to be a constantly changing prediction. Most businesses, and most databases, that are successful, grow. You'll see more data over time so the prediction will change. However, measuring growth, say over the last month (again, by data, not by rows or by transactions), will give you a number to project out with.
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
November 30, 2016 at 4:54 am
Thank you all for the inputs. Much appreciated!
Viewing 7 posts - 1 through 6 (of 6 total)
You must be logged in to reply to this topic. Login to reply