SSIS MySQL Component for SSDT 2015

Discussion of issues, suggestions and bugs of Devart SSIS Data Flow Components, our product line for building SSIS-based ETL solutions, performing data access to popular cloud applications and databases.
Post Reply
sqlrunner
Posts: 4
Joined: Wed 22 Nov 2017 17:32

SSIS MySQL Component for SSDT 2015

Post by sqlrunner » Wed 22 Nov 2017 17:37

Is there a version of the SSIS component for MySQL for SSDT 2015? I installed the version provided in the download page and when I ran SSDT 2015 I noticed the component is not in the toolbox. I looked through the forums and noticed the suggestion was to make sure the .dll exists in the /110,/120/130 directories. SSDT 2015 is in /140.

Am I missing something?

Pinturiccio
Devart Team
Posts: 2420
Joined: Wed 02 Nov 2011 09:44

Re: SSIS MySQL Component for SSDT 2015

Post by Pinturiccio » Fri 24 Nov 2017 16:49

sqlrunner wrote:SSDT 2015 is in /140
"/140" means SQL Server 2017. SSDT works with SQL Server 2016 by default. Please right-click your SSIS project in Solution Explorer and click Properties, then check the value of the TargetServerVersion property. If it is set to "SQL Server 2017", change it to other value (e.g., "SQL Server 2016").

SSIS Data Flow Components do not support SSDT for Visual Studio 2017 and SQL Server 2017 yet. The support of SSDT for Visual Studio 2017 is on our todo list. We will post here when we support it.

sqlrunner
Posts: 4
Joined: Wed 22 Nov 2017 17:32

Re: SSIS MySQL Component for SSDT 2015

Post by sqlrunner » Fri 24 Nov 2017 18:36

SSDT 2015 does allow for and by default the destination is SQL Server 2017. When I change the destination to SQL Server 2016, the SSIS component it still doesn't show. As a side note SSDT 2015 is part of Visual Studio 2015, not 2017.

Pinturiccio
Devart Team
Posts: 2420
Joined: Wed 02 Nov 2011 09:44

Re: SSIS MySQL Component for SSDT 2015

Post by Pinturiccio » Tue 28 Nov 2017 15:07

sqlrunner wrote:When I change the destination to SQL Server 2016, the SSIS component it still doesn't show.
SSIS Data Flow components should be added to SSIS Toolbox automatically. Devart components are in SSIS Toolbox (not ordinary Toolbox), when a project is open, and you switched to the Data Flow tab. Devart components are added to the Common tab of the SSIS Toolbox.

If there are no Devart components in SSIS Toolbox after you change the TargetServerVersion property to SQL Server 2016, please make sure that the Devart.SSIS.MySql.130.dll assembly is present in the C:\Program Files (x86)\Microsoft SQL Server\130\DTS\PipelineComponents\ folder. If there is no such assembly, copy it there from the C:\Program Files (x86)\Devart\SSIS Data Flow\Assemblies\ folder.

zpt2
Posts: 1
Joined: Mon 04 Dec 2017 10:29

Re: SSIS MySQL Component for SSDT 2015

Post by zpt2 » Mon 04 Dec 2017 11:23

Pinturiccio wrote:
SSIS Data Flow Components do not support SSDT for Visual Studio 2017 and SQL Server 2017 yet. The support of SSDT for Visual Studio 2017 is on our todo list. We will post here when we support it.
Hi Pinturiccio,

do you have any info when SSIS Data Flow Components will support SQL Server 2017? What is the plan?

Thank you

Pinturiccio
Devart Team
Posts: 2420
Joined: Wed 02 Nov 2011 09:44

Re: SSIS MySQL Component for SSDT 2015

Post by Pinturiccio » Wed 06 Dec 2017 13:34

We can't tell whether SQL Server 2017 will be supported in next public build, but we intend to support SQL Server 2017 and SSDT 2017 in the near feature.

Pinturiccio
Devart Team
Posts: 2420
Joined: Wed 02 Nov 2011 09:44

Re: SSIS MySQL Component for SSDT 2015

Post by Pinturiccio » Fri 08 Dec 2017 14:43

We have supported SSIS components and connections for SSDT 2017. We will post here when the corresponding build of SSIS Data Flow Components is available for download.

Pinturiccio
Devart Team
Posts: 2420
Joined: Wed 02 Nov 2011 09:44

Re: SSIS MySQL Component for SSDT 2015

Post by Pinturiccio » Fri 12 Jan 2018 15:19

New version of Devart SSIS Data Flow Components 1.6 is released.
It can be downloaded from https://www.devart.com/ssis/download.html or from Customer Portal (for users with valid subscription only).
For more information, please refer to viewtopic.php?t=36454

Post Reply