Note: If you are using SAS^® Marketing Automation in a Windows environment and are using Microsoft SQL Server to hold the SAS^® Customer Intelligence common data model, see SAS Note 57270: "Applying Hot Fixes W25001 or K96004 to SAS/ACCESS^® Interface to OLE DB prevents SAS^® Marketing Automation campaigns from working" before applying the hot fix in this SAS Note.

When you use SAS/ACCESS Interface to OLE DB and run a SAS UTF-8 encoding session, you might encounter a problem in which the non-UNICODE character column lengths are three times larger than expected when they are read into SAS. These non-UNICODE Microsoft SQL Server data types are CHAR, VARCHAR, and TEXT.

To work around the issue, use the SAS data set option DBSASTYPE= to specify the column length. Here is an example:

data saslib.table;
   set oledblib.table(dbsastype=(column1='char(10)'));
run;

The column column1 is read into SAS with a length of 10.

Click the Hot Fix tab in this note to access the hot fix for this issue.

Operating System and Release Information

A fix for this issue for SAS/ACCESS Interface to OLE DB 9.4_M3 is available at:

A fix for this issue for SAS/ACCESS Interface to OLE DB 9.4_M2 is available at:

A fix for this issue for SAS/ACCESS Interface to OLE DB 9.3_M2 is available at: