Do I need Visual Studio 2019 installed on a server in order to run SSIS packages from the same server ? The SSIS packages were upgraded in Visual Studio 2019.

Question

I have an SSIS project that was built using Visual Studio 2012 Shell and SSDT from a SQL server install. I want to upgrade the SSIS project using Visual Studio 2019.

Is SSDT available with SQL server 2019 install? Is Visual Studio Shell no longer available with VS 2019?

Either way, I am able to upgrade the SSIS packages using the Integrated services extensions and SSDT in Visual Studio 2019 and compile the project.

We need to be able to run these upgraded VS 2019 SSIS packages using powershell scripts from a server. My question is: Do I also need Visual Studio 2019 installed on the same server where the packages are being run in order for the packages to run successfully? The server in question does have Integrated services installed (from the SQL server 2019 install).

If I don't need Visual Studio 2019 install on this server in order for the SSIS packages to run, is this something you would recommend? What is the best practice when running SSIS packages (created in a SSIS Project) on multiple servers in multiple environments?

Also, I couldn't enter a proper tag for this question.

Answer 1

SSDT is no longer needed. To build SSIS packages you should install Visual Studio (you can use Community if you don't have a license for a full version). NOTE: You must currently use VS 2019, not the newer VS 2022 as SSIS is not yet supported on the newer version. After you install VS 2019 then install the SQL Server Integration Services Projects extension.

You do not need to have VS installed on the SQL machine. SSIS runs on your SSIS server (generally your SQL server) and therefore you just need to deploy the package to that server. It is not recommended that you install development tools on a production server under any circumstances. You can debug your SSIS package locally on your dev machine in VS.

Do be aware that SSIS is tied to the version of SQL you'll run it against so ensure that your SSIS packages are targeting the version of SQL you need. If you need an older version of SSIS then you might need to also run an older version of SSDT as SSDT is tied to specific SSIS versions.

Answer 2

Thank you very much!