DSXchange

removed garbage post

A friend suggested that I provide the structure of a job sequence to give you an idea of what I am doing with each table, so here goes: JobControl starts | BatchNumber job runs | Job Sequence starts | Check # of rows in Source | |----exit showing success if zero ---------------------------|---------...

Hey Craig,

Would Ken's JobControl utility be of any use to Rajesh in this situation? I don't know what versions it may or may not work with. Just a thought and I figured you would probably know if it would (or maybe Ken's ears are burning and he will answer for us )

Hey Craig,

Would Ken's JobControl utility be of any use to Rajesh in this situation? I don't know what versions it may or may not work with. Just a thought and I figured you would probably know if it would (or maybe Ken's ears are burning and he will answer for us )

Hi all! Hopefully, this is a legimate problem and not just one of those instances of me having another mental speedbump... :oops: Here's my situation: I am using Ken Bland's JobControl utility to run my data transfer process for 192 tables from our OLTP system to staging tables for each client's dat...

Depending on how much data is involved with each row in the sequential files, follow Arnd's suggestion about using the hashed file, but only put the PK fields in there, this will make your hashed file smaller and possibly speed things up as well. Once again, this depends on the amount of data you ar...

Depending on how much data is involved with each row in the sequential files, follow Arnd's suggestion about using the hashed file, but only put the PK fields in there, this will make your hashed file smaller and possibly speed things up as well. Once again, this depends on the amount of data you ar...

Just as an experiment, try landing the data instead of sending it directly from source to target in the same job. Send the source data to a sequential file and then put together a job to push the landed data to the target. If you are using the ODBC Stage, consider trying the RDBMS stage. I know it i...

I haven't actually faced this problem, but it looks as though you need to add code that will provide better error control. Whether this is in the form of an additional stage in the sequence or a terminator stage or something, I'm not sure. Could you provide more information about how the sequence is...

I have found issues with using the Run Stored Procedure stage as well. My solution has just been to use a before or after SQL call in a workable place. For example, if I need to run a procedure before I process another job then in that job, I will add the code that would normally call an SP from wit...

Also, if you have parameterized your paths for job control, then you can refer to the parameter using the standard #parametername# notation.

Is the field that has the problem consistently in the same position, or do multiple fields have the issue? If it is always the 17th field, for example, then you could use a little Perl script to find rows that have too many commas and then remove the comma after the beginning of that problem field. ...

Just for grins, try it this way: record ( Col1:string[5] { delim='ws', quote=double }; Clo2:string[5] { delim='ws', quote=double }; ) I don't know how finicky Parallel is on format of the file. I am assuming that the database defaults field definitions to nullable (if that's not the case then add it...

Something else you might try is landing the data. Rewrite the job to drop the data into a sequential file using pipe (|) delimiters (unless your data contains that character). Then load to your target from the sequential file. This should take care of the issue with your dates. I also believe it wil...

It is literally pennies a day and worth every bit of it. You can write it off as a business expense at the end of the year (if your company doesn't pay for it for you) and everything!