Posted: Mon May 21, 2007 9:55 pm
If you know, whether the incoming row is Insert or update, then for the Insert Target Stage, Set target action as "Insert New Rows only" and for the Update Target Stage , set the target action as "Update Existing rows only". Because the target action "Insert or Update" will definetly reduce the performance.
And if you are doing the lookup only for getting the Created Timestamp, then the lookup is not necessary. Make the Created Timestamp as a Nullable field and dont pass any value to the Created Timestamp from the Job. Instead write an After Sql to update the Created Timestamp, some thing like
In this case, your target action should be "Insert or Update", as you are not doing the lookup to determine , whether the Incoming row is Update or Insert.
And if you are doing the lookup only for getting the Created Timestamp, then the lookup is not necessary. Make the Created Timestamp as a Nullable field and dont pass any value to the Created Timestamp from the Job. Instead write an After Sql to update the Created Timestamp, some thing like
Code: Select all
Update YOURTABLE Set Created_TimeStamp = %DateTimeIn(#DSJobStartTimestamp#) where Created_TimeStamp IS NULL