DSXchange

"C# characters" doesn't tell us a whole lot. Are they extended ASCII? What are the actual hex/dec values of the characters?

I would assume the parameterized name of the file.

Do you really need to start a brand new conversation every time you have a variation of your original question? :? As for this tangent, dsjob both has full "usage" reporting plus it and the other parts of the Command Line Interface are fully documented. Have you been through it yet for you...

Your "exhaustive list" would be in the documentation. Here is a link to the Command Line Interface documentation, the API is documented as well and supports the same capabilities. This to address your 'automation' question. As to the 'develop' side, there is no such capability out of the b...

You'd have to specifically show us what your "list of parameters" looks like before anyone can help. Guessing, however, that you do not have the "-param " you need in front of every name/value pair.

:?: Can you clarify what you mean when you say "created all the parameters in one script ex:param.sh"? A shell script that "creates parameters" would typically mean sets up environment variables (using 'set') which jobs built to do so would use. If it is meant to be a parameter v...

Append = what? The entry in the table I mentioned shows it as the default action and very clearly explains what it does. Nothing. The others are there for when you want something at the table level to be done.

It's those SFDC messages that get ya.

Have you tried reading the documentation? For example, the Connectivity Guide for Oracle Databases pdf? I'd start there. A search for "Table 11" will get you to the right spot.

NULL never equals another NULL as both are unknown values. Sounds to me like you'll need custom SQL where the keys either equal or are both NULL. Something like: and (X = Y or (X is null and Y is null)) Or you can play a different game to do the same thing all at once. Here is the Oracle version sin...

You need to determine the bottleneck. Rather than a magic setting in the connector it could be the source database, complexity of the source SQL, network issues or just how long it takes to write to the target. Eliminate each one by one.

JRodriguez wrote:The purge rules apply only for new jobs.

Isn't that only true for older versions? Could swear it was something they changed / fixed in "more recent" releases.

Thanks.

So as a point of clarification for me... is the index function in "data rule logic" different than the parallel version of the function? Because the latter isn't a zero-based index. When zero means the first character position, how does the function indicate there is no occurrence - by ret...

From what I recall, if you recompile the base job all of those invocations in the Director will go away.