Setting preferences for SQL database connections

In the workbench, you can use database connections in two ways:

To create a new connection by using the New Connection wizard, see Creating an SQL database connection, or complete the following steps to set up or edit the connections:

  1. Click Window > Preferences.
  2. When a list of preferences is displayed, expand EGL and click SQL Database Connections.
  3. The currently selected connection in the Connection list is the default database for EGL in the workbench. In this window, you can switch between database connections, edit or delete the connections, and test the connections.
  4. To create a new connection, click New. For an explanation of the preference fields, see Fields in the New Connection wizard.
  5. If you are using IBM® DB2®, you might need to set the Secondary Authentication ID field.For more information, see "Secondary Authentication ID" in this topic.
You can clear or apply preference settings:

Secondary Authentication ID

The secondary authentication ID is more commonly known as the secondary authorization ID. The meaning and use of the secondary authorization ID depends on the following conditions:
  • The DB2 platform that you are using.
  • In some cases, the way that the platform is configured.
To understand how a secondary authorization ID can be used for your environment, see your DB2 documentation.
Here are common examples of the secondary authorization ID:
  • For DB2 UDB, if you specify a secondary authorization ID, that ID is used as the default schema name for all SQL statements.
  • For DB2 on zOS, a secondary authorization ID is often mapped to a RACF® group. Access rights to DB2 objects are granted to the RACF group and individual user IDs are added to the RACF group. This technique minimizes work when your authorization requirements change. For example, if a new DB2 table is created, the system administrator can grant access to a RACF group, and all individuals that belong to that group receive read access as long as they are using the secondary authorization ID.

Feedback