Visual Studio 2017 - SSDT

Question

Visual Studio 2017 - SSDT

NicHopper

SSCrazy Eights

Points: 9090
More actions
May 2, 2017 at 4:01 am

#321195

Hi,
I'm hoping someone can tell me that I'm mistaken and have missed something but I've installed Visual Studio Professional 2017 (15.1 - 26403.7) Release.
The project template for SSIS packages is missing so I installed SSDT,taking the installer from here https://docs.microsoft.com/en-us/sql/ssdt/download-sql-server-data-tools-ssdt
This installed successfully, however there is still no template for SSIS projects and attempting to open an existing VS2012/2015 SSIS projects results in an error.
So I started to look around and from what I can see VS 2017 does not yet support SSIS projects, is that right? or am I missing something?
I came across this
https://developercommunity.visualstudio.com/content/problem/25001/cannot-open-integration-services-ssis-projects.html
Which to me indicates SSAS and SSRS are supported via extensions but not SSIS. Please say I'm missing something.
Thanks,
Nic
Check out my blog http://www.sqlservercentral.com/articles/Best+Practices/61537/

Viewing 10 posts - 1 through 9 (of 9 total)

You must be logged in to reply to this topic. Login to reply

Thom A SSC Guru Points: 99133 More actions · Answer 1

SSIS has not been released yet for VS 2017. Probably because the latest SQL 2017 CTP version doesn't support SSIS yet either (due in the next month or 2 I think?).

It'll come; my personal guess is when SSIS is available for SQL 2017.

EDIT/P.S. ARGH!!! What made you choose to use the abomination of a font! Mine EYES!!! 😉

Thom~

Excuse my typos and sometimes awful grammar. My fingers work faster than my brain does.
Larnu.uk

Phil Parkin SSC Guru Points: 246985 More actions · Answer 2

NicHopper - Tuesday, May 2, 2017 4:01 AM
Hi,
I'm hoping someone can tell me that I'm mistaken and have missed something but I've installed Visual Studio Professional 2017 (15.1 - 26403.7) Release.
The project template for SSIS packages is missing so I installed SSDT,taking the installer from here https://docs.microsoft.com/en-us/sql/ssdt/download-sql-server-data-tools-ssdt
This installed successfully, however there is still no template for SSIS projects and attempting to open an existing VS2012/2015 SSIS projects results in an error.
So I started to look around and from what I can see VS 2017 does not yet support SSIS projects, is that right? or am I missing something?
I came across this
https://developercommunity.visualstudio.com/content/problem/25001/cannot-open-integration-services-ssis-projects.html
Which to me indicates SSAS and SSRS are supported via extensions but not SSIS. Please say I'm missing something.
Thanks,
Nic

Your suspicions are confirmed on the SSDT 2017 page here.

The absence of evidence is not evidence of absence.
Martin Rees

You can lead a horse to water, but a pencil must be lead.
Stan Laurel

NicHopper SSCrazy Eights Points: 9090 More actions · Answer 3

Thanks for the replies.

As for the font - I thought I'd Jazz it up a bit. 🙂

Check out my blog http://www.sqlservercentral.com/articles/Best+Practices/61537/

pat.lendrum SSC Enthusiast Points: 194 More actions · Answer 4

I have found a SOLUTION!!! This is for 2012 solution/project but should work for all...

1) Install SSDT for VS 2017; I ONLY installed Integration services (NOT Analysis or Reporting Services)

2) Restart Computer after install

3) Open Visual Studio-->Tools-->Extensions and Updates-->ENABLE Integration services extension (NEVER knew this was an extension/option)

4) Restart Visual Studio

5) Open solution. The Project may still error; if it does, right click on the project and rebuild project. It should now open and have the version in parenthesis

Thom A SSC Guru Points: 99133 More actions · Answer 5

pat.lendrum - Tuesday, May 29, 2018 6:19 PM
â€‹I have found a SOLUTION!!! This is for 2012 solution/project but should work for all...
1) Install SSDT for VS 2017; I ONLY installed Integration services (NOT Analysis or Reporting Services)
2) Restart Computer after install
3) Open Visual Studio-->Tools-->Extensions and Updates-->ENABLE Integration services extension (NEVER knew this was an extension/option)
4) Restart Visual Studio
5) Open solution. The Project may still error; if it does, right click on the project and rebuild project. It should now open and have the version in parenthesis

