We recently upgraded to QC 9.0. during the upgrade we choose the option of putting our project repositories into the DB.
The goal to make backups & recovery simpler. However, we discovered that there are limits to doing this.
We ran into problems with projects that had large repositories, anything over say 600M.
The upgrade would simply fail, i.e. 'failed to upgrade project' was the message.
Upgrading the same project WITHOUT putting the resp. into the DB worked fine.
Some of our projects had huge repositories, (15G). If you consider result sets from load test and analysis.
When dealing with Mercury support they admitted that they had no solution and that they were no DEFINED limits.
But it turned out that they do not recommend putting a repository larger then 500M into the DB.
Has anyone else decided on putting their repository into the DB?
I have been told that QC 9.2 will no longer support this feature . [img]/images/graemlins/confused.gif[/img]
I have a call with Mercury to discuss tomorrow and will update this thread.
CORRECT 9.2 WILL still support projects that the repository in the DB.
However I have been told that it will not be an option in 9.2.
I can tell you what I have tried recently. I have a number of very small projects that are in the DB.
I tried the following :
We use a SQL server DB.
Project_a in the DB (complete with attachments (jpg, bmp, excel, word, ppt, tsi) requirements tree, defects, test plan, runs, the works)
step 1) Backup Project_A, create a new project, Project_a_in_FS, with the repository in
the file system by using the copy option of ALL of Project_a.
step 2) Then I deleted Project_a.(after testing the project of course.)
step 3) Next I recreated project Project_a with the repository in the file system by using the copy option of ALL of Project_a_in_FS.
I recreated Project_a with the same name so the DB created would have the exact same name thus not impacting the backup plan.
Two issues came up:
First, a folder created in step 1 called 'checkouts' was created it was an empty folder. However in step 3 this folder was not created for some projects.
The checkouts folder is used by QC only if you are using any Version Control integrations like with Microsoft VSS or ClearCase. Otherwise, it is unneeded and should be created on-demand.
We do not use version control
Second, 2 html files in the 'attach' folder created in step 1 did not get created in the 'attach' in step 3. All other attachments were created fine.
I looked these up is to in the CROS_REF table of the project, and compare the file name with the CR_REFERENCE column. They are not listed. Which means they are orphaned. How not sure yet.