Is it true that breakpoints won't work in a script component
I just wrote a script source component to reorder the columns in incoming CSV's based on the column names in the first row.
I set some break points to debug, but they get ignored every time I try to run it. My "precompile" flag is set to false per some earlier posts, but that doesn't seem to affect the issue.
We don't support breakpoints in script data flowcomponent in this release.
The script task breakpoints should work, except when the package is executed using 64-bit runtime on x64 machines.
Jamie - are you using CTP 16 I remember in some older builds the script task breakpoints did not work if the PreCompile property of the task was true. I think it is fixed in CTP 16 (but it could be after CTP 16 - for RTM, not sure).
Hi Michael, Yeah, I am using Sept CTP/IDW 16 and I do have PreCompile=TRUE.
The package is at the office and I am currently at home so I'll check this out (i.e. set PreCompile=FALSE) on monday.
I found that if you are in debug at a breakpoint on a looping bit of code. If you press F5 the code then continues and doesn't break on the break point again, even though the statement with the breakpoint is executed again.
I thought F5 ran the code and if a breakpoint is found it should stop
We don't support breakpoints in script data flowcomponent in this release.
The script task breakpoints should work, except when the package is executed using 64-bit runtime on x64 machines.
Jamie - are you using CTP 16 I remember in some older builds the script task breakpoints did not work if the PreCompile property of the task was true. I think it is fixed in CTP 16 (but it could be after CTP 16 - for RTM, not sure).
Breakpoint doesn't work
Sm00ches
You will need to put some logging information in your script component see my post http://www.sqljunkies.com/WebLog/simons/archive/2005/08/03/SSIS_Script_Component_Debugging.aspx
Thomas Phillip
cdolphin88
I just wrote a script source component to reorder the columns in incoming CSV's based on the column names in the first row.
I set some break points to debug, but they get ignored every time I try to run it. My "precompile" flag is set to false per some earlier posts, but that doesn't seem to affect the issue.
hommer
Hi Michael,
Yeah, I am using Sept CTP/IDW 16 and I do have PreCompile=TRUE.
The package is at the office and I am currently at home so I'll check this out (i.e. set PreCompile=FALSE) on monday.
-Jamie
Thinh
I thought F5 ran the code and if a breakpoint is found it should stop
kaku Mohanty
The script task breakpoints should work, except when the package is executed using 64-bit runtime on x64 machines.
Jamie - are you using CTP 16 I remember in some older builds the script task breakpoints did not work if the PreCompile property of the task was true. I think it is fixed in CTP 16 (but it could be after CTP 16 - for RTM, not sure).
Studioj
PareshC
Nah, I know this has worked in the past and I've read posts today from people that have had it working.
-Jamie