unixodbc

SQL Server queries beyond a certain character length are timing out

。_饼干妹妹 提交于 2021-02-11 16:33:44
问题 Recently I migrated an ETL platform from Python 2.7 to 3 and also updated its Docker image from Ubuntu 16.04 to 18.04. After the migration I started encountering some really strange behavior when trying to reflect SQL Server tables using SQLAlchemy with the pyodbc driver. Initially, I was seeing this error message: [08S01] [FreeTDS][SQL Server]Read from the server failed (20004) (SQLExecDirectW) I had updated SQLAlchemy from 0.9.8 to 1.3.10 (I hadn't touched pyodbc which was at 3.0.10) so I

SQL Server queries beyond a certain character length are timing out

谁说胖子不能爱 提交于 2021-02-11 16:31:51
问题 Recently I migrated an ETL platform from Python 2.7 to 3 and also updated its Docker image from Ubuntu 16.04 to 18.04. After the migration I started encountering some really strange behavior when trying to reflect SQL Server tables using SQLAlchemy with the pyodbc driver. Initially, I was seeing this error message: [08S01] [FreeTDS][SQL Server]Read from the server failed (20004) (SQLExecDirectW) I had updated SQLAlchemy from 0.9.8 to 1.3.10 (I hadn't touched pyodbc which was at 3.0.10) so I

SQL Server queries beyond a certain character length are timing out

送分小仙女□ 提交于 2021-02-11 16:31:31
问题 Recently I migrated an ETL platform from Python 2.7 to 3 and also updated its Docker image from Ubuntu 16.04 to 18.04. After the migration I started encountering some really strange behavior when trying to reflect SQL Server tables using SQLAlchemy with the pyodbc driver. Initially, I was seeing this error message: [08S01] [FreeTDS][SQL Server]Read from the server failed (20004) (SQLExecDirectW) I had updated SQLAlchemy from 0.9.8 to 1.3.10 (I hadn't touched pyodbc which was at 3.0.10) so I

SQL Server queries beyond a certain character length are timing out

淺唱寂寞╮ 提交于 2021-02-11 16:30:26
问题 Recently I migrated an ETL platform from Python 2.7 to 3 and also updated its Docker image from Ubuntu 16.04 to 18.04. After the migration I started encountering some really strange behavior when trying to reflect SQL Server tables using SQLAlchemy with the pyodbc driver. Initially, I was seeing this error message: [08S01] [FreeTDS][SQL Server]Read from the server failed (20004) (SQLExecDirectW) I had updated SQLAlchemy from 0.9.8 to 1.3.10 (I hadn't touched pyodbc which was at 3.0.10) so I

How to connect to SQL Server using FreeTDS ODBC

半腔热情 提交于 2021-02-10 15:57:11
问题 I am trying to connect to my company's SQL Server Databases via my MacBook and have followed the steps outlined here: https://github.com/mkleehammer/pyodbc/wiki/Connecting-to-SQL-Server-from-Mac-OSX but keep getting the following error when I get to the following step: Check that all is OK by running isql TEST myuser mypassword . You should see the following: +---------------------------------------+ | Connected! | | | | sql-statement | | help [tablename] | | quit | | | +---------------------

How to connect to SQL Server using FreeTDS ODBC

元气小坏坏 提交于 2021-02-10 15:56:00
问题 I am trying to connect to my company's SQL Server Databases via my MacBook and have followed the steps outlined here: https://github.com/mkleehammer/pyodbc/wiki/Connecting-to-SQL-Server-from-Mac-OSX but keep getting the following error when I get to the following step: Check that all is OK by running isql TEST myuser mypassword . You should see the following: +---------------------------------------+ | Connected! | | | | sql-statement | | help [tablename] | | quit | | | +---------------------

centos7安装sql-server2017

不打扰是莪最后的温柔 提交于 2021-02-05 09:57:23
1. 关闭selinux Vim /etc/selinux/conf 将selinux=enable 改成selinux=disabled 2. 清空/关闭iptables策略 Iptables –L Iptabels –F Service stop iptables /etc/init.d/iptables save 3. 下载163yum源 wget http://mirrors.163.com/.help/CentOS7-Base-163.repo 更新yum源 4. 下载sql-server2017yum源 curl -o /etc/yum.repos.d/mssql-server.repo https://packages.microsoft.com/config/rhel/7/mssql-server-preview.repo 5.yum 安装sql-server yum install -y mssql-server 6. 安装完成之后,执行下面命令,根据提示设置SA密码,并选择相应的版本 /opt/mssql/bin/mssql-conf setup 7. 开启防火墙上的 SQL Server 端口,默认为TCP 1433 sudo firewall-cmd --zone=public --add-port=1433/tcp --permanent sudo

iSeries Access ODBC Driver with unixodbc on Debian - Invalid UTF-8 characters being returned from iSeries

只谈情不闲聊 提交于 2021-01-29 19:38:36
问题 Using ODBC driver, ibm-iaccess-1.1.0.10-1.0.amd64, on Debian Linux. When I perform a php sql query and validate the response, I see some of the data returned is not valid utf-8. mb_check_encoding returns 'false' and the character on screen in a chrome browser is the diamond question mark character. This happens on a few CHAR field types. if(!mb_check_encoding($row["field"])) { ... exit with utf-8 error } I can work around this by converting from UTF-8 to UTF-8: mb_convert_encoding($row["field

Connecting Oracle using unixODBC: Can't open lib '/usr/lib/oracle/12.1/client/lib/libsqora.so.12.1'

走远了吗. 提交于 2021-01-28 03:41:30
问题 I am trying to connect to Oracle using unixODBC but it doesn't work. So far I have tried to follow How do I setup Oracle ODBC drivers on RHEL 6/Linux . When I try to connect using isql I get following: user@user:~$ isql -v oracle-jono [01000][unixODBC][Driver Manager]Can't open lib '/usr/lib/oracle/12.1/client/lib/libsqora.so.12.1' : file not found [ISQL]ERROR: Could not SQLConnect I have checked that /usr/lib/oracle/12.1/client/lib/libsqora.so.12.1 exists. When I run ldd command it says that

配置ODBC

对着背影说爱祢 提交于 2020-12-17 07:51:14
rpm -q gcc tar xzvf unixODBC-2.3.0.tar.gz cd unixODBC-2.3.0/ ./configure --enable-gui=no make && make install odbc_config -j odbc_config --odbcini odbc_config --odbcinstini vim /usr/local/etc/odbc.ini [dm8] description=dm8 driver=odbc dm8 server=192.168.6.110 uid=sysdba pwd=EnmoEdu123 tcp_port=5252 vim /usr/local/etc/odbcinst.ini [odbc dm8] description=odbc dm8 driver=/opt/dm8/drivers/odbc/libdodbc.so [dmdba@enmoedu1 ~]$ isql dm8 +---------------------------------------+ Connected! sql-statement help [tablename] quit +---------------------------------------+ SQL> 来源: oschina 链接: https://my