To maintain a single data warehouse/mart implementation our development team needs to access 50 user ID/password/server combinations. The architecture is one where atomic-level detailed information from fuel cost and billing systems is brought into the DW dimensional models then aggregates dimensionally modeled are generated in the data mart. The account access information is too much for anyone to remember so it is out on the server in a text file for reference and our passwords are not secure/changed because synchronizing them and parameter files is a task and a half. Basically our DBAs have gone wild architecting the environment without project/ETL team input. What is an ETL/project team to do in such an environment? Is this the norm?
Dig Deeper on Oracle data warehousing
What are the pros/cons of custom development vs. an ETL tool? The question of custom code versus the use an ETL tool is one that we are faced with ...
I am evaluating ETL tools for the organization. Considering that I am looking at three or four tools, how do I rate these and put a weight-age for ...
ETL tools provide very robust support for complex business logic.
Have a question for an expert?
Please add a title for your question
Get answers from a TechTarget expert on whatever's puzzling you.