We have recently upgraded the SQL Server and SSIS projects from 2012 to 2019 version. Since this upgrade, one SSIS project is taking very huge time for completion. This SSIS project has a package which loads data from MySQL ODBC source and insert it into another MySQL ODBC destination via data flow task. The data is inserted in batches of 100K rows. Each batch previously took around 30 seconds but now it is taking 5 minutes.
I have tried out below things but nothing fixed the issue:
Used different versions of MySQL ODBC drivers i.e. MySQL ODBC 5.3 Unicode Driver and MySQL ODBC 8.0 Unicode Driver
Recreated the data flow task
Added new ODBC connections in SSIS package and used them into data flow task
Related
I have managed this in the past on two separate machines. Now one machine has lost the DSNs and I cannot for the life of me add them back.
Uninstalled all MariaDB exes and MariaDB ODBC drivers.
Installed latest MariDB 10.5 and latest 32-bit MariaDB ODBC 3.1 drivers 3.1.9 (26/6/20)
Using ODBCad64 I am informed I am not administrator when I am (but this is not a huge problem, and other answers point to Office causing this).
I want to use 32bit drivers with VFP9 anyway, so usually run ODBCad32.exe as administrator, go to System DSNs and Add...
I can add any of the listed drivers except the MariaDB ODBC 3.1 Driver, which just shows a thinking-about-it cursor for a few seconds, then nothing, rather than the dialogue to choose the data source.
This behaviour occurs on User DSNs as well. On a separate Win10 machine I correctly get the next dialogue "Create a new Data Source to MariaDB" wizard, which I have had in the past on the problem machine. The problem machine will be the production database server, and has worked perfectly in the past, before losing the DSNs.
The other machine is development and bizarrely can still connect to the production machine, even though I uninstalled and reinstalled everything there and haven't setup DSNs there, and cannot see any existing ones. The development machine connects to MariaDB 10.05 (correct, just installed that on the production machine 10 minutes ago) using DRIVER={MariaDB ODBC 3.1 Driver};TCPIP=1;SERVER=;UID=root;PWD=*******;PORT=4306 (there is an existing service on 3306).
So the Driver appears to be working remotely, but I cannot add DSNs to use ODBC locally. What I can do is (locally) send the complete SQL connection string from VFP i.e. a DSN-less connection.
Any ideas much appreciated!
I have a requirement in BizTalk to connect to sybase database.
we are using BizTalk 2013 R2. I tried all ways to connect but not successful.
ODBC(Twoconnect)
Its showing up in admin console and when using add generated items in visual studio but the mysql option is not showing up in visual studio.I did install the older 5.3 my sql connector versions as the new 8 series throws an error when installing.
https://downloads.mysql.com/archives/c-odbc/
https://social.technet.microsoft.com/wiki/contents/articles/12824.biztalk-server-list-of-custom-adapters.aspx#hhh
In the technet link the ODBC is supported till BizTalk 2013.
CDATA
I have also tried to connect using CDATA
https://www.cdata.com/drivers/sybase/biztalk/
but it looks like the connection string is invalid when i try.
I am trying to provide servername,DB name,UserID,password and port number.It says specified connecting string in Invalid.
Not sure how to proceed further.
System specs: 64-bit OS (Win7), 64-bit R (3.3.3), 32-bit MS Access (2016).
I have data in a 32-bit .accdb file and I want to read it into R. I tried this:
con <- odbc::dbConnect(odbc::odbc(),
dsn="MS Access Database")
but saw the following error:
Error: nanodbc/nanodbc.cpp:950: IM014: [Microsoft][ODBC Driver Manager]
The specified DSN contains an architecture mismatch between the Driver and Application
Web search indicated that the bit difference between R and the database is the culprit. The default ODBC manager in Windows doesn't include drivers for MS Access (or rather, it seems to, but attempting to manage them using that tool gives you an architecture error). Following other advice, I used the ODBC manager for 32-bit programs (c:\windows\sysWOW64\odbcad32.exe) to create a new DSN with a new name for MS Access files, and then called this DSN:
con <- odbc::dbConnect(odbc::odbc(),
dsn="MSAccess32")
I got the same error, however, and suspect there is something I don't understand about what this error means. Is there a known workaround for the problem?
The access file itself knows nothing about bitness, its only about the client application and the bitness of the odbc driver:
If your R is 64 bit, you need the 64bit ODBC driver for access and therefore also use the odbc manager for 64bit, which is C:\Windows\System32\odbcad32.exe (in Win7 64bit).
While if your R is 32bit, you need the 32bit ODBC driver, located at C:\Windows\SysWOW64\odbcad32.exe.
You can download the required Access Database Engine 2010 Redistributable from here: https://www.microsoft.com/en-US/download/details.aspx?id=13255
So, download the 64 bit Access Database driver, create a 64bit DSN entry and you should be fine.
I have created an ASP.net web application which reads data from excel sheet and displays it in jquery data table.
After taking a build and deploying it on IIS 8, it works fine on my machine. But once I deploy it on another machine which has 32 bit office installed, there is Microsoft.OLEDB 12.0 driver not registered error.
But even after installing microsoft redistriuable and data connectivity components I am getting the same exception.
Every answer on stackoverflow covers driver installation but it dosen't help in my case.
I have a database: Oracle SQL Developer 3.2.20.9
an asp.net web application running locally on a pc with Windows 7 enterprise 64 bit, and to developed it I used Visual Studio 2013.
Now I should connect the application with the db so I' m trying to install:
Oracle 10g ODAC and Oracle Developer Tools for Visual Studio .NET
I get this Error:
"Abnormal program termination. an internal error has occured. Please provide the following files to Oracle Support:
Unknown
Unknown
Unknown"
Could I connect the webapp in other ways?
When I go to Server Explorer in Visual Studio and I choose connect to database -> add connection -> Oracle database -> .NET framework Data Provider for Oracle
I get:
"This provider is deprecated and should not be used. Instead, download Oracle Developer Tools for visual Studio for comprehensive integration with Oracle databases."
Oracle supports connections back two versions. You should try installing the ODAC client for 11g as that will connect to a version 10 database and supports windows 7.
Seeing as SQL developer is free why not get the latest version 4.02 here
Be sure to get an ODAC version that matches the bitness of the database, 32 bit or 64 bit. You can check this by logging onto the machine with Run > cmd > sqlplus > connect as your user/your password. If the header that is returned does not say 64 bit then the database is a 32 bit install and you need ODAC to match that.
And seeing as connecting to Oracle is popular question a good troubleshooting routine is
connect from sqlplus on the database
connect with sql developer from your client pc
then try connecting through Visual Studio.