Database Sizing and Planning
Looking for some feedback as to the size of typical repositories. I am guessing that the type of asset will affect this greatly (Bitmap checks for example), but for capacity planning I am looking for a general formula like....
300 total scripts (avg 10 versions for each), 100 total Objects, 50 total checks/events
= SQL Server at 50 mb
500 total scripts (avg 20 versions for each), 100 Total objects, 50 total checks/events
= 3 Access Repositories at 20mb each
Any help is greatly appreciated.
Re: Database Sizing and Planning
I am not sure if you could accurately formulate the size.
The problem arises when, as you stated, you start using bitmap checks and bitmap selects. While QARun can create bitmap images for you, when doing bitmap selects, they are often unreliable as the image seems to be of uniform size but too small to be of good use. Creating your own images works much better but will take more space.
For Bitmap checks every difference will be stored in the database which can quickly grow the size of the database. The same goes for text checks.
It would also be difficult to figure in the use of formchecks as the size will be dependent on the number of controls that are being identified.
IF you can find a way to manage the above mentioned items, I think your only other drawback is the datatype used within the repository. For instance the text type in Access can use up to 255 characters but does not allocate space for unused characters. This means attach names will vary in storage space within the repository. I am not sure if many other data types behave this way, but hopefull someone else can add to this.
I personally would not recommend an Access repository above a couple of hundred mb as you will probably start experiencing problems. The only size problems I have had in SQL are when tables get really large and the default time outs in QARun may not be long enough. Increasing them helped resolve the problem, but overall I think regular maintenance was a better solution.