It is not a joke: SSIS is available for Visual Studio 2019 as a preview. Whoa, hold on. SQL Server 2019 hasn’t been released yet? But there’s already an SSIS 2019? Didn’t we have to wait months after the release of SQL Server 2017 before we had an SSIS version for Visual Studio 2017? Yes, we did, you can read all about there here.
But times have changed apparently. The SSIS team caught up with the rest of the BI tools: SSIS projects are now available from the Visual Studio market place.
Let’s rejoice!
Why is this important? In VS 2017, SSAS and SSRS were already available as extensions, but when you wanted to use SSIS you had to install the full-blown SQL Server Data Tools (which you can install as a shell or into an existing Visual Studio installation). However, to be able to install SSDT, you had to uninstall the SSAS/SSRS extensions. Ugh. Those days are now over. The extensions are also easier to update than SSDT.
The direct consequence is that SSDT, formerly known as SSDT-BI, formerly known as BIDS, will not be available for Visual Studio 2019. An era has ended. Also, SSDT when installed as a shell was free. The full Visual Studio is not. You can use Visual Studio Community though. (Check your licenses people!)
If you’re wondering how you can install the database part of SSDT, these are available as a “workload” during installation:
The SSIS extension is still in preview. Clicking on it in the “Manage Extensions” window will make you download a .exe file of about 400MB. This will install SSIS into Visual Studio.
When the installation is finished, you can connect to your repository or open existing projects. You can now upgrade your SSIS projects to SQL Server 2019 (compatibility still goes back to 2012):
Again, keep in mind it’s currently still in preview. Don’t put this baby in production yet.
All in all, I have to say this was the smoothest install of the Microsoft BI tools in a very long time. Did everything work directly? I had to rebuild a script component, because first it gave me this error:
Cannot communicate with the debug host process. The IDtsHost interface is not registered.
After rebuilding the script and saving the package, it ran successfully. Someone mentioned on Twitter that they experienced issues with deploying SSAS Tabular models. First I got a .NET environment error when I tried to deploy one, but to be honest, I had just run a tool that forcibly removed all remnants of Visual Studio 2015, so maybe that tool had been a bit too enthusiastic? I did a repair of Visual Studio 2019 and then I could deploy Tabular models without issues.
Also: dark theme!
Need to find your variables or your SSIS toolbox? The SSIS menu has been moved to Extensions:
One small bummer: I haven’t found the Power Query Source preview in the toolbox 🙁
I'm hosting a free webinar at MSSQLTips.com at the 19th of December 2024, 6PM UTC.…
The slides and scripts for my session "Tackling the Gaps & Islands Problem with T-SQL…
Sometimes your Microsoft Entra ID account (formerly known as Azure Active Directory) is added as…
In Azure Data Factory (ADF, but also Synapse Pipelines and Fabric Pipelines), you have a…
I wrote a piece of SQL that had some new T-SQL syntax in it: IS…
I'm very excited to announce I've been selected as a speaker for dataMinds Connect 2024,…
View Comments
SSIS was COM not .NET was the reason holding SSIS tooling back I believe?
SSRS
SSAS
SQL DB
Powershell
R
are all .NET VS VSIX extensions
this is good news I hope
ive had too many sessions rebuilding a PC because of MS Tooling
SSMS
VS
SSDT fighting each other
This would usually manifest as not being able to edit C# Script Tasks in SSIS Projects
Usually had to trash everything and start over
TONS of threads all over the innerwebs about that joyfull experience