DSXchange

As do I.

Contact your support peoples, ask them.

I'm assuming A-F are being considered as hex values and thus valid in the Integer data type?

IsValid()

It's an Importing tool, not an Editor.

You do the TRIM in the trigger expression itself. And if you search for a unique portion of your error - say, "ParamValue/Limitvalue is not appropriate", you'll see we've discussed this ad nauseum and proper trimming of the output will solve your problem.

Of course they can be "undone" but I've never run into a situation where I've had to do anything of the sort in say, parent tables because of problems in the child tables. At least not in Production. As noted, constraints are fully qualified / checked / handled in the job designs so that there is no...

Just stumbled across this problem in a project I don't normally spend much time in and found the DS_RESENU hashed file was corrupted as noted here. Copied the contents from another project and all is well now.

:D

Sure. Field(InputField," ",1,1) would get the first word from a space delimited InputField, Field(InputField," ",2,1) would get the second one. Field(InputField," ",1,2) would get the first and second "word" at once. Etc.

Is there any way to make the entire sequence as one transaction? No. And it works this way in any database AFAIK, it's not a DataStage issue. About the only way you can truncate and load 7 "in use" tables and not affect users (too much) is to look into building shadow tables - tables with the same ...

Not to derail your topic as I'm interested in the answers, but there's no need to upgrade just to get support on your current version. Or at least no need that I'm aware of. We have support on our 7.5.x installs and they (sadly) have no intention of upgrading to 8 dot anything. Affordability is a ho...

Cool. Please mark the topic as Resolved using the big button on the top of the screen.

From his website: www.duke-consulting.com in the 'Tips and Tricks' section. All kinds of good stuffs there.

Bummer.

My solution is perfectly valid, I have thousands of production jobs that do this very thing. The jobs are properly designed so they do not violate constraints of any kind.

I have no clue what you mean by "one transaction for each table access".