We recently switched from Access to SQL Server and now EVERY time we
execute a script, we get a dialog that comes up and says "Linking ODBC
tables" and it does some kind of "linking" for a few seconds before it
goes away. It didn't used to do that with the Access database and I was
wondering if anyone else was receiving this dialog or if we had
something set up incorrectly.
It's not a big deal now that we are running only a few tests while
coding the scripts. But when we start executing 100s or 1000s of
scripts, this delay is going to add up!
After doing a little more research on this, I came across this in QARun's help:
The link file (.qld) is a Microsoft Access database that resides on the local machine and maps QARun’s tables to the ODBC database server. If QARun detects a change in the version of the database schema, the link file will automatically trigger an update to QARun’s tables.
What appears to be happening with our database is that every time we log in or run a test, it thinks that the database schema has been updated and it needs to relink everything in this "qld" database file again. So I decided to create a new SQL Server database and create a new QARun schema in it. After connecting to this new database, everything seems fine now. I am not seeing the linking going on anymore. I exported the scripts, objects and aliases from the old database and imported into the new one.
I guess something is messed up with our old database. It's a QARun database schema that was created a couple months back and is in the same physical database as our Compuware Reconcile schema. Maybe the 2 product schemas are not supposed to live in the same database?