Debian Codegraph @

README.sqlserver

raw
1 It is proving near impossible to workaround all the different bugs in
2 the various SQL Server ODBC drivers and SQL Server Native Client
3 drivers. From here on I am going to try and keep a record or what
4 worked and what bugs I found.
5
6 There are 5 basic ways I know to connect to SQL Server via ODBC:
7
8 1. On Windows via the SQL Server OBDC Driver
9 2. On Windows via the SQL Server Native Client
10 3. On UNIX via an ODBC driver manager (of which there are 3) and
11 a SQL Server ODBC Driver. There are at least 4 of these:
12 o Easysoft SQL Server ODBC Driver
13 o Data Direct SQL Server Driver
14 o Openlink SQL Server Driver
15 o FreeTDS SQL Server Driver
16 4. On Unix via DBD::Proxy
17 5. On Unix via an ODBC-ODBC Bridge
18 At least Easysoft and Openlink have these.
19
20 Each driver manager and driver has it own bugs and other issues and it
21 is exceedingly difficult to keep up with them all. For Windows and the
22 various SQL Server drivers the list of bugs and workarounds is growing
23 to a point making it difficult to keep track.
24
25 Driver: SQL Server
26 Version reported in ODBC Administrator: 2000.85.1132.00
27 Driver version: 03.85.1132
28 Driver name: SQLSRV32.DLL
29 Passes all tests in: 1.18_2
30 Issues/Notes:
31
32 1. does not support MARS_Connection (see 20SqlServer.t)
33
34 2. needs special workaround when inserting more than 400K into a
35 varxxx(max) field (see rt_38977.t). The workaround is to set the
36 strlen_or_indptr in SQLBindParameter to SQL_LEN_DATA_AT_EXEC(0)
37 and the buffer_length to 0. Without the workaround the errors
38 produced in rt_38977.t are:
39
40 The insert/update of a text or image column(s) did not succeed.
41 The text, ntext, or image pointer value conflicts with the column name.
42
43 3. Sometimes describes parameters incorrectly. Although the
44 workaround in dbdimp.c to set the column_size to the
45 buffer_length works around most sometimes you need to set the
46 parameter type yourself (see rt_39841.t).
47
48 Driver: SQL Native Client
49 Version reported in ODBC Administrator: 2005.90.1399.00
50 Driver version: 09.00.1399
51 Driver Name: SQLNCLI.DLL
52 Passes all tests in: 1.18_2
53 Issues/Notes:
54
55 1. does support MARS_Connection
56
57 2. Sometimes describes parameters incorrectly. Although the
58 workaround in dbdimp.c to set the column_size to the
59 buffer_length works around most sometimes you need to set the
60 parameter type yourself (see rt_39841.t).
61
62 3. Fails the rt_38977.t test to insert more than 400K into a
63 varxxx(max) field unless column_size is set to 0 in the
64 SQLBindParamter call.
65
66 Driver: SQL Server
67 Version reported in ODBC Administrator: 6.00.6000.16386
68 Driver version: 06.00.6000
69 Driver Name: SQLSRV32.DLL
70 Passes all tests in: 1.18_2
71 Issues/Notes:
72
73 Probably has many of the same issues as other SQL Server ODBC drivers
74 but not individually tested.
75
76 Driver: SQL Server
77 Version reported in ODBC Administrator: 2000.86.1830.00
78 Driver version: 03.86.1830
79 Driver Name: SQLSRV32.DLL
80 Passes all tests in: 1.18_2
81 Issues/Notes:
82
83 Probably has many of the same issues as other SQL Server ODBC drivers
84 but not individually tested.
85
86 Driver: SQL Server
87 Version reported in ODBC Administrator: 2000.85.1132.00
88 Driver version: ??????
89 Driver Name: SQLSRV32.DLL
90 Passes all tests in: ??
91 Issues/Notes:
92
93 There is more than one "driver version" reported for the version the
94 ODBC Administrator reports (2000.85.1132.00) and at least one of them
95 fails rt_38977.t with "Invalid precision value".