Menu
We migrated packages from Visual Studio 2012 to 2017 There is no cdc source component in the ssis toolbox:
and the cdc source component looks like:
And cannot be opened as well.
If I create a new Visual Studio 2017 Project it has the cdc source component in the ssis toolbox:
and I can work with it:
557
SQL Server 2012 - Visual Studio 2010 (SSDT, available on SQL Server installation media) or Visual Studio 2012 (SSDT-BI, available as a separate download)
SSDT is backwards compatible, so you can always use the newest SSDT to design and deploy databases, models, reports, and packages that run on older versions of SQL Server.
Right-click the solution, point to Add, and then click Existing Project.
The SQL Server Data Tools (SSDT) is where you'll spend most of your time as an SSIS developer. It is where you create and deploy your SSIS projects. SSDT uses a subset of the full version of Visual Studio 2013.
I was researching this issue a bit and found that some people have success migrating packages by just changing the target version of the packages from 2012 to 2016. Have a look at this blog post to see it in action.
187
First of all, it is good to post the upgrade results, so it can more clarify the issue. Also upgrade operations are not always working 100%, i faced many issue after upgrading package, which in many times caused to recreate packages from scratch.
.dtsx files are written in XML
One thing i can suggest, create a ssis 2017 package that contains CDC Source with the same configuration, and open both dtsx files (the new package and the upgraded package) with a text editor, and compare both XML syntax of the CDC Source, i can leads you to the issue cause
Comparing PackageFormatVersion, VersionBuild, and other properties can lead to the issue
Also try comparing both packages version informations, so from the PackageFormatVersion (if it is the same between the two packages that mean that they are both targeted to SQL Server 2012 so you need to change the Target version in the solution properties) and other field you can get if there is any difference or it can lead you to the issue.
Read more about getting packages informations in my answer on the following question: Automate Version number Retrieval from .Dtsx files
Also read more about changing target version in this Microsoft article - Version targeting in Integration Services projects section
If none of the first suggestions leads you to the issue cause, i didn't find a precise cause. but i find some links showing some problem when upgrading SQL server or when deployment is on a machine with different SQL server version - which I cannot affirm that this is 100% true - but i think that there are many issue concerning the CDC that are not fixed by Microsoft.
You can see this from the following links as example:
40
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With
