The biggest win for my organization are the great improvements we have seen in load / refresh processing time over our legacy ETL tool. I was skeptical of the ELT architecture going into our Proof of Concept with WhereScape. I had believed that a more traditional ETL architecture of dedicated ETL servers and applications doing the transformations in memory, then writing to the database, would be faster. It turned out that the ELT approach of using the muscle of the RDBMS was significantly faster than our legacy ETL tool. We are now 2.5 years into using WhereScape and all warehouse code we have converted from our old tool to WhereScape has performed faster; anywhere from 20-80% reduction in processing time. This was huge for us, as increased demand for the warehouse and increased upstream operational system batch processing has really shrunk our batch window. We now have room in our batch window to add more content to the warehouse. In addition to improved performance, we no longer need dedicated ETL servers in our warehouse environment.
The documentation WhereScape provides has also been great. We have always struggled with maintaining documentation on our ETL. It is very nice to get source-to-target mappings, table diagrams, and dependency diagrams, which are up to date, with the click of a button.
Finally, the use of RED has resulted in a much more standardized, easier to support warehousing environment, from what we had prior.