I have an existing SSIS project that I am trying to debug.
I can see the Control Flow tab correctly but there is no Edit breakpoints... option on the context menu, which appears when you right-click on Control Flow tasks such as Execute SQL Task, Script task etc.
Solution explorer does not have anything related to debugging either and only Deploy option is visible. Debugging from the main menu results in Canceled by user error almost immediately.
Would you know how this can possibly be the case and how to remedy it?
*.dtsx files are on a machine that I remotely connect to. I run Visual studio under another user and the server is on yet another machine. Could this possibly affect the contents of the context menus?
Environment information:
- Windows XP
- VS 2008 Pro
- BIDS
- MS SQL Server
Prior to the SQL Server 2012 release of SSIS, you cannot debug script components (those in a data flow). The general approach I’ve seen and used it to emit the information I want to use to debug via message boxes or throw information events and then log those out.
A script task (control flow) should provide you the ability to set breakpoints however you need them.
There’s nothing to “debug” in an
Execute SQL Task. You can breakpoint the usual stuff Pre/Post Execute but no way I’m aware of to debug into SQL Server from there.The only other thought I have is that you might be just “opening” an SSIS package in Visual Studio/BIDS. While it allows you to view a package, you can’t do anything with it unless the editor has an SSIS project opened.
Package without a project, notice greyed out Play button
Package edited within a project, green play arrow