Preventing projects from deploying when debugging a SSIS package

This is a quick tip to help quickly solve a problem I run into sometimes, and now that I am writing a blog about it, will be able to solve it in no time (a big benefit of blogging is to never have to try to remember a solution to a problem you have had before…just search your blog!):

In Visual Studio, I have a solution that encompasses three projects: a SSIS project, a SSAS project, and a SSRS project.  Say I’m working on the SSAS project in this solution and it’s in an incomplete state.  Then I get an email that there is a problem with a SSIS package, and that package is in the same solution under the SSIS project.  So I go to that package and hit debug, and the SSIS package does not run because it tried to deploy the SSAS project and there were errors.  Why does it try to deploy the SSAS project when I’m just trying to run a SSIS package?

The problem is your solution is set up to build and/or deploy ALL the projects when you just want to debug one project.  The solution is simple – right click the solution, select “Configuration Manager…”, and uncheck the “Build” and “Deploy” boxes:

Now, when you debug the SSIS package, the SSAS project and any other packages will be ignored.

About James Serra

James is a big data and data warehousing solution architect at Microsoft. Previously he was an independent consultant working as a Data Warehouse/Business Intelligence architect and developer. He is a prior SQL Server MVP with over 25 years of IT experience.
This entry was posted in Quick Tip, SQLServerPedia Syndication, SSIS, Visual Studio 2008. Bookmark the permalink.

Comments are closed.