Hi All,
The boss asked me how we could be made aware of schema changes to transactional application databases that will later cause a data warehouse SSIS package to fail. Obviously, we could keep complete documentation in the form of field mappings that list our sources and destinations--I typically create these in Excel before I begin development--but it would be a huge task to complete up front and to maintain, not to mention having to reference them every time a change to a source table is proposed. Is there another option?
Thanks,
Eric B.