1DBIx::Class::Storage::DUDBsBIeI:rx::OC:DoCBnlCta:rs:isMb:iu:ctSretodosroPafegtre_l:S:QDDLoB_cISu:em:reOvnDetBraC(t:3i:)oMnicrosoft_SQL_Server(3)
2
3
4
6 DBIx::Class::Storage::DBI::ODBC::Microsoft_SQL_Server - Support
7 specific to Microsoft SQL Server over ODBC
8
10 This class implements support specific to Microsoft SQL Server over
11 ODBC. It is loaded automatically by by DBIx::Class::Storage::DBI::ODBC
12 when it detects a MSSQL back-end.
13
14 Most of the functionality is provided from the superclass
15 DBIx::Class::Storage::DBI::MSSQL.
16
18 The following options are alternative ways to enable concurrent
19 executing statement support. Each has its own advantages and drawbacks.
20
21 connect_call_use_dynamic_cursors
22 Use as:
23
24 on_connect_call => 'use_dynamic_cursors'
25
26 in your "connect_info" in DBIx::Class::Storage::DBI as one way to
27 enable multiple concurrent statements.
28
29 Will add "odbc_cursortype => 2" to your DBI connection attributes. See
30 "odbc_cursortype" in DBD::ODBC for more information.
31
32 Alternatively, you can add it yourself and dynamic cursor support will
33 be automatically enabled.
34
35 If you're using FreeTDS, "tds_version" must be set to at least 8.0.
36
37 This will not work with CODE ref connect_info's.
38
39 WARNING: this will break "SCOPE_IDENTITY()", and "SELECT @@IDENTITY"
40 will be used instead, which on SQL Server 2005 and later will return
41 erroneous results on tables which have an on insert trigger that
42 inserts into another table with an "IDENTITY" column.
43
44 connect_call_use_server_cursors
45 Use as:
46
47 on_connect_call => 'use_server_cursors'
48
49 May allow multiple active select statements. See "odbc_SQL_ROWSET_SIZE"
50 in DBD::ODBC for more information.
51
52 Takes an optional parameter for the value to set the attribute to,
53 default is 2.
54
55 WARNING: this does not work on all versions of SQL Server, and may lock
56 up your database!
57
58 connect_call_use_MARS
59 Use as:
60
61 on_connect_call => 'use_MARS'
62
63 Use to enable a feature of SQL Server 2005 and later, "Multiple Active
64 Result Sets". See "Does DBD::ODBC support Multiple Active Statements?"
65 in DBD::ODBC::FAQ for more information.
66
67 WARNING: This has implications for the way transactions are handled.
68
70 See "CONTRIBUTORS" in DBIx::Class.
71
73 You may distribute this code under the same terms as Perl itself.
74
75
76
77perl v5.12.0 DBIx::Class:2:0S1t0o-r0a5g-e1:2:DBI::ODBC::Microsoft_SQL_Server(3)