Using SAS/ACCESS Interface to Greenplum in a DBCS session, such as Simplified or Traditional Chinese, might result in data being truncated. This would become apparent when you are reading and writing data.

Here is an example. If you are viewing data in Greenplum using a third-party tool, it might look like this:

However, after reading that data into SAS using SAS/ACCESS Interface to Greenplum, the data might be truncated and look something like the following:

The problem occurs because the Greenplum engine is not encoding the data properly. When you are running DBCS SAS sessions, the engine sends the data to the DataDirect ODBC driver.

Note: Data that has been written to and read from Greenplum using UTF-8 SAS sessions is and has been correct.

Operating System and Release Information