DSXchange

You dont need admin rights to unlock jobs

Hey narasimha, are you preety sure of that?
have you tried that using a login without admin rights?

I somehow remember doing it and it didn't work, just confirm.

No, it won't have any problems.

Only thing that you need to make sure is you map the columns to compatible datatype columns from source to target.

Also if you have single job with "upsert" option (update + insert) you may end up loosing processing time to check whether it is update or insert. Therefore I will sugesst you to go for two links instead of one. That is again based on the case by case. Say for e.g., if you are bringing th...

loveojha2 wrote:Do get rid of such a dataloss case, make sure your job aborts even when it generates a warning, if that's what you want.

Just a typo

To get rid of such a dataloss case, make sure your job aborts even when it generates a warning, if that's what you want.

Why do you want to go the user defined sql way.

Please provide the sql then you are trying to accomoplish, may be we can think of an alternate solution.

Do get rid of such a dataloss case, make sure your job aborts even when it generates a warning, if that's what you want.

ray.wurlod wrote:It's called Runtime Column Propagation and you get it in parallel jobs. ...

Runtime Column Propagation, meaning it happens at the runtime only or there are methods of doing it with the job metadata also.

You can unlock the jobs using the tool DS.TOOLS . You need to execute it from within the command window of the Administrator. Plus you would need admin rights only then you can unlock it. Just follow the instructons that come when you execute it, I am sure you'll be able to find it, since the messag...

ie only keys which end with X in input should not have that X in output

Using Matches operator or Colname[Len(Colname)]='X' could be a more suitable for this, before chopping the last X and use Left operator for removing the training

Or left outer joins doing two times,

Something like
if you don't want to use the link merge stage.

How many jobs were running at that time on the server?

Your server is overloaded and it can't serve the new request for now.

Try rerunning the job and see you get the same error again or not. If yes, then run your job when your server is relatively idle.

Is it paramterized job, are you using any parameters (may be different values could be a cause.)


How it is showing in the job after the complete job run.(how many rows selected, written to the links).

How about concatenating the key columns and passing the concatenated value for the sequence generation.

Something like using the

I don't think that it is possible to do it without client (not sure what is your definition of client?)
What you exactly want to do? Plz Explain.

Two options: 1. Use parameterized File Names within the server job and run it from a sequence job providing the value for the parameter. You can include Loop activity to do it for multiple times. File Names can be read from within a Routine. 2. Use parameterized file names and create the job as mult...