Click here to monitor SSC
SQLServerCentral is supported by Redgate
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase ««12

SSIS mysql to mssql Expand / Collapse
Author
Message
Posted Friday, September 20, 2013 2:39 AM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Tuesday, December 15, 2015 12:07 PM
Points: 8, Visits: 59
I created in
C:\Windows\SysWOW64\odbcad32.exe
and
I instaled mysql-connector-odbc-5.1.12-win32
Post #1496752
Posted Friday, September 20, 2013 3:07 AM
SSChasing Mays

SSChasing MaysSSChasing MaysSSChasing MaysSSChasing MaysSSChasing MaysSSChasing MaysSSChasing MaysSSChasing Mays

Group: General Forum Members
Last Login: Wednesday, March 30, 2016 3:20 PM
Points: 626, Visits: 1,058
Hi
It looks you have 32-bit odbc drivers , try to run your package from cmd using :

<drive>:\ Program Files(x86)\Microsoft SQL Server\110\DTS\Binn\DTExec.exe /F <your package>
and let us know the status.

Br.
Mike
Post #1496755
Posted Friday, September 20, 2013 4:05 AM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Tuesday, December 15, 2015 12:07 PM
Points: 8, Visits: 59
Sorry I have 64

I ran in cmp and I have error.

Description: Failed to decrypt protected XML node "DTS:Password" with error 0x8009000B "Nieprawidłowy klucz do użycia w podanym stanie.". You may not be authorized to access this information. This error occurs when there is a cryptograph
Verify that the correct key is available.
Post #1496776
Posted Friday, September 20, 2013 4:49 AM
SSChasing Mays

SSChasing MaysSSChasing MaysSSChasing MaysSSChasing MaysSSChasing MaysSSChasing MaysSSChasing MaysSSChasing Mays

Group: General Forum Members
Last Login: Wednesday, March 30, 2016 3:20 PM
Points: 626, Visits: 1,058
Hi

I'm guessing that your native SQL connections are 'trusted'
,so please set Protection Level for this package to "DontSaveSensitive" and try again run in 32-bit mode:

<drive>:\ Program Files(x86)\Microsoft SQL Server\110\DTS\Binn\DTExec.exe /F <your package>

and then in 64-bit mode:

<drive>:\ Program Files\Microsoft SQL Server\110\DTS\Binn\DTExec.exe /F <your package>

Br.
Mike
Post #1496799
Posted Monday, September 23, 2013 12:25 AM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Tuesday, December 15, 2015 12:07 PM
Points: 8, Visits: 59
Problem is the end.
I change ADO NET -> MySQL Data provider to ADO NET ->Odbc Data Provider and I don't used user DSN but I connect direct use connect string "Driver={MySQL ODBC 5.1 Driver};server=<myServer>;uid=<user>;port=3306;database=<NameDataBase>;user=<user>;option=3"

Thank you for help
Post #1497273
Posted Monday, June 20, 2016 6:13 PM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Yesterday @ 10:49 AM
Points: 3, Visits: 204
I can confirm that calling out the specific driver name (including ANSI vs Unicode) in the connection string is the only way this worked for me. I have installed 32-bit drivers on both dev machine (Windows 7 64 bit with VS 2015 Enterprise, SSDT 14.0.60413.0) and prod SSIS server (Windows 2012R2, SQL Server 2014) and added DSN using the 32-bit ODBC adminstror. Package would fail on the prod server because it couldn't create connection.

One thing to make sure to execute the package using 32-bit runtime on the prod server.
Post #1796002
« Prev Topic | Next Topic »

Add to briefcase ««12

Permissions Expand / Collapse