how to reduce the rework on Informatica ETLs due to change of table and column names -


currently, have lot of etls developed , underlying table , column names going change. example, physical names used abbreviated names rather full names since wanted deploy on oracle, now, decided use sql server, hence there discussion on using full names @ db level. impact etls have developed.

i wondering whether there efficient way remap etl changed column names? can provide file old , new table/column names input.

any on appreciated.

one possible way use sql override value in of source qualifier transformations contains sql query parameter file substitutions. way can change column names , select them in mapping sources without modifying source definitions. of course require up-front refactoring of existing source qualifier transformations.

alternatively, @ database level create views onto existing tables use old abbreviated column names, providing translation between new column name , old one. not require changes existing etl.

however, advise against changing in case, since difference purely cosmetic - produce maintenance , complexity headaches.


Comments

Popular posts from this blog

c# - how to write client side events functions for the combobox items -

exception - Python, pyPdf OCR error: pyPdf.utils.PdfReadError: EOF marker not found -