June 29, 2017 at 9:13 am
I am currently working with SQL Server 2016. However, I created and run an SSIS package (integration services project) in Visual Studio 2012. The project is fairly simple in that it creates a SQL table and generates a series of text files. While the package appears to run fine in Visual Studio 2012, are there technical concerns with using this older package with SQL Server 2016?
June 29, 2017 at 9:26 am
SQL Server 2016 requires SSDT 2016 to be able to deploy SSIS, SSRS, SSAS projects. Unless I'm mistaken, SSDT 2016 is only supported in VS 2015 onwards. I would imagine you will be unable to therefore deploy to a 2016 instance (or if you do, I would not say it it will (always) work as expected).
If you are using SQL Server 2016, use VS 2015 with SSDT 2016. SSDT was split out (or is currently) in VS 2017 and only SSRS and SSAS are currently supported.
Thom~
Excuse my typos and sometimes awful grammar. My fingers work faster than my brain does.
Larnu.uk
June 29, 2017 at 11:04 am
Thom - Thanks very much for your prompt response to my question. I will take your advice and get the new version of Visual Studio.
July 10, 2017 at 9:31 pm
Agreed.
Avoid any unexpected issues with package deployment by sticking with the latest version of SSDT
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply