Production run of code - Indexing - Massive Logs

[Jyuen204]

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!

[LinusH]

Is it possible to share the log for the step that queries the table?

[Jyuen204]

I have a table i have built with a few thousand records. I created the index on the key I am matching against. The table I am matching against is a Table in our EDW. Nothing fancy in other words just :
Create table XYZ
as
Select a.* from EDW.TABLE as A
inner join MYTABLE as B
where a.COA = b.COA;
quit;