DSXchange

You are better off creating a generic custom routine for this, one that can both attach and detach from the job needing to be queried.

What makes you guys think it doesn't "start" immediately? If it takes 25 minutes to push everything out, all you can do to improve a query like that is to use a parallel hint. And perhaps bump up the array size.

Why can you not send the email once the loop ends, which it will automatically do after "counter = index"? Or are you controlling the loop in some other fashion?

Again, of course not. Nothing in = nothing out, period. So you need to arrange for there to always be an input of some kind, as already explained. Or if that just isn't making any sense to you, do as Mike suggested almost a month ago and take that part out of the job into an after-job routine that u...

Well then, stop recompiling and Reset the dang job instead. Also post whatever other errors you see with that one, it by itself is fairly meaningless.

Sounds like you already had Array Size at 1 if you stuck with the default, so changing the Transaction Size would be what fixed it. The only "problem" with that is each row is committed as it hits the database, so you take a large performance hit and have no rollback capability. On the plu...

Got no clue how SQL Server does locking, so totally guessing here but... array size? Have you tried setting all links to 1?

Perhaps try wapping it in the absolute value function.

ray.wurlod wrote:Operator role can not start most jobs. Operator role can only start "released" jobs, which almost nobody uses any more.

Hmmm... I thought that was something they 'fixed' in the 8.x world. And added the Super Operator to boot. Ah well.

Right... the FTP stage is not meant to simply move file(s) from one server to another. It's all about pushing rows from a job to another server via the FTP protocol or sourcing a file from another server directly into a job in the same fashion. And because of that it is totally metadata driven. Some...

True... they all suck but mutt sucks less. Blat is just as easy.

You typically accomplish something like this by automating the exporting of job logs into a persistent store (say like an rdbms) and then allowing people to query that store. There's no way that I know of to allow logs to be viewed from the Director client but disallow the running of jobs. Could be ...

Well, that's an interesting solution.

I would simply script something to run 'after job'. Or if I was going to use that routine, I would create a copy of it and name it something more appropriate: DSSendMailInline or some such. More... "future proof" that way I would think as well.

You are probably searching for "too much", too many words at a time - try another search for 'Unable to determine current working directory'.

You'll have to "roll your own" for that, script something using your tool of choice - sendmail, mailx, blat, whatever is in use there that supports that option to "inline" your file.