Advanced Tab
The following table and the sections below lists and explains the connection properties that are in the Advanced Tab of the New Data Source Window.
|
A template for generating a URL to connect to the physical data source. |
|
|
The URL string generated from the connection URL pattern with the connection information you provide. |
|
|
Lets you specify property-value pairs to pass to the JDBC data source |
|
|
Maximum number of connections (both active and idle) allowed for the data source. When the maximum is reached, new requests must wait until a connection is available. |
|
|
Minimum number of connections in the pool even when the pool is inactive. |
|
|
Number of seconds that a connection can remain idle without being dropped from the pool when there are more than the minimum number of connections. |
|
|
The number of minutes that a connection that was returned to the pool persists if there are more open connections than the minimum pool size. |
|
|
A data-source-specific query that the TDV query engine sends to see if the data source connection is valid. This query is executed every time a connection is checked out from the pool. Enter a query that returns quickly. |
|
|
The number of seconds an execution query on the data source can run before being canceled. |
|
|
Lets a SELECT statement be executed using a new connection from the connection pool, and committed immediately after completion. INSERT, UPDATE, and DELETE statements are executed using the same connection as part of the transaction. |
|
|
A procedure that returns a valid SQL statement that can be used to initialize the connection. |
|
|
Check only if this data source supports very large predicates and very large cardinalities for star schema semijoins. |
|
|
See the documentation for semijoins and the TDV Administration Guide for more information. |
|
|
Sets the minimum target-to-source ratio of cardinality for semijoins. Refer to the TDV Administration Guide for more information. |
|
|
See the documentation for semijoins and the TDV Administration Guide for more information. |
|
| Enable Native Data Loading |
Lets the data source use its proprietary functionality to optimize performance. |
|
TDV does not use the SORT MERGE join algorithm if any data source involved in the join is marked Collation Sensitive. |
|
|
Works with the Massively Parallel Processing engine configuration parameters to control the amount of parallelization for the queries for a particular data source. |
|
| Is dataship source | This must be checked if the physical data source might be used as a source of shipped tables to another data ship enabled data source. Check Is dataship source for all data sources so that the TDV Server can analyze the query and determine the side that would be best to ship to based on expected or estimated query node cardinality. |
| Is dataship target | This must be checked if the physical data source might be used to receive shipped tables from another data ship enabled data source. Check Is dataship target for all data sources so that the TDV Server can analyze the query and determine the side that would be best to ship to based on expected or estimated query node cardinality. |
| Lower bound/Upper bound for dataship | TDV uses Explain Plan to arrive at a numeric estimate of the cost of shipping data from a node to the Data Virtualizer. When the cost of shipping a federated query node falls between the limits of the Lowerbound and Upperbound, it is considered eligible for shipment so that it can be processed locally. |
| Schema Path for Temp Tables | A relative path to set the location of the temp tables on the data source. It is the name of a schema in the data source. |
| Temp Table Prefix | A character string addition to temporary table names so that they are recognized if they are needed. |
|
Takes advantage of PostgreSQL COPY command. |
|
|
Check to enable database links to improve performance if you plan to use this data source for data caching or data ship optimization. If you check this box, add one or more database links by specifying the database link name and path of the data source for each link |
|
| Database Links | If you check the box Enable PostgreSQL dblink, add one or more database links by specifying the database link name and path of the data source for each link |
Connection URL Pattern
A template for generating a URL to connect to the physical data source.
Data Type
string
Default Value
jdbc:<DATA SOURCE>//<HOST>:<PORT>/<DATABASE_NAME>
Remarks
TDV does not validate modifications at the time of configuration. The data source adapter might not validate changes.
Connection URL String
The URL string generated from the connection URL pattern with the connection information you provide.
Data Type
string
Default Value
“”
Remarks
This string is used by the JDBC adapter to connect to the physical data source. This field cannot be edited. For details, see the section “Connecting through JDBC Adapters” in the TDV Administration Guide.
JDBC Connection Properties
Lets you specify property-value pairs to pass to the JDBC data source.
Data Type
string
Default Value
“”
Remarks
Click to add custom connection properties for any JDBC data source. Commonly used properties are populated with default values. Use the Add Argument button to specify other properties and values.
TDV does not validate property names. Some data source adapters ignore invalid property names or values; others return an error.
The driver properties specify connection timeout settings required by specific drivers. To avoid leaving connections open indefinitely, specify properties explicitly for your data source.
Connection Pool Maximum Size
Maximum number of connections (both active and idle) allowed for the data source. When the maximum is reached, new requests must wait until a connection is available.
Data Type
Numeric
Default Value
100
Remarks
If the maximum number of connections is in use when a request comes in (even with pass-through authentication), the new request is blocked and queued until a connection is available or the Connection Pool Idle Timeout is reached.
If no connection was made available within the specified timeout, a check is made for an available connection by the same user. If none is available, the least recently used connection for another user is dropped and a new connection is opened.
Studio reuses pooled connections if they continue to be valid after changes (such as connection name), but JDBC requests are forced to use new connections if any part of the data source connection configuration has changed.
Connection Pool Minimum Size
Minimum number of connections in the pool even when the pool is inactive.
Data Type
Numeric
Default Value
0
Remarks
When a connection has been idle, a validation query is used to verify whether an open connection is still valid just prior to submission of a request. If the connection is invalid, the connection is discarded and another is used.
Connection Pool Idle Timeout
Number of seconds that a connection can remain idle without being dropped from the pool when there are more than the minimum number of connections.
Data Type
Numeric
Default Value
30
Maximum Connection Lifetime
The number of minutes that a connection that was returned to the pool persists if there are more open connections than the minimum pool size.
Data Type
Numeric
Default Value
30
Remarks
The duration is calculated from connection creation. Default value is 60 minutes. Set a smaller value if the pool is likely to run out of connections. Be sure to add a validation query. Set a larger value if you want the connections to be held for a longer period. Set a value of 0 to keep connections alive indefinitely.
Connection Validation Query
A data-source-specific query that the TDV query engine sends to see if the data source connection is valid. This query is executed every time a connection is checked out from the pool. Enter a query that returns quickly.
Data Type
string
Default Value
""
Remarks
If this query returns a non-error result, the data source connection is considered valid. If this query fails, the connection is discarded and a new connection is checked out from the available pool.
No one SELECT statement works with all data sources. To verify that TDV is running and that it can connect to the data source, devise a query against a published table from that data source.
Enable Native Data Loading
Lets the data source use its proprietary functionality to optimize performance.
Data Type
Bool
Default Value
True
Remarks
See the User Guide, Chapter About Data Source Native Load Performance Options” for more details,.
Collation Sensitive
TDV does not use the SORT MERGE join algorithm if any data source involved in the join is marked Collation Sensitive.
Data Type
Bool
Default Value
False
Remarks
None
Concurrent Request Limit
Works with the Massively Parallel Processing engine configuration parameters to control the amount of parallelization for the queries for a particular data source.
Data Type
Numeric
Default Value
0
Remarks
None
Is dataship source
This must be checked if the physical data source might be used as a source of shipped tables to another data ship enabled data source. Check Is dataship source for all data sources so that the TDV Server can analyze the query and determine the side that would be best to ship to based on expected or estimated query node cardinality.
Data Type
Bool
Default Value
False
Remarks
None
Is dataship target
This must be checked if the physical data source might be used to receive shipped tables from another data ship enabled data source. Check Is dataship target for all data sources so that the TDV Server can analyze the query and determine the side that would be best to ship to based on expected or estimated query node cardinality.
Data Type
Bool
Default Value
False
Remarks
This option is available only if Is dataship source field is enabled.
Lower bound/Upper bound for dataship
TDV uses Explain Plan to arrive at a numeric estimate of the cost of shipping data from a node to the Data Virtualizer. When the cost of shipping a federated query node falls between the limits of the Lowerbound and Upperbound, it is considered eligible for shipment so that it can be processed locally.
Data Type
Numeric
Default Value
Lower bound - 50000
Upper bound - 5000000
Remarks
To make changes in this field Is dataship source must be enabled.
Schema Path for Temp Tables
A relative path to set the location of the temp tables on the data source. It is the name of a schema in the data source.
Data Type
String
Default Value
""
Remarks
None
Temp Table Prefix
A character string addition to temporary table names so that they are recognized if they are needed.
Data Type
String
Default Value
T
Remarks
None
Enable Bulk Export/Load
Takes advantage of PostgreSQL COPY command.
Data Type
Bool
Default Value
True
Remarks
To make changes to this field enable Is dataship source
Enable PostgreSql dblink
Check to enable database links to improve performance if you plan to use this data source for data caching or data ship optimization. If you check this box, add one or more database links by specifying the database link name and path of the data source for each link
Data Type
Bool
Default Value
False
Remarks
None
Database Links
If you check the box Enable PostgreSQL dblink, add one or more database links by specifying the database link name and path of the data source for each link
Data Type
Bool
Default Value
False
Remarks
None
Execution Timeout
The number of seconds an execution query on the data source can run before being canceled.
Data Type
Numeric
Default Value
0
Remarks
None
Execute SELECTs Independently
Lets a SELECT statement be executed using a new connection from the connection pool, and committed immediately after completion. INSERT and UPDATE statements are executed using the same connection as part of the transaction.
Data Type
Bool
Default Value
True
Remarks
None
Connection Checkout Procedure
A procedure that returns a valid SQL statement that can be used to initialize the connection.
Data Type
string
Default Value
""
Remarks
The signature of the initialization procedure should be:
(IN ds_name VARCHAR, OUT sqlText VARCHAR)
Give the full path to the procedure in the Connection Check-out Procedure box.
Max Source Side Cardinality for Semi Join
See the documentation for semijoins and the TDV Administration Guide for more information.
Data Type
Numeric
Default Value
""
Remarks
None
Max Source Side of Semi Join To Use OR Syntax
See the documentation for semijoins and the TDV Administration Guide for more information.
Data Type
Numeric
Default Value
2147483647
Remarks
None
Min Target to Source Ratio for Semi Join
Sets a minimum ratio to trigger use of semi join optimization.
Data Type
Numeric
Default Value
""
Remarks
None
Supports Star Schema
Check only if this data source supports very large predicates and very large cardinalities for star schema semijoins.
Data Type
Bool
Default Value
False
Remarks
Refer to the section Star Schema Semijoin in the User Guide, for more information.