Has anyone had a problem with corruption in the TestDirector database in version 7.x? We have been running TestDirector since version 6 and since going to version 7.x (we are currently on 7.6 SP3), approximately every 4 months we have some problem with the database, which will show itself in a number of different ways:
1 - Random tests are appended onto the end of test sets. In one extreme case earlier this year several of my test sets had 700+ tests added to them.
2 - Test results history is not updated after tests run and test reports are not created.
3 - Test parameter values are lost at random points.
4 - Execution flows are lost.
5 - Tests run from TD will randomly stop with a 'WinRunner is busy' error when WinRunner is not running anything.
These have been reported but no real solution has been offered other than to upgrade the project. I have done this several times already, but this is of course after the fact and the damage has already been done at the cost of much downtime.
Is there any regular maintenance procedure that I should be doing to the TD database? Are there any queries that I can run on the database to periodically check the integrity of the tables?
I've never used SQL but if I might suggest, you could back up your current database and then convert it over to Access. Just to see if the corruption continues for a while. We've never had issues with Access. The only down side is if/when you go back to SQL you will lose what was done during that time.
Maybe someone else has a better idea.
Success is the ability to go from one failure to another with no loss of enthusiasm.
~ Winston Churchill ~
First of all I will recommended to you to upgrade to 7.6 SP4.
What version is your SQL server 7 or 2000 ?
Did you try to use database backup ?
Does the issue reproduced on all of your project (if you have more then 1)
When it reproduced (weekends, during work hours..)?
We use SQL Server 7. We only have 1 project. I was thinking of upgrading TestDirector directly to version 8 instead of SP4 but I am skeptical that either version will do anything for stability. Our history with TestDirector starting with version 7 has been to install it, use it for 4-6 months, watch the database get corrupted, install the latest SP and upgrade the project, use it for 4-6 months, watch the database get corrupted, etc. etc. up to 7.6 SP3. 18 months ago we manually recreated the entire project but the cycle of corruption and upgrade started all over again on the new project.
At this point I am looking for some preventative measures that will identify potential problems in the database before they show up in the middle of a QA cycle.