topic Re: Getting transcode error while pulling data from REDSHIFT using PROC SQL in SAS Programming

Getting transcode error while pulling data from REDSHIFT using PROC SQL

RAmarapuram — Tue, 02 May 2023 17:53:29 GMT

Hi Everyone,

I am facing issue with data pull from REDSHIFT using PROC SQL. The code errors out with "unable to transcode:".

I have viewed various posts regarding encoding option, but they talk about DATASET and filename.

Can someone help me on this please ?

Appreciate your time on this.

Re: Getting transcode error while pulling data from REDSHIFT using PROC SQL

ballardw — Tue, 02 May 2023 20:51:50 GMT

SAS, as well as all the other programs on your computer, uses some character set. One difference is that SAS allows you to specify, or in some cases override the specification, of the set used. You will have a default character set for your computer and depending on options chosen when SAS was installed one was selected as the default.

That's generic information.

Now you are attempting to access data that apparently contains characters from a set that your current setting in SAS does not like. The solution, in general, depends on two things:

What character set is the external data source using?

What is your current SAS session using?

Depending on the combination of answers to the two questions different solutions are possible.

Additionally how you "pull" data from an external source may have some impact as a specific SAS Access tool for that set may, or may not, attempt an automatic conversion.

When you answer those two questions then we may be able to provide specific answers.

It may help to provide the log of the code submitted and all the messages associated, Or screen shots if using a graphic interface to connect to the Redshift source, so that we can see the choices you already made.

Re: Getting transcode error while pulling data from REDSHIFT using PROC SQL

SASKiwi — Tue, 02 May 2023 22:02:39 GMT

To check your SAS session encoding run this:

proc options option = encoding;
run;

Compare this with Redshift encoding. You could ask your Redshift DBA for this if you don't know.

Transcoding problems can happen if there is an encoding difference.