I have a multi source load script that concatenates a lot of fields into a single "datatable" one of the sources is not going to be used anymore. I tried to re-load the script with that piece commented out, but when I relaod the data it is looking for the "trr_recordid" field that I do not want or need anymore. It may actually look for more of them but it's only bombing on that first field for now. The end result is that I want to replace that piece of script with a new similar but completely different data source.
Concatenate LOAD trr_recordid, carrier, member# as trr_member#, trr_ymdeff, trr_ymdend, text(prov#) as prov#main, date(ymdreviewstart) as ymdfilter, ymdreviewend, recordvalue_int, tool, tool_abbr, question, question_weight, excludefromscoring, nationalstandard FROM [lib:/ZZZ//xxx.qvd] (qvd);
Concatenate Load countyid as saa_countyid, carrier, date(rptyear) as ymdfilter, prov#2 as prov#main, q_num as saa_mems_hit_threshold, q_den as saa_mems_schitz_diag, q_percent as saa_num_div_den, q_avg as saa_mem_score_avg, q_low as saa_mem_score_low, q_high as saa_mem_score_high;
select a.countyid, b.carrier, a.rptyear, a.prov#2, q_num, q_den, q_percent, q_avg, q_low, q_high from zzz a inner join xxx b on a.countyid = b.countyid;
thank you for your quick response, but this is not the case. this was the only spot in my load script that used that "trr_recordid" field name. I believe that it is bombing out when the autogenerated piece is trying to run. I'm afraid to unlock the autogenerated piece for fear of it not allowing me to load other data properly in the future