Re: Using mxodbc with SQL Server 2012
Sheila Allen <[email protected]> Thu, 3 Sep 2015 05:06:15 -0500
| Newsgroups | gmane.comp.python.egenix.user |
|---|---|
| Message-ID | <CAKJxN3UDK5m699BMLphdSRzFfuvEv4NLy6CwM8r3-Z+HG1jsJg@mail.gmail.com> |
--===============37406814985996073== Content-Type: multipart/alternative; boundary=e89a8f3ba55f9d7703051ed4f175 --e89a8f3ba55f9d7703051ed4f175 Content-Type: text/plain; charset=UTF-8 On Thu, Sep 3, 2015 at 4:16 AM, M.-A. Lemburg <[email protected]> wrote: > > On 03.09.2015 08:44, Sheila Allen wrote: > >> I'm looking into the MS SQL Server Native client again as well, we tried > >> it when they first announced it and it would segfault with any significant > >> load > > > > We're currently testing the MS ODBC Driver for Linux, and ran into a > > similar segfault under load. This was resolved by upgrading unixODBC 2.3.0 > > to 2.3.2, even though the MS ODBC Driver officially only supports 2.3.0. > > > > Some discussion of the issue here: > > https://social.msdn.microsoft.com/Forums/sqlserver/en-US/23fafa84-d333-45ac-8bd0-4b76151e8bcc/sql-server-driver-for-linux-causes-segmentation-fault > > We are using the MS driver with unixODBC 2.3.2 just fine. The only > segfault we've seen so far is related to using Unicode strings with > DriverConnect(): > > http://www.egenix.com/products/python/mxODBC/doc/#_Toc427692959 > > If you can provide instructions on how to reproduce the problem > you are seeing under load, we can try to investigate this some > more. The segfault issue goes away with 2.3.2, as mentioned above. This discussion describes how to reproduce the issue using the unixODBC 2.3.0: https://social.msdn.microsoft.com/Forums/sqlserver/en-US/23fafa84-d333-45ac-8bd0-4b76151e8bcc/sql-server-driver-for-linux-causes-segmentation-fault The point here...the concern...is really that the official Microsoft certified unixODBC version is 2.3.0, a very old version with a known bug. The documentation mentions that version repeatedly, and specifically states that 2.3.1 is not supported. So the docs are really outdated, and I guess the installation script is too because it requires additional manual workarounds to use newer versions of unixODBC. Here are the Microsoft installation docs: https://www.microsoft.com/en-us/download/details.aspx?id=36437 This has been raised in several threads, and has been a known issue since 2012, but Microsoft has failed to certify or document use of newer versions of unixODBC since then. Unless I'm just looking in the wrong place. Here's another article that turned up in a search for the driver...once again it describes use of unixODBC 2.3.0. https://msdn.microsoft.com/en-us/library/hh568449(v=sql.110).aspx So the question is whether it's a good idea to advocate for the use of this driver, which seems to be somewhat abandoned after several years. Has anyone seen any statements from Microsoft that they're continuing to support it? I've seen this discussed among users also on the Microsoft blog, with no response: http://blogs.msdn.com/b/sqlnativeclient/archive/2013/01/23/introducing-the-new-microsoft-odbc-drivers-for-sql-server.aspx#10620294 Am I just looking in the wrong places? -- This e-mail message (including any attachments) may contain information that is confidential, protected by the attorney-client or other applicable privileges, or otherwise comprising non-public information. This message is intended to be conveyed only to the designated recipient(s). If you have any reason to believe you are not an intended recipient of this message, please notify the sender by replying to this message and then deleting it from your system. Any use, dissemination, distribution, or reproduction of this message by unintended recipients is not authorized and may be unlawful. --e89a8f3ba55f9d7703051ed4f175 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable <div dir=3D"ltr"><div><br>On Thu, Sep 3, 2015 at 4:16 AM, M.-A. Lemburg <= ;<a href=3D"mailto:[email protected]">[email protected]</a>> wrote:<br>><br= >> On 03.09.2015 08:44, Sheila Allen wrote:<br>> >> I'm loo= king into the MS SQL Server Native client again as well, we tried<br>> &= gt;> it when they first announced it and it would segfault with any sign= ificant<br>> >> load<br>> ><br>> > We're currently= testing the MS ODBC Driver for Linux, and ran into a<br>> > similar = segfault under load. This was resolved by upgrading unixODBC 2.3.0<br>> = > to 2.3.2, even though the MS ODBC Driver officially only supports 2.3.= 0.<br>> ><br>> > Some discussion of the issue here:<br>> >= ; <a href=3D"https://social.msdn.microsoft.com/Forums/sqlserver/en-US/23faf= a84-d333-45ac-8bd0-4b76151e8bcc/sql-server-driver-for-linux-causes-segmenta= tion-fault">https://social.msdn.microsoft.com/Forums/sqlserver/en-US/23fafa= 84-d333-45ac-8bd0-4b76151e8bcc/sql-server-driver-for-linux-causes-segmentat= ion-fault</a><br>><br>> We are using the MS driver with unixODBC 2.3.= 2 just fine. The only<br>> segfault we've seen so far is related to = using Unicode strings with<br>> DriverConnect():<br>><br>> <a href= =3D"http://www.egenix.com/products/python/mxODBC/doc/#_Toc427692959">http:/= /www.egenix.com/products/python/mxODBC/doc/#_Toc427692959</a><br>><br>&g= t; If you can provide instructions on how to reproduce the problem<br>> = you are seeing under load, we can try to investigate this some<br>> more= .</div><div><br></div><div>The segfault issue goes away with 2.3.2, as ment= ioned above. This discussion describes how to reproduce the issue using the= unixODBC 2.3.0:</div><div><br></div><div><a href=3D"https://social.msdn.mi= crosoft.com/Forums/sqlserver/en-US/23fafa84-d333-45ac-8bd0-4b76151e8bcc/sql= -server-driver-for-linux-causes-segmentation-fault">https://social.msdn.mic= rosoft.com/Forums/sqlserver/en-US/23fafa84-d333-45ac-8bd0-4b76151e8bcc/sql-= server-driver-for-linux-causes-segmentation-fault</a><br></div><div><br></d= iv><div>The point here...the concern...is really that the official Microsof= t certified unixODBC version is 2.3.0, a very old version with a known bug.= The documentation mentions that version repeatedly, and specifically state= s that 2.3.1 is not supported. So the docs are really outdated, and I guess= the installation script is too because it requires additional manual worka= rounds to use newer versions of unixODBC. Here are the Microsoft installati= on docs:</div><div><br></div><div><a href=3D"https://www.microsoft.com/en-u= s/download/details.aspx?id=3D36437">https://www.microsoft.com/en-us/downloa= d/details.aspx?id=3D36437</a><br></div><div><br></div><div>This has been ra= ised in several threads, and has been a known issue since 2012, but Microso= ft has failed to certify or document use of newer versions of unixODBC sinc= e then. Unless I'm just looking in the wrong place.</div><div><br></div= ><div>Here's another article that turned up in a search for the driver.= ..once again it describes use of unixODBC 2.3.0.</div><div><br></div><div><= a href=3D"https://msdn.microsoft.com/en-us/library/hh568449(v=3Dsql.110).as= px">https://msdn.microsoft.com/en-us/library/hh568449(v=3Dsql.110).aspx</a>= <br></div><div><br></div><div>So the question is whether it's a good id= ea to advocate for the use of this driver, which seems to be somewhat aband= oned after several years.=C2=A0 Has anyone seen any statements from Microso= ft that they're continuing to support it? I've seen this discussed = among users also on the Microsoft blog, with no response:</div><div><br></d= iv><div><a href=3D"http://blogs.msdn.com/b/sqlnativeclient/archive/2013/01/= 23/introducing-the-new-microsoft-odbc-drivers-for-sql-server.aspx#10620294"= >http://blogs.msdn.com/b/sqlnativeclient/archive/2013/01/23/introducing-the= -new-microsoft-odbc-drivers-for-sql-server.aspx#10620294</a><br></div><div>= <br></div><div>Am I just looking in the wrong places?</div><div><br></div><= /div> <br> <span style=3D"color:rgb(34,34,34);font-family:arial,sans-serif;font-size:1= 2.8000001907349px;background-color:rgb(255,255,255)">This e-mail message (i= ncluding any attachments) may contain information that is confidential, pro= tected by the attorney-client or other applicable privileges, or otherwise = comprising non-public information. This message is intended to be conveyed = only to the designated recipient(s). If you have any reason to believe you = are not an intended recipient of this message, please notify the sender by = replying to this message and then deleting it from your system. Any use, di= ssemination, distribution, or reproduction of this message by unintended re= cipients is not authorized and may be unlawful.</span> --e89a8f3ba55f9d7703051ed4f175-- --===============37406814985996073== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit _______________________________________________________________________ eGenix.com User Mailing List http://www.egenix.com/ https://www.egenix.com/mailman/listinfo/egenix-users --===============37406814985996073==--