Menu
I've been using SSIS for quite a while now and it has always bugged me that if you open a SSIS package without it being in a solution, none of the debug or execute options are available in Visual Studio.
On my current project I need to edit some SSIS packages left on our server that are executed from the filesystem. The problem is that the deploy phase does not (and should not) include copying over the solution (.sln) files. If I then go and create a solution inside the default location and add the packages, they get copied over (instead of referencing them directly). This is a problem since some execute other packages that reside on the same directory. So I have to copy the SSIS package over, edit, test, copy it back to the original location. This can get pretty annoying at times, as you can imagine.
So I was wondering, is there any way to execute those packages without including them inside a solution?
I'm using Visual Studio 2008, making SSIS packages for SQL Server 2008.
879
You cannot run a SSIS package (. dtsx) without installing the SQL Server integration Services. The minimum requirements are the SSIS client tools and the DTEXEC utility so you must install the Integration Services shared feature from the SQL Server install media.
To run a package, use one of the following procedures: Open the package that you want to run and then click Start Debugging on the menu bar, or press F5. After the package finishes running, press Shift+F5 to return to design mode. In Solution Explorer, right-click the package, and then click Execute Package.
I agree. This is a total pain. You CAN create a project that contains a simple "wrapper" package with an Execute Package Task that just jumps into to the package you want to debug. When you debug the wrapper it will open your real package and you can debug away. Not ideal but at least its something.
131
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With
