Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase ««12

Using Checkpoints in SSIS (Part 1) Expand / Collapse
Author
Message
Posted Thursday, February 19, 2009 12:01 PM
Valued Member

Valued MemberValued MemberValued MemberValued MemberValued MemberValued MemberValued MemberValued Member

Group: General Forum Members
Last Login: Thursday, July 07, 2011 6:35 AM
Points: 54, Visits: 96
Hi Aaron

Yeah, I feel kinda stupid now. The object did have an expression set on that property. It was changing the value as soon as the expression was evaluated. I deleted the expression and it appears to have solved the problem. I'm running the package now and its performing exactly as it should. Thank you so much for pointing out the obvious. Sometimes it is the last place we look.

-Gary
Post #660678
Posted Thursday, February 19, 2009 12:01 PM
SSC Rookie

SSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC Rookie

Group: General Forum Members
Last Login: Wednesday, September 11, 2013 2:57 PM
Points: 25, Visits: 143
kgiambas (2/19/2009)
Hmm...I have to disagree with you on this. Though your alternative (assign the CheckpointFileName to a variable and use a package config to change the variable) works just fine, I was able to create a package configuration file that included the CheckpointFileName property and changed it directly.


Yep, you're right. Not sure what I was thinking...possibly going a bit crazy.


Aaron Akin
http://aaronakinsql.wordpress.com || http://www.linkedin.com/in/aaronakin
Post #660679
Posted Thursday, February 19, 2009 12:02 PM
SSC Rookie

SSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC Rookie

Group: General Forum Members
Last Login: Wednesday, September 11, 2013 2:57 PM
Points: 25, Visits: 143
gary.proctor (2/19/2009)
Hi Aaron

Yeah, I feel kinda stupid now. The object did have an expression set on that property. It was changing the value as soon as the expression was evaluated. I deleted the expression and it appears to have solved the problem. I'm running the package now and its performing exactly as it should. Thank you so much for pointing out the obvious. Sometimes it is the last place we look.

-Gary


No problem. Glad you got it working.


Aaron Akin
http://aaronakinsql.wordpress.com || http://www.linkedin.com/in/aaronakin
Post #660685
« Prev Topic | Next Topic »

Add to briefcase ««12

Permissions Expand / Collapse