DSXchange

Go in reverse order.

... except they are not having issues with commas but rather embedded double quotes inside one of the double-quoted string data fields.

Not that I am aware of. Others may, however. While you wait you could always open a support case, see if they have any Words of Wisdom.

Create a new post for that, please.

I guess I need to check out Alteryx to see what a "more modern user interface" looks like.

Unless something has changed that I'm not aware of, the advice I've seen here is to use a Server job and its sequential file stage, that or use it in a Server Shared Container in your PX job. For whatever reason, it can handle those embedded quotes much more better than the Parallel version can.

According to the "Connectivity Guide for Teradata Databases" documentation that I have you have the following property for that: Enable quoted identifiers Use this property to specify whether to enclose database object names in double quotation marks in the generated SQL. Double quotation ...

If you want a specific parameter then don't use "LIKE ...ABC..." as that is a wildcard search. Worst case get rid of the "..." on either side, does that not get you want you want if you do that?

It's what happens when someone posts a link to a topic that doesn't start with "www.", just "dsxchange.com/xxxxx" which is what Ray did. When I edited in the three w's it started to work properly for everyone, including me. And you.

Without access to the latest version, the typical answer for a "basic one single tab" would be simply another csv file. Excel will automatically open them as a spreadsheet, it would be up to the user to save it back as an xls. You may be able to leverage ODBC for this, there are UNIX drive...

In other words, yet another Ray Wurlod post, one with a bit more explanation of something that "isn't in the manual".

Perhaps you should look into why they are like that and see what needs to be done to correctly 'translate' them rather than simply removing them... just a thought.

While various translation programs could probably do a (somewhat) decent job of it, best to stick with English here.

There's nothing "unstructured" about your data so why use that stage? Use the normal Sequential File stage.

You should be importing the metadata for your source and target, then loading them into the stage, that way you don't have to manually type them in. And then yes, the source stage can automatically generate the SQL at runtime from the metadata. I have no DataStage access and it's been way too long b...