odbc

Switching from sqloledb to odbc driver 13 for SQL Server

百般思念 提交于 2020-02-25 10:08:28
问题 I want to use Always Encrypted feature introduce in SQL Server 2016 SP1 . In order to do that, I need to use the new ODBC Driver 13.1 for SQL Server instead the current one sqloledb . It seems it is breaking my application, for example, when XML is returned. Here, it is said that: In order to take advantage of new features introduced in SQL Server 2005 such as multiple active result sets (MARS), query notifications, user-defined types (UDTs), or the new xml data type, existing applications

First argument is not an open RODBC channel

若如初见. 提交于 2020-02-24 18:58:54
问题 I am connecting to an Oracle database via DNS (set up the connection on the tnsnames.ora with the name "database"). I am able to succesfully run the following code: con <- DBI::dbConnect(odbc::odbc(), "database", UID = "user", PWD = "password", trusted_connection = TRUE) I am also able to succesfully list all the tables in the database via: list <- dbListTables(con) View(list) However, when I run: results <- sqlQuery(channel = con, query = "select * from myschemaname.table") I get the error:

First argument is not an open RODBC channel

会有一股神秘感。 提交于 2020-02-24 18:58:26
问题 I am connecting to an Oracle database via DNS (set up the connection on the tnsnames.ora with the name "database"). I am able to succesfully run the following code: con <- DBI::dbConnect(odbc::odbc(), "database", UID = "user", PWD = "password", trusted_connection = TRUE) I am also able to succesfully list all the tables in the database via: list <- dbListTables(con) View(list) However, when I run: results <- sqlQuery(channel = con, query = "select * from myschemaname.table") I get the error:

First argument is not an open RODBC channel

扶醉桌前 提交于 2020-02-24 18:58:12
问题 I am connecting to an Oracle database via DNS (set up the connection on the tnsnames.ora with the name "database"). I am able to succesfully run the following code: con <- DBI::dbConnect(odbc::odbc(), "database", UID = "user", PWD = "password", trusted_connection = TRUE) I am also able to succesfully list all the tables in the database via: list <- dbListTables(con) View(list) However, when I run: results <- sqlQuery(channel = con, query = "select * from myschemaname.table") I get the error:

How to use mod_authn_dbd with SQL Server (ODBC)

坚强是说给别人听的谎言 提交于 2020-02-07 04:13:09
问题 There are many tutorial for using mod_authn_dbd with MySQL but I could not find any with SQL Server using ODBC. It took me a while to figure it out, so I decided to write it up here. It's not a full blown tutorial but it should be enough to get you up and running. 回答1: All commands must be run as root or using sudo. Install Microsoft ODBC drivers for Linux Instructions on Microsoft site Example for Debian 9: apt update apt install curl apt-transport-https curl https://packages.microsoft.com

Progress database, OpenLink, OpenEdge compatibility

陌路散爱 提交于 2020-02-05 02:36:11
问题 I am configuring several Windows 10 systems that will need to reliably connect via ODBC using system DSNs to both Progress version 9.x and Progress version 10.x databases. I have been told by one of our IT staff that interfacing with Progress versions 9.x servers require the OpenLink ODBC client software, while interfacing with Progress 10.x requires the OpenEdge ODBC client software. I am not completely confident that this is true, but I have not been able to find any authoritative

Is it possible to read to a Paradox 7.x .db file in a .Net app?

独自空忆成欢 提交于 2020-02-04 02:46:27
问题 I'm trying to read a Paradox 7.x .db file in a .Net 3.5 app and I'm not being successful on that. First of all, when I'm registering the odbc, as a user or system dsn, the Microsoft Paradox ODBC Driver only display versions up to 5.x, so it looks like that it does not support Paradox version 7.x. At connectionsstrings.com I've found the connection string that is supposed to work with Paradox 7.x: Provider=MSDASQL;Persist Security Info=False;Mode=Read; Extended Properties='DSN=Paradox;DBQ=C:

OLEDE Error: Login failed for user 'DOMAIN\ComputerName$'.;28000

和自甴很熟 提交于 2020-02-03 08:22:13
问题 I am trying to deploy an Analysis Services cube in SQL Server 2012. My user account is REALM\Merin where REALM is the domain and my computer's name is Hercules . I am already in Analysis Service's administrator group. When I process the cube using SQL Server Data Tools, I get following error. OLE DB error: OLE DB or ODBC error. Login failed for user 'REALM\Hercules$'.; 28000. My user account is REALM\Merin but I don't know why it is complaining about user REALM\Hercules$. What does this

OLEDE Error: Login failed for user 'DOMAIN\ComputerName$'.;28000

风流意气都作罢 提交于 2020-02-03 08:21:51
问题 I am trying to deploy an Analysis Services cube in SQL Server 2012. My user account is REALM\Merin where REALM is the domain and my computer's name is Hercules . I am already in Analysis Service's administrator group. When I process the cube using SQL Server Data Tools, I get following error. OLE DB error: OLE DB or ODBC error. Login failed for user 'REALM\Hercules$'.; 28000. My user account is REALM\Merin but I don't know why it is complaining about user REALM\Hercules$. What does this

POCO libraries: MinGW (MSYS2) compilation has generated libPocoDataODBC.dll with missing entry points (Poco::Data::ODBC::Connector::registerConnector)

依然范特西╮ 提交于 2020-01-25 09:28:14
问题 I have succeeded compiling POCO libraries with MinGW64 (MSYS2). To build it, I installed Windows SDK and added to the PATH environment the path to mc.exe , so I executed: pacman -S mingw-w64-x86_64-cmake # Get POCO git clone -b master https://github.com/pocoproject/poco.git # set Windows SDK to the PATH export PATH="/c/Program Files (x86)/Windows Kits/10/bin/10.0.18362.0/x64:$PATH" # Prepare compilation cd poco /mingw64/bin/cmake -G "MSYS Makefiles" .. # Compile make The compilation succeeded