August 26, 2009 at 6:13 am
I have a package that for the most part runs successfully. It has a SQL 2000 database as it's source and a SQL 2005 database as it's destination. It runs a series of sp's with ONE variable as a parameter.
There are a few queries before the push that clears out the old data for that variable. That is were I run into problems. (after running a trace on each database to see what is going on) The initial queries from SQL 2K run just fine, no probs. The delete queries on the other hand are pulling in some variable value for which I have no idea where it is coming from. I don't even recognize it.
The kicker is that I am running with ONE global variable with a default value does anyone have any ideas on this one?
August 26, 2009 at 6:34 am
Is there a default value for the parameter in the stored proc?
What is the default value for the variable in SSIS?
Can you see what the value of the variable is just before executing the stored proc?
I take it there is no local variable as well.
What task are you using to execute the stored proc?
Ells?
😎
August 26, 2009 at 8:52 am
Ells (8/26/2009)
Is there a default value for the parameter in the stored proc?What is the default value for the variable in SSIS?
Can you see what the value of the variable is just before executing the stored proc?
I take it there is no local variable as well.
What task are you using to execute the stored proc?
Ells?
😎
Yes there is a default value, 100 I am running a SQL trace. Is there a way to step into the SSIS package? How do I do that?
August 26, 2009 at 9:04 am
I would edit the package and put in a script task prior to calling the stoired proc. Put a MSG box in the script task. Run the package the message box pops up and wont contiinue till you acknowledge the msgbox.
I take it that the dfault value for the stored proc is not the value being used.
Ells.
:w00t:
August 26, 2009 at 9:17 am
Ells (8/26/2009)
I would edit the package and put in a script task prior to calling the stoired proc. Put a MSG box in the script task. Run the package the message box pops up and wont contiinue till you acknowledge the msgbox.I take it that the dfault value for the stored proc is not the value being used.
Ells.
:w00t:
How is that going to help? Is there not a way to step into the package?
August 26, 2009 at 9:54 am
yep. Put breakpoints in
Ells.
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply