List of Registered Databases

When opening a database, Database Tour registers it in the list of used databases, which can be accessed from Database | Registered Databases... menu. The application uses this list each time it opens a database.

Beside database names, the list contains also connection parameters for the databases. The database connection parameters can be viewed or edited using the corresponding buttons. There is also a possibility to edit common properties of multiple selected databases.

Any database from this list can be easily reopened by using the corresponding button. Open databases from this list are marked with a tick.

You can copy the database list, delete records, clear stored database passwords and add new records by opening new databases using the corresponding dialog.

Workspace File

The list of the registered databases (along with their connection parameters and SQL windows) is saved to a workspace file. By default, this is a dbtour.workspace file from the {Local AppData}\Vitaliy Levchenko\{Software Name}\{Software Version}\Settings folder.

The workspace file is saved in the following cases: before executing a SQL query, before database closing, and before the application's closing. Please consider this information when working with multiple instances of the application. When the application is restarting, the list is loaded from the workspace file into the operating memory and used to open the previously opened databases.

Exporting and Importing the Workspace

Using Import and Export buttons from the Registered Databases window, you can import or export the workspace from/to another file, respectively. This functionality can be used for the following purposes:

Important Notes

  1. When importing the workspace, all existing entries from the current workspace are deleted. So, make sure to backup your workspace (using Export button) before the importing another workspace.
  2. After exchanging workspace between applications on different computers, the database passwords stored in the imported workspace might become invalid and you will have to reenter them.
  3. After importing the workspace from 32-bit version to 64-bit version and vice versa, some registered database entries might become unusable due to architecture mismatch.
  4. It is recommended that the application importing the workspace was the same version as application from where the workspace was exported.