I have a script in which I applied an Index. I noticed that in a production run while monitoring the job that when the index is applied the logs are massive
246 +proc sql;
247 +create index CUST_ID on CTC_TB(CUST_ID);
INFO: Multiple concurrent threads will be used to create the index.
NOTE: Simple index CUST_ID has been defined.
248 +run;
I pulled the above from the log where it cerates the index.
After that, when it runs the part of the script where it utilized the index i get pages upon pages of this:
INFO: Index CUST_ID selected for WHERE clause optimization.
INFO: Use of index CUST_ID for WHERE clause optimization canceled.
INFO: Index CUST_ID selected for WHERE clause optimization.
INFO: Use of index CUST_ID for WHERE clause optimization canceled.
INFO: Index CUST_ID selected for WHERE clause optimization.
The code runs and all. But I just wanted to know if this was normal or if I am applying the index inefficiently/incorrectly.
TIA!
Is it possible to share the log for the step that queries the table?
Are you ready for the spotlight? We're accepting content ideas for SAS Innovate 2025 to be held May 6-9 in Orlando, FL. The call is open until September 25. Read more here about why you should contribute and what is in it for you!
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.