I'm undertaking a review of the issues that could possibly be found if our company migrated all projects & databases that we have onto one central database.
Some issues that we are having so far is that:
1. We are based some 300+ miles away from our server, so any automated scripts take some time to run so are not feasible to store and execute from Test Director.
2. By mid week TD is rather slow and needs to be taken down for maintenance.
Can anyone assist with possible problems that I may encounter especially from the automation angle?
Re: Test Director - Migrating to 1 database, issue
Using the old version, having one single or multiple databases isn't going to change the conditions you mentioned.
All settings for users, database connections, and sessions are handled through a single server. Quality Center allows for load balancing across servers to take care of situations of server bouncing, slowness, etc.
Everyone connecting to Test Director will be going to the single server, which will then connect out to the project databases. If this is a single or multiple, you are sill going to the same server for your TD connection.
About the only real solution you would have to the situation would be to work for an upgrade to Quality Center with your company. Since TD 8.0 is no longer supported (don't think it has been for a year), the move will be needed anyway.
Insanity: doing the same thing over and over again and expecting different results