Even if @RW9 is not a DI Studio user, he's on to it. DI Studio is a metadata specification tool, so it lacks a bit of the data management parts, like automatically create alter table statements. So, you add columns in metadata, create mappings from the source. If your target table have's a some kind of update strategy in the table loader, chances are that you will receive an error when redploying your job code. So you need to add new/changed columns to the physical table in this scenario. If you are working with SAS tables/data sets - I'm sorry, but a rewrite of all data will occur.   If you are/or want to become a mature data warehouse shop, you need to implement these kind of actions in your production/maintenance process. ... View more

The right forum for DIS questions would be "SAS Data Management".   To answer your question: The changes you apply in DIS are on SAS Metadata level. What you look at in SAS EG is most likely on physical table level (except the library got assigne via META engine).   I assume your DIS job only creates the table if it doesn't exist. In such a case just changing the column on Metadata level in the DIS job won't change the underlying physical table. Easiest is: Delete the physical table, then re-run your DIS job and things should work just fine. ... View more