DSXchange

You tune the query not the database, and that's a conversation you'd need to have with your DBA or someone else onsite with you.

How much "extra time"? Enough to make this search for another way worth your time? I sincerely doubt it.

Excellent! Please mark your post as Resolved using the button at the top of the page.

That's what I was afraid of and it should have been the very first thing you mentioned. Start with what Ray asked you to do.

Two nodes = two sets of stats. Since the nodes run in parallel, why would you expect all of the stats to sum up to the total run time? Constrain it to one node and see if the stats make more sense that way.

You would have to script the 'for' loop and the run the script in the ESS. Did you not try the 'find' command?

The connector stages are new and tend to be a little buggy, best to check with your official support provider.

Reserved word issue, I would think. Change the parameter name to something less generic, like 'run_date' or something more appropriate to its function.

:lol: I was wondering when we would get around to that little fact. Everyone got so caught up in the UNIX syntax issues from the original suggestions (and all the struggles there) that the fact that they were Windows client commands was never mentioned. There is limited server-side import functional...

Right, an exact search for "DSSetUserStatus" will turn up many conversations on its use and the little "interlude" routine you'd need to write to call it.

@chulett,Job is still running while i ran the command,in that case intrim status should also be as Running. No. Reread what I posted more carefully... and then put it from your mind as it won't help here. This kind of thing is typically a locking issue in the target database, have your DBA check wh...

Do you understand what that first slash means? I suspect not.

cd to $DSHOME/bin and then issue your ./dsexport from there. There are no .exe files on UNIX so do not include that.

Right, lay that one right at your DBA's feet.

Long time lurker, eh? :wink: When you say "JobStatus" do you actually mean "UserStatus"? You don't have a lot of control over the job's status other than being able to force either a warning or an abort. User Status can hold anything and the value of it is easy to check in a Sequ...

Ah... only been mentioned a couple of other times here so not something I tend to remember. I'm not even sure it's officially documented.