Simplifying ETL execution with system configurations
Working in multiple source and target environments is very common. The development of ETL processes by accessing data directly from the production system happens very rarely. Most of the time, multiple copies of the source system database are created to provide the working environment for ETL developers.
Basically, the development environment is an exact copy of the production environment with the only difference being that the development environment holds an old snapshot of the data or test data in smaller volumes for quick test job execution.
So, what happens after you create a datastore object, import all required tables from database into it, and finish developing your ETL? You have to switch ...
Get SAP Data Services 4.x Cookbook now with the O’Reilly learning platform.
O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.