July 12, 2007 at 6:59 pm
I'm planning to create a website to track users fitness workouts. I will have 2 databases aspnet.db and a workout.db. The aspnet.db will contain all of the users information, while the workout.db will contain 2 tables one for storing equipment information and the other for storing the user's workout details, such as exercise type, duration, weight, sets, reps, comments.
Are there any guidelines I can following in initially configuring the sizes of the databases? I unfortunately don't have any possible projections of how active the site might or might not be. The Web Host I'm considering offers 400MB per database and initially the aspnet.db is configured at 3mb with unrestricted growth by VS2005.
What's the best way to go about setting an initial size for the databases taking into account the above information that will be stored in them?
Thank you.
July 12, 2007 at 7:37 pm
You may want to read this article for db capacity planning:
http://www.sqlservercentral.com/columnists/aBanerjee/analyzingdiskcapacityforsqlserver.asp
However, tempdb needs special attention; you could find useful info here:
http://msdn2.microsoft.com/en-us/library/ms175527.aspx
July 12, 2007 at 8:07 pm
Thank you for the quick response. I did some further searching and came across the following on MSDN that might be just what I'm looking for and helpful to others as well. I may have worded the subject of my post incorrectly as I'm mostly interested in how to determine the initial size I should create my databases and plan for future growth.
http://technet.microsoft.com/en-us/library/ms187445.aspx
Nonetheless thank you again as those links will also be helpful to me.
July 12, 2007 at 11:29 pm
Capacity Plan itself is an art. You have to decide disk and space usage in phases and also you have to decide where to place the data and log file.
Cheers,
Sugeshkumar Rajendran
SQL Server MVP
http://sugeshkr.blogspot.com
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply