I am receiving this message repeatedly after a simple code like this: What would be the cause?
PROC SQL;
CREATE TABLE WORK.QUERY_FOR_ah AS
SELECT DISTINCT
t1.Store_ID,
t1.Customer_ID,
t1.CLUSTER_ID
FROM adm.Jumb_ah t1
ORDER BY t1.CLUSTER_ID;
QUIT;
That's a weird message. What does the log show?
What happens if you run the code without the create table clause, i.e.:
PROC SQL;
SELECT DISTINCT
t1.Store_ID,
t1.Customer_ID,
t1.CLUSTER_ID
FROM adm.Jumb_ah t1
ORDER BY t1.CLUSTER_ID;
QUIT;
Is the source data (adm.Jumbh_ah) a SAS dataset, or some relational database?
In the part of the screen shot that you blacked out, what data set is the message referring to? Is it adm.Jumb_ah or work.Query_For_ah or something else?
Could adm.Jumb_ah be a database view with integrity constraints, rather than a table? And when you query from adm.Jumb_ah one of the integrity constraints fails?
It's finally time to hack! Remember to visit the SAS Hacker's Hub regularly for news and updates.
Learn how use the CAT functions in SAS to join values from multiple variables into a single value.
Find more tutorials on the SAS Users YouTube channel.
Ready to level-up your skills? Choose your own adventure.