Overview

ProblemTracker interfaces with either Microsoft Access, Microsoft SQL Server, or Oracle databases using a standard OLE-DB interface. A Database Administration Utility is included with ProblemTracker to provide some basic operations (e.g. initialization) which may be required in order to use a database with ProblemTracker. However, backups and other database administration should be performed using the tools that come with the database.

Workgroup Management System

Regardless of the database type being used for the workgroups in your ProblemTracker installation, the Workgroup Management System is in Access format and must be backed up.

By default, the Workgroup Management System database file is located at:

installDir/ptadmin/Database/ptadmin.mdb

where installDir is the directory where ProblemTracker was installed (by default, C:\Inetpub\wwwroot\ProblemTracker).

Microsoft Access Databases

By default ProblemTracker uses a Microsoft Access database file located at:

installDir/workgroup/Database/Bugtrack.mdb

where installDir is the directory where ProblemTracker was installed (by default, C:\Inetpub\wwwroot\ProblemTracker), and workgroup is the name of the ProblemTracker workgroup that was installed. There is one database per workgroup.

It is recommended that you back up the database file on a regular basis (e.g. daily) and at a time when it is highly unlikely to be in use (e.g. early morning when backups are typically run). As with any other Windows file, if the file is open, it cannot be backed up until it is closed. ProblemTracker only accesses the database (opens the file) briefly to handle each request (it is only opened between the time a user clicks on a link or button and the requested web page is returned, it is not left open).

To back up your Access database, copy the file installDir/versionDir/Database/Bugtrack.mdb (as described above) for each workgroup.

You also need to back up the Attachments folder which is located at installDir/workgroup/Attachments for each workgroup.

Over time this file may become quite large. You can attempt to compact this file by using Microsoft Access 2000. It is strongly recommended that you backup the file before attempting this operation.

MS SQL Server Databases

If you are using ProblemTracker with a SQL Server database, please refer to the SQL Server documentation on recommended administration procedures, such as regular scheduled backups, etc.

There is one SQL Server database for each ProblemTracker workgroup. By default, the database name is the same as the workgroup name. If the database name is different than the workgroup name, the database name can be found by viewing a workgroup in the Workgroup Management System.

ProblemTracker uses a login with the name PROBLEMTRACKER to access these databases for ProblemTracker operations.

You also need to back up the Attachments folder which is located at installDir/workgroup/Attachments for each workgroup where installDir is the directory where ProblemTracker was installed (by default, C:\Inetpub\wwwroot\ProblemTracker), and workgroup is the name of the ProblemTracker workgroup that was installed.

Oracle Databases

If you are using ProblemTracker with an Oracle database, please refer to the Oracle documentation on recommended administration procedures, such as regular scheduled backups, etc.

There is one Oracle database for each ProblemTracker workgroup. By default, the database name is the same as the workgroup name. If the database name is different than the workgroup name, the database name can be found by viewing a workgroup in the Workgroup Management System.

ProblemTracker uses a login with the name PROBLEMTRACKER to access these databases for ProblemTracker operations.

You also need to back up the Attachments folder which is located at installDir/workgroup/Attachments for each workgroup where installDir is the directory where ProblemTracker was installed (by default, C:\Inetpub\wwwroot\ProblemTracker), and workgroup is the name of the ProblemTracker workgroup that was installed.

Direct Database Edits are Not Supported

Although ProblemTracker uses a standard database, it is recommended that you do not directly modify (or even open) the database(s). Doing so may result in serious and perhaps unrecoverable damage to your ProblemTracker data. Directly accessing the database may also lock users out of the system. Support is not provided for ProblemTracker installations in which the database(s) have been modified using anything other than the (unmodified) ProblemTracker web pages that are shipped with the product (unless you were directed to do so by NetResults Technical Support or NetResults Professional Services). If NetResults Technical Support discovers that your data has been directly modified (or your ProblemTracker web pages have been modified), they may require that you reinstall the product and reinitialize the database(s) before providing any further support.

Direct modification of a ProblemTracker database or source pages by users is not supported by NetResults.