From no-reply at appveyor.com Thu Jan 4 08:55:28 2018 From: no-reply at appveyor.com (AppVeyor) Date: Thu, 04 Jan 2018 13:55:28 +0000 Subject: [freetds] Build failed: freetds 1007 Message-ID: <20180104135027.1.E2B6D98F42AF40EE@appveyor.com> From no-reply at appveyor.com Sat Jan 20 16:57:31 2018 From: no-reply at appveyor.com (AppVeyor) Date: Sat, 20 Jan 2018 21:57:31 +0000 Subject: [freetds] Build completed: freetds 1009 Message-ID: <20180120215731.1.B60F82B81489343B@appveyor.com> From sf at 4js.com Thu Jan 25 08:55:41 2018 From: sf at 4js.com (Sebastien FLAESCH) Date: Thu, 25 Jan 2018 14:55:41 +0100 Subject: [freetds] Support for SQL_SS_TIME2 / SQL_SS_TIME2_STRUCT Message-ID: <865bf2f1-8ebc-cf89-70ac-50335ab322ce@4js.com> Hi all, I need to know what is the status of SQL_SS_TIME2 / SQL_SS_TIME2_STRUCT support in 1.00 I am using 1.00.15 for now. When binding an SQL Parameter with this structure to insert a TIME(N) value, I get the following error: SQLState = HY003 Message = [FreeTDS][SQL Server]Program type out of range Is this structure/type properly supported? Where can I find some code example? What needs to be set in the C type, precision and scale in SQLBindParameter() ? Thanks! Seb From sf at 4js.com Thu Jan 25 10:41:47 2018 From: sf at 4js.com (Sebastien FLAESCH) Date: Thu, 25 Jan 2018 16:41:47 +0100 Subject: [freetds] Support for SQL_SS_TIME2 / SQL_SS_TIME2_STRUCT In-Reply-To: <865bf2f1-8ebc-cf89-70ac-50335ab322ce@4js.com> References: <865bf2f1-8ebc-cf89-70ac-50335ab322ce@4js.com> Message-ID: FYI I am using the binding params as described here: https://docs.microsoft.com/en-us/sql/relational-databases/native-client-odbc-how-to/use-date-and-time-types Seb On 01/25/2018 02:55 PM, Sebastien FLAESCH wrote: > Hi all, > > I need to know what is the status of SQL_SS_TIME2 / SQL_SS_TIME2_STRUCT support in 1.00 > > I am using 1.00.15 for now. > > When binding an SQL Parameter with this structure to insert a TIME(N) value, I get the following error: > > SQLState = HY003 > Message? = [FreeTDS][SQL Server]Program type out of range > > Is this structure/type properly supported? > > Where can I find some code example? > > What needs to be set in the C type, precision and scale in SQLBindParameter() ? > > Thanks! > Seb > _______________________________________________ > FreeTDS mailing list > FreeTDS at lists.ibiblio.org > https://lists.ibiblio.org/mailman/listinfo/freetds > From freddy77 at gmail.com Sat Jan 27 12:46:57 2018 From: freddy77 at gmail.com (Frediano Ziglio) Date: Sat, 27 Jan 2018 17:46:57 +0000 Subject: [freetds] Support for SQL_SS_TIME2 / SQL_SS_TIME2_STRUCT In-Reply-To: <865bf2f1-8ebc-cf89-70ac-50335ab322ce@4js.com> References: <865bf2f1-8ebc-cf89-70ac-50335ab322ce@4js.com> Message-ID: 2018-01-25 13:55 GMT+00:00 Sebastien FLAESCH : > Hi all, > > I need to know what is the status of SQL_SS_TIME2 / SQL_SS_TIME2_STRUCT > support in 1.00 > > I am using 1.00.15 for now. > > When binding an SQL Parameter with this structure to insert a TIME(N) value, > I get the following error: > > SQLState = HY003 > Message = [FreeTDS][SQL Server]Program type out of range > > Is this structure/type properly supported? > > Where can I find some code example? > > What needs to be set in the C type, precision and scale in > SQLBindParameter() ? > > Thanks! > Seb Hi, I though was implemented! But I just tested master and is not. Weird... there's some handling for SQL_SS_TIME2 from C to TDS but then the conversion fails as the conversion is not available in libTDS! Frediano From sf at 4js.com Sat Jan 27 13:03:00 2018 From: sf at 4js.com (Sebastien FLAESCH) Date: Sat, 27 Jan 2018 19:03:00 +0100 Subject: [freetds] Support for SQL_SS_TIME2 / SQL_SS_TIME2_STRUCT In-Reply-To: References: <865bf2f1-8ebc-cf89-70ac-50335ab322ce@4js.com> Message-ID: <3bdcca9e-d3d7-c502-3c5e-e17fb2045b10@4js.com> On 01/27/2018 06:46 PM, Frediano Ziglio wrote: > 2018-01-25 13:55 GMT+00:00 Sebastien FLAESCH : >> Hi all, >> >> I need to know what is the status of SQL_SS_TIME2 / SQL_SS_TIME2_STRUCT >> support in 1.00 >> >> I am using 1.00.15 for now. >> >> When binding an SQL Parameter with this structure to insert a TIME(N) value, >> I get the following error: >> >> SQLState = HY003 >> Message = [FreeTDS][SQL Server]Program type out of range >> >> Is this structure/type properly supported? >> >> Where can I find some code example? >> >> What needs to be set in the C type, precision and scale in >> SQLBindParameter() ? >> >> Thanks! >> Seb > > Hi, > I though was implemented! > > But I just tested master and is not. > Weird... there's some handling for SQL_SS_TIME2 from C to TDS but then > the conversion fails as the conversion is not available in libTDS! > > Frediano > _______________________________________________ > FreeTDS mailing list > FreeTDS at lists.ibiblio.org > https://lists.ibiblio.org/mailman/listinfo/freetds > Thanks for looking at this Frediano! From my tests (I have installed 1.00.80 now): It appears that SQL_SS_TIME2 / SQL_SS_TIME2_STRUCT can be used in SQLBindCol() but not with SQLBindParameter... One can use SQL_C_CHAR / SQL_VARCHAR to pass time data with SQLBindParameter(). However, for consistency, it would be nice to support SQL_SS_TIME2 / SQL_SS_TIME2_STRUCT also in SQLBindParameter(). Seb From lnrdghn at gmail.com Tue Feb 27 14:28:26 2018 From: lnrdghn at gmail.com (Leonard Gahan) Date: Tue, 27 Feb 2018 19:28:26 +0000 Subject: [freetds] NTLMv2 Support Message-ID: Hi folks, I'm working for a company that has been using the original Microsoft/Sybase db-library in their legacy C/C++ applications for many years. They are now looking to move away from this library as it has not been supported for some time and has a number of issues with more recent versions of SQL Server. As I understand it, the main issue is that the library does not support NTLMv2 and so they cannot use it to connect to remote SQL Server instances (only to local instances using Named Pipes). >From the Github commit history, user guide, and mailing list archives it seems FreeTDS does support NTLMv2 (and Kerberos) so we were thinking it might be a suitable replacement. Before getting too far into it though, I was hoping someone here could confirm that they've been able to successfully connect to remote SQL Server 2014+ instances using NTLMv2 (from Windows) and Kerberos (from Linux)? Many thanks, Leonard From freddy77 at gmail.com Wed Feb 28 02:32:37 2018 From: freddy77 at gmail.com (Frediano Ziglio) Date: Wed, 28 Feb 2018 07:32:37 +0000 Subject: [freetds] NTLMv2 Support In-Reply-To: References: Message-ID: 2018-02-27 19:28 GMT+00:00 Leonard Gahan : > Hi folks, > > I'm working for a company that has been using the original Microsoft/Sybase > db-library in their legacy C/C++ applications for many years. > > They are now looking to move away from this library as it has not been > supported for some time and has a number of issues with more recent > versions of SQL Server. > > As I understand it, the main issue is that the library does not support > NTLMv2 and so they cannot use it to connect to remote SQL Server instances > (only to local instances using Named Pipes). > > From the Github commit history, user guide, and mailing list archives it > seems FreeTDS does support NTLMv2 (and Kerberos) so we were thinking it > might be a suitable replacement. > > Before getting too far into it though, I was hoping someone here could > confirm that they've been able to successfully connect to remote SQL Server > 2014+ instances using NTLMv2 (from Windows) and Kerberos (from Linux)? > > Many thanks, > Leonard Hi, I don't know the exact combination but I don't see any reasons why this should not work. >From Windows the default and best option is to use SSPI which will provide the authentication options that best suit the system. >From Linux you can use either NTLMv2 or Kerberos. For NTLMv2 you have to provide username/password as Linux does not store AD authentication, for Kerberos you have to have a ticket ready. Maybe you need to specify some options like "use ntlmv2" (see http://www.freetds.org/userguide/freetdsconf.htm). Empty username and password are used for Kerberos authentication. Frediano From cejackson51 at gmail.com Tue Feb 27 15:14:26 2018 From: cejackson51 at gmail.com (Craig Jackson) Date: Tue, 27 Feb 2018 15:14:26 -0500 Subject: [freetds] NTLMv2 Support In-Reply-To: References: Message-ID: I'm interested in that you're using the old MS Db-Library. I'm working on the TDS support for Wireshark, and I don't have a copy of the old MS library for testing. Could you get me an install file? I don't think it's available from MS anymore. FYI, as far as I know freetds works fine. I know it was used for monitoring SQL Server from Linux at my last job. Craig Jackson On Feb 27, 2018 2:46 PM, "Leonard Gahan" wrote: Hi folks, I'm working for a company that has been using the original Microsoft/Sybase db-library in their legacy C/C++ applications for many years. They are now looking to move away from this library as it has not been supported for some time and has a number of issues with more recent versions of SQL Server. As I understand it, the main issue is that the library does not support NTLMv2 and so they cannot use it to connect to remote SQL Server instances (only to local instances using Named Pipes). >From the Github commit history, user guide, and mailing list archives it seems FreeTDS does support NTLMv2 (and Kerberos) so we were thinking it might be a suitable replacement. Before getting too far into it though, I was hoping someone here could confirm that they've been able to successfully connect to remote SQL Server 2014+ instances using NTLMv2 (from Windows) and Kerberos (from Linux)? Many thanks, Leonard _______________________________________________ FreeTDS mailing list FreeTDS at lists.ibiblio.org https://lists.ibiblio.org/mailman/listinfo/freetds From no-reply at appveyor.com Tue Mar 13 20:24:28 2018 From: no-reply at appveyor.com (AppVeyor) Date: Wed, 14 Mar 2018 00:24:28 +0000 Subject: [freetds] Build failed: freetds 1020 Message-ID: <20180314002428.1.F9765FE8604983BB@appveyor.com> From lnrdghn at gmail.com Thu Mar 8 06:26:07 2018 From: lnrdghn at gmail.com (Leonard Gahan) Date: Thu, 8 Mar 2018 11:26:07 +0000 Subject: [freetds] NTLMv2 Support In-Reply-To: References: Message-ID: Thanks for getting back to me and apologies for the late reply. As far as I know, the old MS library was last included with the SQL Server 2000 installer. I'm not actually able to copy files off the company network here but let me see if I can get the relevant files elsewhere and I'll send them on to you. I believe the key files you would need are ntwdblib.dll, sqlfront.h, and sqldb.h. Regards, Leonard On 27 February 2018 at 20:14, Craig Jackson wrote: > I'm interested in that you're using the old MS Db-Library. I'm working on > the TDS support for Wireshark, and I don't have a copy of the old MS > library for testing. Could you get me an install file? I don't think it's > available from MS anymore. > > FYI, as far as I know freetds works fine. I know it was used for monitoring > SQL Server from Linux at my last job. > > Craig Jackson > > On Feb 27, 2018 2:46 PM, "Leonard Gahan" wrote: > > Hi folks, > > I'm working for a company that has been using the original Microsoft/Sybase > db-library in their legacy C/C++ applications for many years. > > They are now looking to move away from this library as it has not been > supported for some time and has a number of issues with more recent > versions of SQL Server. > > As I understand it, the main issue is that the library does not support > NTLMv2 and so they cannot use it to connect to remote SQL Server instances > (only to local instances using Named Pipes). > > From the Github commit history, user guide, and mailing list archives it > seems FreeTDS does support NTLMv2 (and Kerberos) so we were thinking it > might be a suitable replacement. > > Before getting too far into it though, I was hoping someone here could > confirm that they've been able to successfully connect to remote SQL Server > 2014+ instances using NTLMv2 (from Windows) and Kerberos (from Linux)? > > Many thanks, > Leonard > _______________________________________________ > FreeTDS mailing list > FreeTDS at lists.ibiblio.org > https://lists.ibiblio.org/mailman/listinfo/freetds > _______________________________________________ > FreeTDS mailing list > FreeTDS at lists.ibiblio.org > https://lists.ibiblio.org/mailman/listinfo/freetds > From patrolliekaptein at gmail.com Thu Mar 8 07:14:09 2018 From: patrolliekaptein at gmail.com (Desmond Coertzen) Date: Thu, 8 Mar 2018 14:14:09 +0200 Subject: [freetds] Escape sequences on output data Message-ID: Hi there, I use freetds heavily to cart data backwards and forwards between mssql systems and linux based systems. I have encountered a problem with mssql character fields that contain control characters like tabs, CR, LF etc. TSQL outputs these in raw format always. Is there -o options available where escape sequences can be turned on or off? I have gone far with replace and quotename functions built into the queries, but it convoluted my scripts.I was hoping freetds has a built-in / native solution to enable/disable escaping at will. Thanks. From freddy77 at gmail.com Tue Mar 20 05:50:06 2018 From: freddy77 at gmail.com (Frediano Ziglio) Date: Tue, 20 Mar 2018 09:50:06 +0000 Subject: [freetds] Escape sequences on output data In-Reply-To: References: Message-ID: 2018-03-08 12:14 GMT+00:00 Desmond Coertzen : > Hi there, > > I use freetds heavily to cart data backwards and forwards between mssql > systems and linux based systems. I have encountered a problem with mssql > character fields that contain control characters like tabs, CR, LF etc. > TSQL outputs these in raw format always. Is there -o options available > where escape sequences can be turned on or off? > No, there's no option, column data are just printed. Currently you can use complicated terminators. Or propose an option/patch. > I have gone far with replace and quotename functions built into the > queries, but it convoluted my scripts.I was hoping freetds has a built-in / > native solution to enable/disable escaping at will. > > Thanks. Frediano From lacak at zoznam.sk Thu Mar 22 08:08:38 2018 From: lacak at zoznam.sk (LacaK) Date: Thu, 22 Mar 2018 13:08:38 +0100 Subject: [freetds] Default ANSI settings in FreeTDS odbc driver Message-ID: <203715e8-8a44-acee-5c83-0f1476ab7d1b@zoznam.sk> Hi *, are there any default settings, which FreeTDS odbc driver set-ups upon connection ? |setquoted_identifier setansi_warnings setansi_padding setansi_nulls setconcat_null_yields_null In my case INSERT on table with filtered index fails with error message, that above mentioned settings must be ON. This happens only on Linux with FreeTDS odc driver, on Windows with Microsoft driver this does not happen (so I guess that MS already sets these ANSI settings by default) Is there way how to set them in any INI file ? Or should I only send commands: ||"setquoted_identifier ON; setansi_warnings ON; setansi_padding ON; setansi_nulls ON; setconcat_null_yields_null ON;" | Thanks -Laco. From freddy77 at gmail.com Sat Mar 24 17:42:41 2018 From: freddy77 at gmail.com (Frediano Ziglio) Date: Sat, 24 Mar 2018 21:42:41 +0000 Subject: [freetds] Default ANSI settings in FreeTDS odbc driver In-Reply-To: <203715e8-8a44-acee-5c83-0f1476ab7d1b@zoznam.sk> References: <203715e8-8a44-acee-5c83-0f1476ab7d1b@zoznam.sk> Message-ID: 2018-03-22 12:08 GMT+00:00 LacaK : > Hi *, > > are there any default settings, which FreeTDS odbc driver set-ups upon > connection ? > > |setquoted_identifier setansi_warnings setansi_padding setansi_nulls > setconcat_null_yields_null In my case INSERT on table with filtered index > fails with error message, that above mentioned settings must be ON. This > happens only on Linux with FreeTDS odc driver, on Windows with Microsoft > driver this does not happen (so I guess that MS already sets these ANSI > settings by default) Is there way how to set them in any INI file ? Or > should I only send commands: ||"setquoted_identifier ON; setansi_warnings > ON; setansi_padding ON; setansi_nulls ON; setconcat_null_yields_null ON;" | > Thanks > -Laco. > Weird, they should have the same settings. There's a bit in the login packet that should set odbc/others like settings, if you use the odbc driver this bit should be compatible with Microsoft drivers. Frediano From lacak at zoznam.sk Mon Mar 26 07:41:21 2018 From: lacak at zoznam.sk (LacaK) Date: Mon, 26 Mar 2018 13:41:21 +0200 Subject: [freetds] Default ANSI settings in FreeTDS odbc driver In-Reply-To: References: <203715e8-8a44-acee-5c83-0f1476ab7d1b@zoznam.sk> Message-ID: <33ee6423-936d-9e8f-151f-db03ad88bcc6@zoznam.sk> >> Hi *, >> >> are there any default settings, which FreeTDS odbc driver set-ups upon >> connection ? >> >> |setquoted_identifier setansi_warnings setansi_padding setansi_nulls >> setconcat_null_yields_null In my case INSERT on table with filtered index >> fails with error message, that above mentioned settings must be ON. This >> happens only on Linux with FreeTDS odc driver, on Windows with Microsoft >> driver this does not happen (so I guess that MS already sets these ANSI >> settings by default) Is there way how to set them in any INI file ? Or >> should I only send commands: ||"setquoted_identifier ON; setansi_warnings >> ON; setansi_padding ON; setansi_nulls ON; setconcat_null_yields_null ON;" | >> Thanks >> -Laco. >> > Weird, they should have the same settings. There's a bit in the login > packet that should set odbc/others like settings, if you use the odbc > driver this bit should be compatible with Microsoft drivers. Thank you for reply. I can confirm, that these ANSI settings are inherited from Database Properties / Options (when I set these settings on database then they are inherited in each connection from Linux ODBC; so Linux FreeTDS ODBC driver does not modify this settings) But it seems, that Microsoft SQL Server ODBC driver (at least in Windows) sets own setting upon connection. So there is different behavior between Linux FreeTDS ODBC driver and Windows Microsoft ODBC driver. No problem for me, now when I know what happens I can work-around this ... -Laco. From no-reply at appveyor.com Mon Mar 26 11:45:53 2018 From: no-reply at appveyor.com (AppVeyor) Date: Mon, 26 Mar 2018 15:45:53 +0000 Subject: [freetds] Build completed: freetds 1023 Message-ID: <20180326154553.1.DE7381196401698A@appveyor.com>