Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
opi
Starting Member
29 Posts |
 Posted - 2009-04-27 : 10:19:27
|
| Hello,I have a question concerning the steps I need to take to go to production. I created an asp.net application that is using SQL Server 2005 as backend database.It uses about 40tables. I have always been working in a test envirement basically.I'll try to explain what I have done so farIndexing etc:I have placed clustered indexes on the tables that are being used heavily by search screens. For the less important tables I have a clustered index on the primary key.Now I'm not really a DBA and currently there is no real budget for this..but I'm a bit concerned concerning growth.I have read somewhere that I need to do sizing etc to be ready for growth in the future. I'm not afraid to learn something new. Could anyone provide me with a list of points that I need to take care of before moving my application to a production environement?Thanks in advance,OPI |
|
|
TG
Master Smack Fu Yak Hacker
6065 Posts |
Posted - 2009-04-27 : 11:27:33
|
| pretty broad questions but here are a couple of factors/decision points:- is your new application replacing an existing production application or is it really "new"?- if replacememnt - do you have a rollback plan? Are users aware of functional changes? Can you rollout without any interuption of service?- Have you tested your application under expected production load and concurrency levels?- Have you estimated the data growth for "normal" usage over time?Be One with the OptimizerTG |
 |
|
|
opi
Starting Member
29 Posts |
Posted - 2009-04-28 : 03:38:25
|
quote:
Originally posted by TG
pretty broad questions but here are a couple of factors/decision points:- is your new application replacing an existing production application or is it really "new"?- if replacememnt - do you have a rollback plan? Are users aware of functional changes? Can you rollout without any interuption of service?- Have you tested your application under expected production load and concurrency levels?- Have you estimated the data growth for "normal" usage over time?Be One with the OptimizerTG
Yes its a completely new applicationHow can I estimate the growth of the data in my database?How can I determine what the data volume will be in say 3 years? |
|
|
|
TG
Master Smack Fu Yak Hacker
6065 Posts |
Posted - 2009-04-28 : 08:13:18
|
| Depends on the nature of your business. For instance if you are collecting weather data every hour from 20,000 stations then you can pretty accurately predict the growth based on the storage requirements of one "station report" multiplied by the number of rows you will collect. However, if your data growth is proportional to the number of clients you will attract over time then you have to try and estimate "best case scenario" requirements. So you'll have to analyze the nature of your business in regards to data collection so you can estimate an average per/unit size requirments then estimate the number of "units" you may expect over time. Books Online has a good topic describing how to estimate the space requirements for a table given a specific structure, indexes, etc. Look up "Estimating the Size of a Table"Be One with the OptimizerTG |
|
|
|
|
|
|
Moving to production