The solution is scalable in that you can have multiple people working on it at once and it won't slow down.

The data scalability depends on the methodology you use.

We have not run into any scalability issues. As mentioned elsewhere, we have seen significant improvements in our “ETL” processing times as we have converted our ETL logic and processing from our legacy ETL tool to WhereScape RED. Here is a little information about our warehousing environment:

• Oracle RDBMS
• 4 ETL developers
• 15 subject area dimensional data marts
• 905 tables (production presentation tables only)
• 1,160,393,098 records (production presentation tables as of 1/31/2017)
• 1.2 Terabytes of used database space (production only)

The product was deemed unscalable in terms of data storage and performance.

I have not run in to any issues with scalability at this point. Although I don't expect code-generation tools to write optimal code. I am surprised to see WS generate fairly good SQL code. I am very skilled in writing SQL and I was very impressed with what was generated.

Previously, I felt that I might need to write custom procedures to handle large table loads (i.e. 500+GB in a table), however, I no longer believe that to be true. I haven't reached those sizes in this environment (yet), however, I believe columnar indices and other standard SQL features would be able to cover any performance concerns since RED is producing well written SQL.

No issues with scalability have been encountered, in fact we continue to do more and more with RED.

Used it on a Telco enterprise data warehouse using Teradata. As it uses database processing (ELT) it is dependent on the underlying database. It can scale to very large volumes with the appropriate underlying database.

No issues.

No.

No.

The scalability seems okay. It handles most of the data for our 30 sources. We are giving each source an independent repository and a separate EDW repo that uses synonyms for the target objects in the source repos.

We currently have six developers or data engineers using WhereScape, but we don't plan to increase the number, because training is not very cheap.