ANSI92 compliant SQL code not generating correctly-TERADATA

I created a universe in IDT against a Teradata (15) database.

I was recently told by the Teradata DBAs that the SQL being sent to the database needs to be ANSI92 compliant. I then went into the business layer of the universe and added the “Query Script Parameter” to ANSI92 = YES. I’ve published the universe and done some testing only to find that the SQL being generated is still the same (non ANSI92) format.

Is there something else I need to update, perhaps a new line item in the teradata.prm file?

How do I get my universe to generate ANSI92 compliant SQL code?


vbagadonuts :us: (BOB member since 2005-06-07)

I bet you are right about the .prm file…but I would do a little test - create a brand new universe against the same universe connection. Make sure to set the ANSI92 parameter to Yes…see if the sql generated is compliant.


Nick Daniels :uk: (BOB member since 2002-08-15)

I did the test ^ and it didn’t change the SQL formation at all.

After finding a bunch of dead ends/unanswered questions, I was able to piece together an answer that worked for me. In the teradata.prm files there is a setting called OUTERJOIN_GENERATION defaulted to INGRES. When I replaced INGRES with ANSI_92…restarted the Webi Services and Webi APS…it fixed the issue and the sql now is ANSI 92 format. :smiley:


vbagadonuts :us: (BOB member since 2005-06-07)