The solution was to wait for the RTM release? Now that it's out, yes SSIS is part of the suite. The OP was using a CTP version of SSDT; which didn't support SSIS at the time.

Thom~

Excuse my typos and sometimes awful grammar. My fingers work faster than my brain does.
Larnu.uk

pat.lendrum SSC Enthusiast Points: 194 More actions · Answer 6

Thom A - Wednesday, May 30, 2018 1:47 AM
pat.lendrum - Tuesday, May 29, 2018 6:19 PM
â€‹I have found a SOLUTION!!! This is for 2012 solution/project but should work for all...
1) Install SSDT for VS 2017; I ONLY installed Integration services (NOT Analysis or Reporting Services)
2) Restart Computer after install
3) Open Visual Studio-->Tools-->Extensions and Updates-->ENABLE Integration services extension (NEVER knew this was an extension/option)
4) Restart Visual Studio
5) Open solution. The Project may still error; if it does, right click on the project and rebuild project. It should now open and have the version in parenthesis
The solution was to wait for the RTM release? Now that it's out, yes SSIS is part of the suite. The OP was using a CTP version of SSDT; which didn't support SSIS at the time.

Yes, however, when you install SSDT for Integration services this is DISABLED by default which throws the SAME error. You need to manually go to tools, enable and then you can do it. WHY the f*** does MSFT disable a component that I am specifically installing?!?! That is where this thread came from and NO answers as to why it still did not open older package version inherently. i should NOT have to enable that SSDT extension after installing (enabled should be the default).

Thom A SSC Guru Points: 99133 More actions · Answer 7

pat.lendrum - Wednesday, May 30, 2018 12:04 PM
Thom A - Wednesday, May 30, 2018 1:47 AM
pat.lendrum - Tuesday, May 29, 2018 6:19 PM
â€‹I have found a SOLUTION!!! This is for 2012 solution/project but should work for all...
1) Install SSDT for VS 2017; I ONLY installed Integration services (NOT Analysis or Reporting Services)
2) Restart Computer after install
3) Open Visual Studio-->Tools-->Extensions and Updates-->ENABLE Integration services extension (NEVER knew this was an extension/option)
4) Restart Visual Studio
5) Open solution. The Project may still error; if it does, right click on the project and rebuild project. It should now open and have the version in parenthesis
The solution was to wait for the RTM release? Now that it's out, yes SSIS is part of the suite. The OP was using a CTP version of SSDT; which didn't support SSIS at the time.
Yes, however, when you install SSDT for Integration services this is DISABLED by default which throws the SAME error. You need to manually go to tools, enable and then you can do it. WHY the f*** does MSFT disable a component that I am specifically installing?!?! That is where this thread came from and NO answers as to why it still did not open older package version inherently. i should NOT have to enable that SSDT extension after installing (enabled should be the default).

SSIS isn't disabled by default... I installed it on 3, machines last month, SSDT comes with all 3 BI tools out the box. Sounds like you didn't tick the right box I'm afraid.

Thom~

Excuse my typos and sometimes awful grammar. My fingers work faster than my brain does.
Larnu.uk

Phil Parkin SSC Guru Points: 246985 More actions · Answer 8

pat.lendrum - Wednesday, May 30, 2018 12:04 PM
Yes, however, when you install SSDT for Integration services this is DISABLED by default which throws the SAME error. You need to manually go to tools, enable and then you can do it. WHY the f*** does MSFT disable a component that I am specifically installing?!?! That is where this thread came from and NO answers as to why it still did not open older package version inherently. i should NOT have to enable that SSDT extension after installing (enabled should be the default).

I did not have to do this when I installed SSDT 2017.

The absence of evidence is not evidence of absence.
Martin Rees

You can lead a horse to water, but a pencil must be lead.
Stan Laurel

pat.lendrum SSC Enthusiast Points: 194 More actions · Answer 9

Phil Parkin - Wednesday, May 30, 2018 1:00 PM
pat.lendrum - Wednesday, May 30, 2018 12:04 PM
Yes, however, when you install SSDT for Integration services this is DISABLED by default which throws the SAME error. You need to manually go to tools, enable and then you can do it. WHY the f*** does MSFT disable a component that I am specifically installing?!?! That is where this thread came from and NO answers as to why it still did not open older package version inherently. i should NOT have to enable that SSDT extension after installing (enabled should be the default).
I did not have to do this when I installed SSDT 2017.

I definitely ticked the 1st box for integration services and left RS and AS unticked...