 | |
Re: How to force a SSIS package step to fail?
microsoft.public.sqlserver.dts microsoft.public.sqlserver.dts
 |
| | Thread Tools | Display Modes |
#21
 
| |||
| |||
|
Re: How to force a SSIS package step to fail? -
03-13-2008
, 10:23 AM
|
Hi J, It took me a while, but I finally figured it out..:-). On the Parameter Mapping tab in the "Execute SQL Task" Editor, I have to define a Parameter Size to my string. For some reason, this only shows "Paramter..." when I open the Editor, so it took some time until I made the window a little bit bigger and finally realized that the full name was "Parameter Size"...:-(. When entering an apropriate value, it worked. Regards Steen jhofm... (AT) googlemail (DOT) com wrote: Hi Steen, There is no concept of "Length" in a package string variable - it is as long as you make it. Try deleting and re-creating the ExecuteSQL task. *Sometimes when you change a stored proc the metadata in SSIS doesn't update correctly. You might also consider changing your SP into a function if all it's doing is returning a value... I think using expressions is a better method of controling application flow than Succ/Fail/Comp ... what happens if your task were to actually fail? Good luck! J- Hide quoted text - - Show quoted text - |
I assumed you were just returning the value as a resultset (single
row, single column).
Good luck!
J
#22
| |||
| |||
|
|
Hi J, It took me a while, but I finally figured it out..:-). On the Parameter Mapping tab in the "Execute SQL Task" Editor, I have to define a Parameter Size to my string. For some reason, this only shows "Paramter..." when I open the Editor, so it took some time until I made the window a little bit bigger and finally realized that the full name was "Parameter Size"...:-(. When entering an apropriate value, it worked. Regards Steen jhofm... (AT) googlemail (DOT) com wrote: Hi Steen, There is no concept of "Length" in a package string variable - it is as long as you make it. Try deleting and re-creating the ExecuteSQL task. *Sometimes when you change a stored proc the metadata in SSIS doesn't update correctly. You might also consider changing your SP into a function if all it's doing is returning a value... I think using expressions is a better method of controling application flow than Succ/Fail/Comp ... what happens if your task were to actually fail? Good luck! J- Hide quoted text - - Show quoted text - |
I assumed you were just returning the value as a resultset (single
row, single column).
Good luck!
J
#23
| |||
| |||
|
|
Hi J, It took me a while, but I finally figured it out..:-). On the Parameter Mapping tab in the "Execute SQL Task" Editor, I have to define a Parameter Size to my string. For some reason, this only shows "Paramter..." when I open the Editor, so it took some time until I made the window a little bit bigger and finally realized that the full name was "Parameter Size"...:-(. When entering an apropriate value, it worked. Regards Steen jhofm... (AT) googlemail (DOT) com wrote: Hi Steen, There is no concept of "Length" in a package string variable - it is as long as you make it. Try deleting and re-creating the ExecuteSQL task. *Sometimes when you change a stored proc the metadata in SSIS doesn't update correctly. You might also consider changing your SP into a function if all it's doing is returning a value... I think using expressions is a better method of controling application flow than Succ/Fail/Comp ... what happens if your task were to actually fail? Good luck! J- Hide quoted text - - Show quoted text - |
I assumed you were just returning the value as a resultset (single
row, single column).
Good luck!
J
#24
| |||
| |||
|
|
Hi J, It took me a while, but I finally figured it out..:-). On the Parameter Mapping tab in the "Execute SQL Task" Editor, I have to define a Parameter Size to my string. For some reason, this only shows "Paramter..." when I open the Editor, so it took some time until I made the window a little bit bigger and finally realized that the full name was "Parameter Size"...:-(. When entering an apropriate value, it worked. Regards Steen jhofm... (AT) googlemail (DOT) com wrote: Hi Steen, There is no concept of "Length" in a package string variable - it is as long as you make it. Try deleting and re-creating the ExecuteSQL task. *Sometimes when you change a stored proc the metadata in SSIS doesn't update correctly. You might also consider changing your SP into a function if all it's doing is returning a value... I think using expressions is a better method of controling application flow than Succ/Fail/Comp ... what happens if your task were to actually fail? Good luck! J- Hide quoted text - - Show quoted text - |
I assumed you were just returning the value as a resultset (single
row, single column).
Good luck!
J
|
« Previous Thread
|
Next Thread »
| Thread Tools | |
| Display Modes | |
Linear Mode
| |
Powered by vBulletin Version 3.5.3
Copyright ©2000 - 2012, Jelsoft Enterprises Ltd.
Copyright ©2000 - 2012, Jelsoft Enterprises Ltd.