Options - Database Profiles
Database Profiles gives you the ability to have different Options for different database connections.
This feature is done by defining a set of Profiles:
- on the Database Profiles tab you specify a set of rules which determines which profile is used by which database connection.
- on the Options for Profile tab you define, for each Profile, the options which are specific to that profile.
How this works
In the grid, you specify a number of rules.
- when you sign onto a database, AQT will go through all the rules to see if the connection matches the specified criteria. If so, AQT will use that Profile for the connection
- if a connection matches more than one entry, the first entry found will be the one used for the connection. Because of this, the order of the entries in the list is important.
- you can have more than one rule for a particular Profile (in the above example, there are multiple rules for both DBA and Master). You would do this if there are multiple criteria for the profile.
- if there is no rule for the connection, the connection will have no Profile. The connection will use the standard options.
In the list of entries:
- Datasource is the name of the datasource. Use this if you want to use a profile for a particular database.
- Type is the database type. Select this from the dropdown list. Use this if you want to use a profile for a particular database type.
- Dbs is the Database Name. This is only used for databases where you can sign onto multiple databases within a server. This includes SQL Server, Sybase, Informix, SQL/MX and MySQL.
- User is the userid you have signed onto the database with. Use this if you want to use a profile when you are signed onto a database with a particular userid.
- Priv is the Oracle Privilege (sysdba or sysoper).
Example
In the above screenshot:
- there are five profiles, Prod, DBA, Oracle, DB2 and Master.
- Prod is used when signed onto datasource Oracle_X
- DBA is used when signed onto any Oracle database as sysdba, except for Oracle_X, which is covered by the previous rule. It is also used when signed onto any DB2 database with userid db2admin
- Oracle is used by any Oracle database that doesn't match the above two conditions
- DB2 is used by any DB2/UDB database that doesn't match the above conditions
- Master is used when signed onto a Master database within a SQL Server or Sybase server