ODBC Server Installation and Management Manual

Managing the NonStop ODBC Server
HP NonStop ODBC Server Installation and Management Manual—429395-002
4-10
Using Batches for DBLIB Clients
This is not an issue for DBLIB clients because cursors are not supported in
TRANSACT-SQL; all data is returned as though the “Read-Only Fast Transfer”
option were being used.
Transaction Isolation
The parameters for this option are as follows:
See the NonStop SQL/MP Reference Manual for detailed information on these
settings.
Auto Commit
The parameters for this option are as follows:
Login Time-Out
The parameter for this option is as follows:
Using Batches for DBLIB Clients
For the best performance, you often want to minimize the number of messages
between the client and the server. One good way of achieving this with DBLIB clients is
by the use of batches, where a batch is a set of SQL statements that are all sent in one
request to the server.
One caution is that each statement in a batch uses heap space in the NonStop ODBC
Server, so it is recommended that a single batch not exceed more than a few hundred
SQL_TXN_READ_COMMITTED The NonStop ODBC Server accesses
SQL/MP by using STABLE access. This is
the default.
SQL_TXN_READ_UNCOMMITTED The NonStop ODBC Server uses BROWSE
access.
SQL_TXN_REPEATABLE_READ The NonStop ODBC Server uses
REPEATABLE access.
SQL_TXN_SERIALIZABLE The NonStop ODBC Server uses
REPEATABLE (serializable) access.
0 Disables auto commit; the application must commit a transaction.
1 Enables auto commit; the NonStop ODBC Server commits the transaction after
each SQL statement.
n The number of seconds that the NonStop ODBC driver waits for a connection to
be completed. If n is zero, the driver waits indefinitely.
Note. Settings on the PC override the profile settings on the NonStop system set up for that
user. Configure the PC settings for ODBC datasources carefully to ensure the best
performance.