Breakpoints in MULTIPLE Script Tasks
-
SSIS Script Task debugging has always been a pain for me, particularly if I have a package with many Script Tasks. I'd set a breakpoint in one script, only to find that it caused the debugger to stop on a different Script Task! I scoured the web and found no solution to this problem, until now...
I'm using the following approach, and it seems to be working. SQLServerCentral community, see if you can poke holes in it!
The key seems to be, for each Script Task in a package, to make sure that the class names are unique across the whole package. I accomplish this by renaming the "ScriptMain" references to "ScriptMain1" in the first Script Task, "ScriptMain2" in the second Script Task, and so on. When renaming "ScriptMain", you have to do it three places: The "EntryPoint" setting in the Script Task Editor dialog, the Project Explorer pane of the VB editor, and the code pane of the VB editor. Once they're all renamed, breakpoints can be added at will, and the SSIS debugger doesn't seem to get all the different Script Task's breakpoints confused.
I hope others can confirm that this works for them, and I hope it helps the SSIS developer community at large!
-
This sounds like a nice workaround. However this situation looks like a bug to me. Have you tried reporting this problem to Microsoft?
---
SSIS Tasks Components Scripts Services | http://www.cozyroc.com/
-
I haven't reported it myself, but I remember seeing it on Microsoft Connect, where MS stated that they were addressing it in SQL 2008 only.
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply