December 20, 2004 at 6:09 am
Hi all,
I'm new to the forum, so please be nice!
I was just wondering how you all go about doing your capacity planning on databases. I'm about to work this out and so far I've been told as a rough guide to do:
(total col length x num rows) + (total index col length x num index rows) + 10% contingency.
How does this sound? And most importantly, how do I size for the system created tables like sysfiles etc, and also views and stored procs? Any definitive methods?
Many many thanks,
Paula
December 21, 2004 at 1:28 am
See, if this helps:
http://www.microsoft.com/technet/prodtechnol/sql/2000/maintain/sqlops6.mspx
This one is for DB2. Maybe some ideas provided there will also help:
http://www.redbooks.ibm.com/redpieces/abstracts/sg247073.html
--
Frank Kalis
Microsoft SQL Server MVP
Webmaster: http://www.insidesql.org/blogs
My blog: http://www.insidesql.org/blogs/frankkalis/[/url]
December 21, 2004 at 8:15 am
Paula,
If this is not a warehouse/data mart, you're going to need a lot more space than that. First off, for you to optimize indexes, you'd need database freespace to rebuild them. You also need to consider index fillfactors and how much growth you're going to experience in the rowcounts. It's MUCH MUCH easier to manage the database if you allocate the space ahead of time instead of reacting to the database's growth.
As for system tables, they're insignificant unless you have hundreds of thousands of database objects. If you have enough drive letters available, you might, however, want to put the user tables and indexes in new filegroups and keep the PRIMARY filegroup for the system tables, but make one of the new filegroups the default one.
There are numerous places for reference (I have none to give you off the top of my head, of course), but Frank is a great source for that.
-ldb
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply