DSXchange

If you want to use SQL to insert or update, you will need to provide column names in the file dictionary. Search DSXchange for "INSERT INTO DICT" for examples.

Otherwise you can use DataStage BASIC code (which does not need column names) or an operating system command such as UVwrite.

Seek out a company called PR3 who may be able to help. I believe they're based in Philadelphia.

Now all you need is correct DataStage BASIC syntax (hint: there's no "fi" and you may need some block-ending "End" statements).

Nice one. Hijacking your own thread. Your most recent question has nothing whatsoever to deal with the thread topic.

An interesting observation. Why should we have to do that? Surely importing using the Connector Access Service will set up everything needed in the metadata repository! If not, I'd be asking why not, and suggesting that there's an enhancement request in the offing.

Don't believe anything that the View Data facility (data browser) shows you when dealing with accented characters. It was clearly written for a market (US English) that does not have them.

That smacks of addressing the symptom rather than the cause, but you probably should do that anyway just so that you get your XMETA back.

I disagree. Think about it some more. Do some examples on paper.

Having read through the fixes for that version on Fix Central (I'm installing the same this weekend), I can't see one that addresses this issue. Therefore I'll be curious to hear what your support provider has to say. (I am presuming, in all of this, that no-one is hacking the XMETA database at your...

We have multiple database products in the mix, so the standard varies slightly. For example:
MYSQL_database_DEV
ORCL_database_DEV
MSSS_database_UAT

Get all the dates into internal format, if they aren't already, then it's a matter of simple arithmetic. For example: svStartDateOver5Days <-- Abs(q_start_date - p_start_date) svpInterval <-- p_end_date - p_start_date You need to have a tighter definition of "difference", in my opinion. Is...

What exact version are you running? What fix packs?

Ask "someone" how they plan to identify which one to use - in the tool all you get to see is the DSN itself.

Post their answer - we're thirsting for this learning!

There's no scope for parameters in the Match Specification itself. Nor, as far as I can tell, can you use a parameter for the Match Specification in a Reference Match stage or an Unduplicate Match stage. Why would you want to?

No.