Connecting to an Existing Enterprise Database

If your organization already has created an enterprise database on Oracle or Microsoft SQL Server and you have an active user account for the database, you can connect to the database as explained in this topic. When you are connected to an enterprise database, a connection speed indicator will be displayed in the MDI status bar.

< 30 ms: Good (acceptable performance)

30 - 70 ms: OK (may exhibit some delays in operations, opening/closing windows, etc.)

70 - 110 ms: Slow (will exhibit some delays in operations, opening/closing windows, etc.)

110 - 150 ms: Very slow (will exhibit significant delays in operations, opening/closing windows, etc.)

> 150 ms: Extremely slow (will result in unacceptable performance and usability)

Connecting for the First Time

Choose File > New > Create a new enterprise repository connection file.

This command creates a Synthesis repository connection file (*.rserp) that is stored locally on your computer; the file contains all of the necessary information for connecting to the enterprise repository. Once this file is created, it can be used to connect to the database and to import from or export to the database.

Specify the name for the connection file, then choose the database type and version (i.e., Microsoft SQL Server 2005 or 2008, or Oracle 10 or 11).

For SQL Server databases, enter the server name and database name. Select the Use impersonation check box if you want the new connection file to impersonate a Windows user account with a SQL Server login that can be shared by multiple users. This connection file can then be distributed to any user who does not have his/her own individual SQL Server login and is not part of an Active Directory group that has a login. See SQL Server Logins or Using Windows Impersonation.
For Oracle databases, enter the port, host and service identifiers and the database schema. Your Windows login credentials are used for access to the database; enter your Windows password.

Select the Always start by connecting with the last repository check box if you want to connect to the last database you used the next time you launch the application. The database will open automatically if the connection information is valid and your user account is active. If you are using an Oracle database and the current Windows login credentials cannot be validated, the software will display a window that allows you to type a different domain, username and password, if appropriate. You may need to use this option, for example, if you are logged in to your personal home computer but you are trying to access a database on your company’s network via VPN.

Once you have connected to the database, you can manage user accounts by choosing File > Manage Repository > Authorized Users.

Reconnecting

To connect to an enterprise repository that you have already connected to, choose File > Recent and in the Recent Repositories list, choose the *.rserp file. You can also choose File > Open Repository and then browse for the *.rserp file.

Tip: It is important to note that the domain is part of your database login information. For this reason, if you anticipate that you will need to connect to an enterprise database from a computer that is not on the same domain, you should make arrangements in advance to set up an alternative login that you can use to access the database from other domains.

Connection Issues

If you are unable to connect with an existing enterprise database, you may be encountering any of the following issues:

No access to the database. If you have not been granted access to the database, you will receive a message stating that your account in the Synthesis repository is not active or not assigned to at least one security group. To correct this problem, you will need assistance from a user with the "Manage users and logins" permission to edit your account settings. For details on activating/deactivating accounts and assigning security groups, see the Manage Repository Security topic.

Cannot connect to the server or login failed. Server-related issues may occur for several reasons, and you may receive various messages pertaining to the situation. Common issues are:
- You do not have a network connection or you may have entered the incorrect database or server name in the connection file. Check if you have a network connection and enter the correct name of the database or server.
- The server may not be configured to allow remote connections, has certain firewall settings or is experiencing other issues. In this case, you will need to contact the IT support group responsible for the server.
- In SQL Server databases, a login issue may occur if your username is not associated with a SQL Server Login. See SQL Server Logins or Using Impersonation.
The database does not recognize your current Windows login. The Synthesis repository uses Windows authentication to verify the user. If your current Windows login (domain/username) is different from what was specified for your user account, then you will receive a message to connect using an alternative login. You will need assistance from a user with the "Manage users and logins" permission to enable the use of an alternative login for your user account.