Getting "x" in Teradata SQL Assistant but x in BTEQ

General
Enthusiast

Getting "x" in Teradata SQL Assistant but x in BTEQ

Hi  All,

Whenever I Fire a query to get description data in my TD table. I get “purebred” in SQL Assistant but the same query would give   purebred   in BTEQ. 

Can any one help me with the reason behind these.

Regards,

Amit Terse

5 REPLIES
Senior Apprentice

Re: Getting "x" in Teradata SQL Assistant but x in BTEQ

Hi Amit,

what's the query you submit?

Dieter

Enthusiast

Re: Getting "x" in Teradata SQL Assistant but x in BTEQ

Hi,

 

I have used the same query in both SQL Assistant and in BTEQ.

Query:

 SELECT cntnt_desc

FROM

DVZECUVIEWS.brdcst_media_cntnt

where cntnt_id IN (79262);

 

Senior Apprentice

Re: Getting "x" in Teradata SQL Assistant but x in BTEQ

Hi Amit,

strange, there's an option to double quote strings in SQLA, but this is only for exporting data.

Can you add a CHAR_LENGTH(cntnt_desc) to see if this is returned by the server or added by the client?

DIeter

Enthusiast

Re: Getting "x" in Teradata SQL Assistant but x in BTEQ

Hi Dieter,

I got a clue that the issue was with the character set.

as there were some Extended ASCII character in the data.

but when I export the data using TPT Fast Export and in UTF8 format then some data near the Extended ASCII character is stripped off.

suggest me if u have came across this issue.

Enthusiast

Re: Getting "x" in Teradata SQL Assistant but x in BTEQ

When you submit a query through BTEQ it do not parse information and shows the data as it is stored in the database. 

While SQL Assistant uses customizations to the format and also depend on ODBC settings thats why causes different behaviour than BTEQ.

If BTEQ is showing purebred, it means it is stored in the database as purebred. and SQL-Assistant is causing some parsing with it. 

There might be some UDF installed for string processing that causes Qoutes around string.

Its just a thought! 

Khurram