I suggested a separate job if DataStage was going to be doing the deletes or otherwise fundamental in controlling the action. If all you're going to end up doing is calling a stored procedure, you can just do that "before SQL" I your existing job.
-craig
"You can never have too many knives" -- Logan Nine Fingers
@Craig
Actually I get to see probably first two lines only.
From that I assumed what your post is
I know I have to renew my membership, but the money has to be approved by our client .
And our client does not think what we developers think about this website.
chandra.shekhar@tcs.com wrote:@Craig
Actually I get to see probably first two lines only.
From that I assumed what your post is
Not to pile on or anything but that doesn't really work. And is doubly disappointing when we take extra time and effort to help out specifically because of someone's Premium status. [sigh]
-craig
"You can never have too many knives" -- Logan Nine Fingers