Devart Forums

Thanks guys for resolving the issue! The re-install went perfectly and the SQL Agent Job runs now :-)

The source task allows you to run SQL statements (at least in the MySQL component). I am using it that way to TRUNCATE and call procedures, the last statement has to be something that returns something.

SELECT '' as workaround;

The component may not be designed for that but it works.

Hi,

I resolved the SSDT issue with setting Run64BitRuntime to false for the project.

Answers to your questions
1) I have installed the SSIS Data Flow component from the devartssis.exe version 1.12.1167
2) SQL 2019 64-bit with CU4, Windows 2016 server with .NET framework 4.8
3) All assemblies are found in their respective folders

However, running the package as a job in SQL Server Agent is failing for me.

What I have noticed in the SSIS error log

Data Flow Task:Error: The managed pipeline component
"Devart.SSIS.MySql.MySqlSource,
Devart.SSIS.MySql.150, Version=1.0.0.0, Culture=neutral,
PublicKeyToken=09af7300eec23701" could not be loaded.
The exception was: Could not load file or assembly
'Microsoft.SqlServer.PipelineHost, Version=15.100.0.0,
Culture=neutral, PublicKeyToken=89845dcd8080cc91' or
one of its dependencies. The system cannot find the file
specified..
Data Flow Task Data Flow Task (Devart MySql
Source [20])
Package:Error:

While on the server I can only find Microsoft.SqlServer.PipelineHost version 15.0.200
If this is the issue, from where can I find version 15.100 of this binary and update the server?

Cheers

Hi,

I have installed the latest Devart connection manager for MySQL on a Windows Server 2016 and SQL 2019 Standard Edition. Using VisualStudio SSDT 15.9.23. I am getting below errors in SSDT when the project is configured as TargetServerVersion SQL 2019.

[SSIS.Pipeline] Error: The component metadata for "Devart MySql Source, clsid {7CDF593F-DE06-4ABD-B356-7976EF7AC8E0}" could not be upgraded to the newer version of the component. The PerformUpgrade method failed.


[SSIS.Pipeline] Error: Cannot find the connection manager with ID "{0C741C0F-3F7D-4445-9701-AF271F8ADBB0}" in the connection manager collection due to error code 0xC0010009. That connection manager is needed by "Devart MySql Source.Connections[Devart MySql]" in the connection manager collection of "Devart MySql Source". Verify that a connection manager in the connection manager collection, Connections, has been created with that ID.

In above case, I created a clean project with TargetServerVersion SQL 2019, and added the connection to a package.
However if I create a project with TargetServerVersion SQL 2017 it works except when running as a SQL Server Job.

I can see that there is Devart.SSIS.MySql.150.dll in the Assemblies folder. Could it be that SSDT is selecting the wrong dll when in TargetServerVersion SQL 2019 or what I am missing?

Update:
I can see that the right .dll is used but it still doesn't work.
Devart.SSIS.MySql.MySqlSource, Devart.SSIS.MySql.150, Version=1.0.0.0, Culture=neutral, PublicKeyToken=09af7300eec23701

Hi folks,

I need to configure my packages' MySQL connection to operate in different environments (dev, stage and prod).
Our MySQL databases access is over SSH.

I have added the remote server's name as and expression @[User::RemoteServer] to the expression editor's 'Server' property and I need to do them same for the SSH Host. However the Advanced Properties like 'SSH Host' doesn't appear in the expression editor's property list!

Any workaround, other than putting the whole connection string as an expression into the the 'ConnectionString' property?

Cheers