We try to estimate what would be the "typical" database size for a large project in QC that has QTP + BPT scripts.
We are using MS-SQL and the repository is located in the filesystem.
They will grow between 300 and 500 megs. If you are keeping the run history you can expect them to be around a gig unless you clear the history once a year. Use SQL as it's much faster than the UI.
I have QC projects that each contain approximately 400 BPT Components and 600 BPT tests in addition to a stack of manual tests.
With the Repository in the Database (oops) these projects are consuming 18G and 11G respectively.
I'm migrating to a new server (that's less likely to explode) and will be shifting the repository to the FS as part of that process.
I'll post back with the impact on tablespace when it's done.
... just another Tester ...
Thanks guys for your replies. That will be interesting to see Asher's migration result!
The tablespace in my projects was being taken up with 'CLOB'/'BLOB' data in the REPOSITORY folder. (attachments to requirements, tests, runs and defects....)
My DBA was able to tell me how much *LOB data there was in my schemas.. but even so the result was still somewhat astonishing to see:
My 18G project is now only consuming ~2G and runs much faster!. It took around 20 hours to clone the project to NOT store repository in DB. (QC9.0)
My 11G project is refusing to play ball and migrate across.. I'm wishing QC9.0 had the magic Repository <> File system switching button that QC9.2 has.
There's a patch for 9.0 to allow you to move the repository from the database to the file system. I just upgraded to version 10 from 9 and had to move the repositories out. If memory serves patch 26 for 9.0 is what you'll need.
@kisvacak, unfortunately it doesn't look like that patch was released for Solaris.. :\