April 18, 2016 at 9:09 am
I've been doing some limited testing and it seems that packages developed in VS2015 can be successfully deployed and executed in SQL Server 2014.
However, it would seem that the 'recommended' version of VS for SQL Server 2014 is SSDT 2013 (see here, for example).
As we are going through an upgrade process at the moment, we would rather jump straight to VS2015, assuming we're doing something which is supported.
Does anyone have any insights to offer here?
If you haven't even tried to resolve your issue, please don't expect the hard-working volunteers here to waste their time providing links to answers which you could easily have found yourself.
April 18, 2016 at 10:13 am
No insight info but have been playing around with 2014 as target server and so far no problem. Note that I've not used any version specific libraries in script components etc., only relatively simple stuff. Next step of course is to start with 2016.
😎
April 18, 2016 at 10:22 am
Eirikur Eiriksson (4/18/2016)
No insight info but have been playing around with 2014 as target server and so far no problem. Note that I've not used any version specific libraries in script components etc., only relatively simple stuff. Next step of course is to start with 2016.😎
Indeed. And as we're at RC3 now, surely it will be RTM soon.
If you haven't even tried to resolve your issue, please don't expect the hard-working volunteers here to waste their time providing links to answers which you could easily have found yourself.
April 18, 2016 at 10:49 am
Phil Parkin (4/18/2016)
Eirikur Eiriksson (4/18/2016)
No insight info but have been playing around with 2014 as target server and so far no problem. Note that I've not used any version specific libraries in script components etc., only relatively simple stuff. Next step of course is to start with 2016.😎
Indeed. And as we're at RC3 now, surely it will be RTM soon.
Hoping to skip 2014 and go straight to 2016 where possible, from what I've tested it's the best one yet.
😎
April 18, 2016 at 10:55 am
Eirikur Eiriksson (4/18/2016)
Phil Parkin (4/18/2016)
Eirikur Eiriksson (4/18/2016)
No insight info but have been playing around with 2014 as target server and so far no problem. Note that I've not used any version specific libraries in script components etc., only relatively simple stuff. Next step of course is to start with 2016.😎
Indeed. And as we're at RC3 now, surely it will be RTM soon.
Hoping to skip 2014 and go straight to 2016 where possible, from what I've tested it's the best one yet.
😎
Thanks, Eirikur. That is also an option for us, so your feedback is useful.
If you haven't even tried to resolve your issue, please don't expect the hard-working volunteers here to waste their time providing links to answers which you could easily have found yourself.
April 18, 2016 at 11:11 am
Phil Parkin (4/18/2016)
Eirikur Eiriksson (4/18/2016)
Phil Parkin (4/18/2016)
Eirikur Eiriksson (4/18/2016)
No insight info but have been playing around with 2014 as target server and so far no problem. Note that I've not used any version specific libraries in script components etc., only relatively simple stuff. Next step of course is to start with 2016.😎
Indeed. And as we're at RC3 now, surely it will be RTM soon.
Hoping to skip 2014 and go straight to 2016 where possible, from what I've tested it's the best one yet.
😎
Thanks, Eirikur. That is also an option for us, so your feedback is useful.
You are welcome Phil, will feedback on this thread if I come across any issues on the SSIS front
😎
January 5, 2017 at 11:00 am
Has anyone run into any issues on this front? I am deploying a package that I recently opened and modified in VS 2015 to SQL 2014 SP2 (12.0.5000) and it is failing with "The version of [OLE DB Destination name] is not compatible with this version of the DataFlow." for each data flow destination. Has anyone experienced this? The target version of the project is set to SQL Server 2014 and I've tried changing some 32-bit/64-bit runtime settings as well. Some responses I've seen on this say that they aren't compatible, but those are a year or two old.
Update after further testing: re-creating the data flow task from scratch still results in the "The version of .. is not compatible with this version of the DataFlow" error. Another item of note is that this is using the package deployment model (as it was in VS 2013), deployed to the SSIS Package Store via 'Save Copy of Package As...'. Would moving the package to a different project and deploying it to the SSIS Catalog using the project deployment model work? Our current project has a lot of packages in it, which is why we don't currently utilize project deployment. If that doesn't work, it's looking like it's back to VS 2013 for us until we can upgrade to SQL 2016.
January 6, 2017 at 6:39 am
We've built and deployed a number of packages in VS2015, targeted to SSIS 2014. All seems to be working fine so far. They are all pretty simple ones though, mostly just pushing data from here to there.
Only issue we've encountered so far is with script tasks, but that was when we accidentally targeted a package to 2016 and deployed it to 2014...it didn't like that, script tasks errored out. Retargeting to 2014 and redeploying fixed it. Lesson: be careful when creating a new package, it looks like it defaults to targeting to 2016, make sure to check/change it.
January 7, 2017 at 12:16 am
Thanks for responding - just curious, were you using project deployment to the SSIS catalog or package deployment to the SSIS package store? Has anyone been successful with the latter?
Viewing 9 posts - 1 through 8 (of 8 total)
You must be logged in to reply to this topic. Login to reply