Connect to an Actian Database Instance
You connect to a local or remote database instance using the Connect to Instance dialog.
To connect to a local instance
1. Click Connection, Connect.
The Connect to Instance dialog opens.
2. Select a local instance from the Instance drop-down by clicking the browse button (...).
You may also enter "local/XX," "local:XX," or just "XX" in the Instance field, where XX is the installation ID of the Actian database installation you want to connect to.
3. Select a user to authenticate login.
• If you select the currently logged in user, you do not need to specify a user name and password.
• If you choose another authenticated user, enter their user name and password.
4. (Optional) Configure advanced authentication options by clicking the Options button.
5. Click Connect.
The connection is attempted. If valid credentials are not supplied or the instance connection fails, a standard error dialog is displayed detailing the reason for the error.
To connect to a remote instance
Note: When connecting to a remote instance, Director checks to see that it is compatible with the version of the management server running on that instance. If they do not match, connection cannot be made. Newer versions of Director should be able to connect to any older versions of the management server, with some minor exceptions.
1. Click Connection, Connect.
The Connect to Instance dialog opens.
2. Specify the server name and instance code in the following format:
ServerName/InstanceCode or ServerName:InstanceCode
3. Select a user to authenticate login.
• If you select the currently logged in user, you do not need to specify a user name and password.
• If you choose another authenticated user, enter their user name and password.
4. (Optional) Configure advanced authentication options by clicking the Options button. Fields are explained in
Connect to Instance Dialog.
5. Click Connect.
The connection is made. If valid credentials are not supplied or the instance connection fails, a standard error dialog is displayed detailing the reason for the error.
Last modified date: 04/24/2023