When starting a new data warehouse project, you must make the decision to either buy or build your ETL (extract, transform and load). There are a few constraints that may prevent you from purchasing a product. After buying the hardware, database software and BI tools, you may not have enough money left in your capital budget for an ETL purchase.

If you are starting with a proof of concept, then it is unlikely that you will have the time or the budget to go through an ETL product selection and purchase cycle in the time allotted. Because there is no vendor selection, tool evaluation or training involved with custom coding, you can start the analysis and programming immediately. You also don't need to worry about sustainability with a proof of concept; therefore, you can do without elements you need in a production scenario such as integrated scheduling, dependency management and recoverability. After the proof of concept, you may consider evaluating a tool rather than doing the additional development, or you may continue with what you have.

Register or login for access to this item and much more

All Information Management content is archived after seven days.

Community members receive:
  • All recent and archived articles
  • Conference offers and updates
  • A full menu of enewsletter options
  • Web seminars, white papers, ebooks

Don't have an account? Register for Free Unlimited Access