Bookshelf: Creating a Connection Pool for All Data Sources

You must create a database object before you create a connection pool. After creating a database object, you create or edit a connection pool in the Physical layer of the Administration Tool.

Table 7. Connection Pool General Properties
Field or Button	Description
Name	The name for the connection pool. If you do not type a name, the Administration Tool generates a name.
Permissions	Click to access the Permissions dialog box. You can use the Permissions dialog box to assign permissions for individual users or groups to access the connection pool. You can also set up a privileged group of users to have its own connection pool.
Call interface	The application program interface (API) with which to access the data source. Some databases may be accessed using native APIs, some use ODBC, and some work both ways. If the call interface is XML, the XML tab is available but options that do not apply to XML data sources are not available. If the call interface is XMLA, the XMLA tab is available but options that do not apply to multidimensional data sources are not available.
Maximum connections	The maximum number of connections allowed for this connection pool.
Require fully qualified table names	Select this check box, if the database requires it. When this option is selected, all requests sent from the connection pool use fully qualified names to query the underlying database. The fully qualified names are based on the physical object names in the repository. If you are querying the same tables from which the Physical layer metadata was imported, you can safely check the option. If you have migrated your repository from one physical database to another physical database that has different database and schema names, the fully qualified names would be invalid in the newly migrated database. In this case, if you do not select this option, the queries will succeed against the new database objects. For some data sources, fully qualified names might be safer because they guarantee that the queries are directed to the desired tables in the desired database. For example, if the RDBMS supports a master database concept, a query against a table named foo first looks for that table in the master database, and then looks for it in the specified database. If the table named foo exists in the master database, that table is queried, not the table named foo in the specified database.
Data source name	The drop-down list shows the User and System DSNs configured on your system. A data source name configured to access the database to which you want to connect. The data source name needs to contain valid logon information for a data source. If the information is invalid, the database logon specified in the DSN will fail.
Shared logon	Select the option Shared logon if you want all users whose queries use the connection pool to access the underlying database using the same user name and password. If this option is selected, then all connections to the database that use the connection pool will use the user name and password specified in the connection pool, even if the Siebel Analytics user has specified a database user name and password in the DSN (or in the Siebel user configuration). If this option is not selected, connections through the connection pool use the database user ID and password specified in the DSN or in the Siebel user profile.
Enable connection pooling	Allows a single database connection to remain open for the specified time for use by future query requests. Connection pooling saves the overhead of opening and closing a new connection for every query. If you do not select this option, each query sent to the database opens a new connection.
Timeout (Minutes)	Specifies the amount of time, in minutes, that a connection to the data source will remain open after a request completes. During this time, new requests use this connection rather than open a new one (up to the number specified for the maximum connections). The time is reset after each completed connection request. If you set the timeout to 0, connection pooling is disabled; that is, each connection to the data source terminates immediately when the request completes. Any new connections either use another connection pool or open a new connection.
Execute queries asynchronously	Indicates whether the data source supports asynchronous queries. Asynchronous queries allow query cancellations to be sent to the database through the same connection while the query is executing. If this option is not selected, query cancellations might not propagate down to the underlying database.
Execute on Connect	Allows the Siebel Analytics Server administrator to specify a command to be executed each time a connection is made to the database. The command may be any command accepted by the database. For example, it could be used to turn on quoted identifiers. In a mainframe environment, it could be used to set the secondary authorization ID when connecting to DB2 to force a security exit to a mainframe security package such as RACF. This allows mainframe environments to maintain security in one central location.
Parameters supported	If the database features table supports parameters and the connection pool check box property for parameter support is unchecked, then special code executes that allows the Analytics Server to push filters (or calculations) with parameters to the database. The Analytics Server does this by simulating parameter support within the gateway/adapter layer by sending extra SQLPrepare calls to the database.
Isolation level	For ODBC and DB2 gateways, sets the transaction isolation level on each connection handle to the back-end database.