Search: Advanced search
Please enter a keyword or ID
Modifying TestTrack Databases
Note: This information only applies to TestTrack 7.0 and later.
If you use TestTrack 7.0 or later, you can store data in a Relational Database Management System (RDBMS) database, such as Oracle or Microsoft SQL Server, instead of the native TestTrack database format.
You can modify the internal TestTrack database format and data from the RDBMS database, but this is not recommended. You TestTrack maintenance contract does not include support for recovering from these types of database changes.
For both TestTrack native databases and RDBMS databases, you can configure field names, custom fields, workflow processes, notification rules, and more. We recommend making these changes using the TestTrack user interface rather than at the database level. Making changes directly in the database requires a full understanding of the TestTrack database format and the rules enforced at the software level.
Database Table Changes
Do not reconfigure the TestTrack database format. When you rename a field in the TestTrack user interface, the database column names do not reflect this change. Do not change database tables/column names, modify column size/attributes, or make any other structural database changes as it will result in errors running TestTrack .
TestTrack caches data to improve the performance of complex reports and filters. Do not perform live updates of TestTrack at the database level unless the TestTrack Server has been shut down. Adding, editing, or deleting TestTrack data while the TestTrack Server is running results in errors and potential data loss. Your changes may be overwritten next time the record is modified because database changes are not immediately read into the TestTrack memory cache.
You can read and view TestTrack information from the database via ODBC or database vendor-specific methods.
The TestTrack native database format prevents users from opening the database in read/write mode while the TestTrack Server is running; however, TestTrack does not implement similar locks when running against an RDBMS database. To perform live TestTrack data updates, use SOAP, bulk field changes, or other methods available in the TestTrack clients.