integration services projects in VS 2017 Community.

Question

_{Tuesday, October 17, 2017 7:53 PM}

I was informed in the SQL Server forum that VS 2017 Community edition does not support authoring Integration Service projects. However, after installing the latest version of SQ Server Data Tools  I am able to create an Integration Services Project (the project template does exist) and can add such tasks as connecting to an Access database. However, after saving the project and then trying to open it, the project name is annotated as 'Incompatible'. Related Log information infers a project migration issue.

This does not make sense to me; i.e., allow the creation of a project but not allow it to be opened. Can anyone help me understand what is going on. (Other VS project types appear to open fine).

jperry

All replies (8)

_{Wednesday, October 18, 2017 9:09 AM}

Hi jperry,

Welcome to the MSDN forum.

Please try to create a new Integration Services project and save it, then reopen it to check if this issue occurs or not. I tried to create a new Integration Services project in my VS 2017 15.4.0 and drag one Data Flow Task into Package.dtsx[Design], save it then reopen VS to open this solution again, it works fine.

How did install the SSDT, through VS 2017 installer or the standalone SSDT installer? Please check the installation doc: Download SQL Server Data Tools (SSDT) and you can download the SSDT installer, run it to check the checkbox of SSTS already checked for VS 2017 or choose ‘Repair’ to repair SSDT. Make sure your VS 2017 is up-to-date, you can re-run the VS 2017 installer as administrator, and if there has ‘Update’ please upgrade it to have a try.

Meanwhile, please have a look at the known issues of SSDT for Visual Studio 2017 (15.3.0 preview), we can report issues at the SSDT Connect Feedback site to the SSDT product Team.

Best regards,

Sara

MSDN Community Support Please remember to click "Mark as Answer" the responses that resolved your issue, and to click "Unmark as Answer" if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to MSDN Support, feel free to contact [email protected]

_{Thursday, October 19, 2017 6:05 PM}

Sara, thanks for the response. Did you use the Community Edition of VS 2017 in your test?

I originally downloaded the SSDT from the link you provided above. (On each of my 2 computers). The only trouble I had initially was getting rid of the 64 bit version of Office 365. I final accomplished this task and was able to install the 32 bit version of the Access Database Engine. From that oint on I have had the "Project Incompatibility" problem.

I did not know that it was possible to install SSDT using the VS 2015 Community Installer, so I uninstalled the version on my computer that was install using the link you recommended, and modified my installation of VS 2015 by adding the SSDT component. I then tried to create a new project using VS 2015 but the only SQL Server related template that is available is for a SQL Server Database Project. There are no templates for  "Integration Services" or  "Analysis Services" projects.

So I have tentatively concluded that there are 2 different SSDT installs, 1 from the standalone SSDT Installer and one from the VS 2017 Installer. And, it appears one of these VS 2017 Installer) provides the template for a SQL Server database project (from VS 2017 installer I believe), and the standalone SSDT installer provides for Integration Services and Analysis Services projects. 

So I am a bit unsure about my best next step. I plan to uninstall SQL Server 2017 Dev, VS 2017 Community, and both instances of the SSDT (If I can figure out how to do both, there is only one instance displayed in "Programs and Features" on my computer. Then will reinstall all of them, using the standalone installer for SSDT. Do you agree with that plan.

And can you confirm that VS 2017 Community Edition does allow authoring and saving Integration Services projects. 

(I am adding this edit to say that I was just ending a reply to this post saying VS 2017 is now working fine with Integration Services projects, when my reply just "disappeared". I cannot find it and if I click "Reply" again to this post, I am told I have a reply open and must close it. But I cannot find it to close it. Help anyone?)

jperry

_{Friday, October 20, 2017 1:46 AM}

Hi jperry,

Thank you for your update.

*>>And can you confirm that VS 2017 Community Edition does allow authoring and saving Integration Services projects. *

Yes, I am using the VS community 2017 15.4.0 version, please check this video

>>I am adding this edit to say that I was just ending a reply to this post saying VS 2017 is now working fine with Integration Services projects

Do you means your issue is solved? If so, please mark your reply as answer and that will help other community members and we can also close this thread, thank you for your understanding. Meanwhile, I found you have already created a new thread for your another issue, usually we discuss one question in one thread and that can help us to trace and research.

>>when my reply just "disappeared". I cannot find it and if I click "Reply" again to this post, I am told I have a reply open and must close it. But I cannot find it to close it. Help anyone?

Thank you for your feedback, I suppose something just refresh or browser cache and affect it, sorry for this inconvenience and usually we need to refresh the current page and add a reply again.

If you have any other issues about VS IDE, please feel free to let us know.

Best regards,

Sara

MSDN Community Support Please remember to click "Mark as Answer" the responses that resolved your issue, and to click "Unmark as Answer" if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to MSDN Support, feel free to contact [email protected]

_{Wednesday, January 31, 2018 6:51 PM}

This is just unfair. Your community edition is more powerful than ours:-).

(Image here not allowed by Microsoft

The community edition does not include the Business Intelligence project types, even after SSDT is installed. Even though both are free, SSDT installs a separate instance of Visual Studio 2017.

I found that the project templates for the Reporting Service and the Analysis Service at Microsoft's Visual Studio Marketplace. After installing both, the community edition project dialog box looks like this:

(Image here not allowed by Microsoft)

But I cannot find a project template for SSIS on the Visual Studio Marketplace. I ran the Visual Studio installer, selected "Modify". I looked under "Workload" and "Individual Components", and I could not find it anywhere. The SSRS and SSAS project templates that I installed show up as "Uncategorized". 

Could you explain how you got all three templates for Business Intelligence installed in the community edition of Visual Studio 2017?

Thank you.

_{Wednesday, January 31, 2018 7:28 PM}

Hi Sara,

BTW the version is "Visual Studio Community 2017 — 15.5.5".

I have SSDT installed. But that does not include Business Intelligence. Perhaps that is an error in Microsoft's installer?

Thank you.

X. Tan

_{Wednesday, January 31, 2018 9:30 PM}

I just figured this out:

1. Download the SSDT VS 2017 installer.

2. Run SSDTSetup with the parameters "/layout <download folder path>"

3. Run each .vsix file to update the VS 2017 community edition.

Now the VS 2017 Community Edition has all of the BI project types.

_{Thursday, February 1, 2018 1:51 AM}

Hi X. Tan,

So glad to hear that your issue is solved and thank you for your sharing.

Best regards,

Sara

MSDN Community Support Please remember to click "Mark as Answer" the responses that resolved your issue, and to click "Unmark as Answer" if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to MSDN Support, feel free to contact [email protected]

_{Sunday, February 4, 2018 1:16 AM}

Thank you Sara.

What I then found out was that the order of installations matter, too. If the community edition is installed first, then when you install SSDT you actually get a choice to install a new instance of Visual Studio, or install into the community edition. If you install the SSDT version first, the community edition would not give you an option to combine itself into the existing SSDT installation.

So installing the community edition first, and then the SSDT edition second, with the choice of updating the existing community edition, seems to be the best approach.