<     >  Table of Contents


InstantSQL is limited in most cases only by the memory available to do its work. The following limits are built into InstantSQL:

Maximum simultaneous connections: 256

Maximum number of simultaneous queries: 2048

Number of stored error messages: 64

If the COBOL program using InstantSQL exceeds the limit on connections or queries, an appropriate error message is generated and the request fails. The program may continue with the resources it has already acquired. The program may free any of those resources and retry the request that failed. For example, if the simultaneous connections limit is exceeded, the application may use the SQL DISCONNECT DATASOURCE statement to make a connection available.

If the number of stored error messages is exceeded, any additional error messages are lost, but a message is generated indicating that this has occurred. The limit on stored error messages is for a single InstantSQL statement and represents the maximum number of messages that an SQL DESCRIBE ERROR statement will return before returning the lost errors message followed by setting sql-EndOfData to true.

LONGVARCHAR and LONGVARBINARY data items are limited to a configurable maximum length, each with a default value of 4096. The SQL BIND COLUMN statement may also be used that specifies a larger COBOL data item to reset the maximum size of a particular result column before a row of data is fetched. If a row containing a LONGVARCHAR or LONGVARBINARY data item is fetched and the value is longer than the existing limit, the value will be truncated on the right. Similarly, the SQL BIND PARAMETER statement may be used that specifies a larger COBOL data item to reset the maximum size of a particular parameter with one of these SQL data types.

ODBC drivers may impose additional restrictions not noted here. Some of these restrictions can be obtained by using an extended connection description group in the SQL DESCRIBE CONNECTION statement.

Copyright 2000 Liant Software Corp. All rights reserved.