| Navigation: SQL Driver Strings(General) >====== MULTIPLEACTIVERESULTSETS ====== |    |
DRIVER('SQLDriver', '/MULTIPLEACTIVERESULTSETS = TRUE | FALSE ' )
[ Mars“ = ] SEND(file, '/ MULTIPLEACTIVERESULTSETS [ = TRUE | FALSE ]' )
(NOTE: Only valid for ODBC and MSSQL Accelerators)
The ODBC and MSSQL drivers default to FALSE (using MARS (Multiple Active Result Sets)) whenever MS-SQL Server 2005 is detected. MARS is defined as the ability to have more than one pending request under a given SQL Server connection. For most cases this will directly translate to the ability to have more than one default result set outstanding while other operations can execute within the same session.
If you need to enable the MARS support, set this driver string to TRUE. It can be turned on by accessing the driver string dialog, or by using a SEND statement prior to the table being opened. This is a connection-wide switch, which means that all files with the same OWNER will have the same MARS support based on the first file that is opened on that connection.
If all tables are closed and a PROP:Disconnect is issued successfully, you will need to SEND the /MULTIPLEACTIVERESULTSETS = TRUE again before the first table is opened.
When MARS is set to ON, the BusyHandling switch is still active, but should not be needed. The driver's default behavior is to retry whenever the busy message is encountered, but a busy message should never happen with MULTIPLEACTIVERESULTSETS on (or active).
Setting this switch ON to backends that do not support MARS have no adverse effect. The driver will detect if the backend does not support MARS and ignore the switch in this case.
See Also: BUSYHANDLING