February 11, 2016 at 5:47 am
I'm now upgrading SSIS packages from 2008 to 2012 and am a little confused. I thought Visual Studio was taking over from BIDS, but when I try to open my projects in VS2012, it complains about not recognizing the project type.
After a little googling, I found a comment about SQL Data Tools. I'm opening up my first project in there and so far everything seems to be fine. But still... what's going on? Why won't VS 2012 open SSIS solutions / projects? Is Data Tools just an updated BIDS?
February 11, 2016 at 6:06 am
Yeah, this gets fun...
SSDT is the "upgraded" BIDS in 2012. In 2014, SSDT is now a completely separate download, either as a stand-alone (I hope as I just downloaded it at home) tool, or as a plug-in for VS.
I think to get VS to open SSIS packages, you'd need to get the SSDT plug-in for it. Here's the link I'm thinking of: https://msdn.microsoft.com/en-us/library/mt204009.aspx
February 11, 2016 at 6:25 am
jasona.work (2/11/2016)
Yeah, this gets fun...SSDT is the "upgraded" BIDS in 2012. In 2014, SSDT is now a completely separate download, either as a stand-alone (I hope as I just downloaded it at home) tool, or as a plug-in for VS.
I think to get VS to open SSIS packages, you'd need to get the SSDT plug-in for it. Here's the link I'm thinking of: https://msdn.microsoft.com/en-us/library/mt204009.aspx
Thanks, Jason. I'll check that link out.
Though given that VS 2012 keeps crashing on me when I try to close a solution (even non-SSIS) or change to a new one the way I can in BIDS and VS 2010, I might just stick to SSDT.
February 11, 2016 at 6:35 am
I actually wrote this up in a few blog post here[/url] and here[/url].
The link provided in the previous post is the link that takes you to the latest release of SSDT, but you can go down to this section in on that page, it will take you to the VS 2013 download for SSDT and SSDT-BI. At this time there is no SSDT-BI released for VS 2015, you will have to stick with VS 2013 or at least I would suggest that version instead of VS 2012.
Shawn Melton
Twitter: @wsmelton
Blog: wsmelton.github.com
Github: wsmelton
February 11, 2016 at 9:04 am
Shawn Melton (2/11/2016)
at least I would suggest that version instead of VS 2012.
You say that as if I have a choice about what version of VS I can use at work. :w00t:
Unfortunately, putting non-approved software on corporate machines is a firing offense. Even if it does help us do our jobs. Exceptions can be made, but paperwork must be filled out, etc.
February 11, 2016 at 11:17 am
Brandie Tarvin (2/11/2016)
Shawn Melton (2/11/2016)
at least I would suggest that version instead of VS 2012.You say that as if I have a choice about what version of VS I can use at work. :w00t:
Unfortunately, putting non-approved software on corporate machines is a firing offense. Even if it does help us do our jobs. Exceptions can be made, but paperwork must be filled out, etc.
Been there, done that...
It only took them about 3 months to get all the paperwork and approvals and testing and retesting done for me to get SSMS 2012 on my workstation...
At least you can do 90% of what you need with SSMS 2008R2 to SQL 2012 and the other 10% would drive Brent Ozar bonkers (running SSMS etc on one of the servers.)
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply