Is there a way to execute SSIS packages inside Visual Studio without participating in a solution?

Question

I've been using SSIS for a long time, and I've always heard that if you open the SSIS package without solving it, none of the debug or execute options are available in Visual Studio.

In my current project, I need to edit some SSIS packages left on our server that run from the file system. The problem is that the deployment phase does not include (and should not) copy over solution files (.sln). If I then go over and create a solution inside the default location and add packages, they will be copied (instead of referencing them directly). This is a problem because some of them run other packages that are in the same directory. Therefore, I need to copy the SSIS package on top, modify, test, copy it back to its original location. This can be quite annoying, as you might imagine.

So, I was wondering if there is a way to execute these packages without including them in the solution?

I am using Visual Studio 2008, creating SSIS packages for SQL Server 2008.

Answer 1

I agree. This is a complete pain. You can create a project that contains a simple wrapper package with an Execute Package Task that simply goes into the package you want to debug. When you debug a shell, it will open your real package and you can debug it. Not perfect, but at least something.

Answer 2

No, you cannot do this inside VS and use the SSIS debugger without a project. Of course, you can run it outside of VS using DTEXEC.EXE.

(technically, the package should be part of the -.dtproj file project, VS creates a solution if necessary, so you can skip the .sln files)

Answer 3

You can also add xml for the package to the .dtproj file. This will allow you to open and run it as part of your package.

Answer 4

There are server-side methods for executing a package without using SQL Server Business Intelligence Development Studio.

1. Run the SSIS package using the command line utility (DTEXEC.EXE):

Use the command line utility and navigate to the path to the file where your SSIS package is stored. It is possible that DTEXEC.EXE is on a different path on your computer, so check this out before.

Example: C: \ Program Files \ Microsoft SQL Server \ 100 \ DTS \ Binn> DTEXEC.EXE / F "C: \ Packages \ SSISPackageToRun.dtsx"

2. Run the SSIS package using the Execute Package Utility (DTEXECUI.EXE):

Run the Execute Package Utility and select the package that you want to run from the file system. Click the Run button to start the package.

You can also go directly to the package in the file system with the right mouse button and select open (or open it using the Execute Package Utility, depending on the settings) and Run the Batch Utility (DTEXECUI.EXE). Click the Run button to start the package.

3. Running the SSIS package using Microsoft SQL Management Studio:

Find your package in the Object Browser with the right mouse button and select Run Package.

4. Running the SSIS package using the SQL Server Agent job:

Create an SQL job and run the package inside the job step. After that, run the sql job that includes your package.

Here is a summary of good solutions: https://www.mssqltips.com/sqlservertip/1775/different-ways-to-execute-a-sql-server-ssis-package/