DSXchange

Far simpler to mark the 'First line is column names' option in the stage, it will automatically skip it.

That makes it problematic as you'd need to commit every record to make them available to the lookup. A hashed file solution is simple - write the new records to the same hashed file and don't cache the lookup.

Via their login. Or a crontab transfer by someone with The Power. We don't let anyone willy-nilly schedule jobs, all jobs are run under a single userid so this isn't an issue for us. YMMV.

Your reference lookup is done to an actual database table or a hashed file?

No, they can only see anything scheduled under their userid.

More than likely the answer is 'Yes', but I'd be curious what exactly you mean by 'server Batch process'?

Well then, off you go.

Exactly, not an ETL issue. Was trying to clarify that all of that 'burden' falls squarely on the shoulders of your DBAs. Thanks Ken.

Ah, yes... sorry. That's for a Premium Poster. All a Premium Member takes is moola. No mimimum number of posts required.

Yup, then sort order is not an issue.

What command? Either supply a full path or explicitly 'cd' there first.

Do the logs show you what the actual sql ends up being for the query?

Take all that advice with a grain or two of salt. Bulk loading will be faster but can 'take more space' as the data is appended to any existing data, internal free space is not taken into account. Who among us can reduce the space the target table consumes by 'using VARCHAR instead of CHAR'? You're ...

That's a bad bit of documentation - it works fine with remote databases as well, we do this 'all the time'.

And do you have any idea what those three dates should be?