- MULTIPLE ACTIVE STATEMENTS
DBIx::Class::Storage::DBI::ODBC::Microsoft_SQL_Server - Support specific to Microsoft SQL Server over ODBC
This class implements support specific to Microsoft SQL Server over ODBC. It is loaded automatically by by DBIx::Class::Storage::DBI::ODBC when it detects a MSSQL back-end.
Most of the functionality is provided from the superclass DBIx::Class::Storage::DBI::MSSQL.
The following options are alternative ways to enable concurrent executing statement support. Each has its own advantages and drawbacks.
on_connect_call => 'use_dynamic_cursors'
in your connect_info as one way to enable multiple concurrent statements.
odbc_cursortype => 2 to your DBI connection attributes. See "odbc_cursortype" in DBD::ODBC for more information.
Alternatively, you can add it yourself and dynamic cursor support will be automatically enabled.
If you're using FreeTDS,
tds_version must be set to at least
This will not work with CODE ref connect_info's.
WARNING: this will break
SELECT @@IDENTITY will be used instead, which on SQL Server 2005 and later will return erroneous results on tables which have an on insert trigger that inserts into another table with an
on_connect_call => 'use_server_cursors'
May allow multiple active select statements. See "odbc_SQL_ROWSET_SIZE" in DBD::ODBC for more information.
Takes an optional parameter for the value to set the attribute to, default is
WARNING: this does not work on all versions of SQL Server, and may lock up your database!
on_connect_call => 'use_MARS'
Use to enable a feature of SQL Server 2005 and later, "Multiple Active Result Sets". See "Does DBD::ODBC support Multiple Active Statements?" in DBD::ODBC::FAQ for more information.
WARNING: This has implications for the way transactions are handled.
You may distribute this code under the same terms as Perl itself.