SQL statements that are generated by SAS Customer Intelligence use MATables instead of the uploaded DBTmplib tables. One example where this might happen is when you update counts on a set of nodes in a group.

The following SQL statement is shown in the SASCustIntelCore6.1.log:

libname dbtmplib OLEDB PROPERTIES=('Persist Security Info'=True 'Integrated
Security'=SSPI 'Initial Catalog'=MAData) PROMPT=NO
DATASOURCE="xxxx" PROVIDER=SQLOLEDB.1;
libname MATables list;

PROC SQL;
Create table MATables.TGGAAOETX0ZCGQTXEsasdemo as
SELECT DISTINCT
  table1.CLIENTNUM AS CLIENTNUM LABEL='CLIENTNUM' FORMAT=F12.0
FROM
  MAData.CLIENTS table0 Inner join MATables.TCGADOLNX4JFXU5KYsasdemo table1 on
table1.CLIENTNUM = table0.CLIENTNUM Inner join
dbtmplib.T2820000090FGCG2MKDJRGHRNEZ table2 on table2.CLIENTNUM =
table0.CLIENTNUM
WHERE
  table0.GENDER = 'F';
quit;

As you can see, the FROM clause has joins to the MATable and the DBTmplib table, which is incorrect. The FROM clause should join only to the already uploaded DBTmplib tables.

Generating SQL statements that involves MATables instead of the uploaded DBTmplib tables can severely affect performance when you execute campaigns.

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 Marketing Automation 6.1_M1 is available at: