Please share with the community what you think needs improvement with WhereScape RED.
What are its weaknesses? What would you like to see changed in a future version?
Customization could be better. When you need to modify or write some custom code, it can get a little messy. Performance can also be better. It would be nice to have synchronicity when integrating multiple tools.
Project-based searching of data objects in the data warehouse browser needs to be improved. When processing stage (work) tables if there are a lot then one has to scroll through a larger list. There is an ability to have projects or subject areas for processing that if applied to source tables would speed development. On a separate note - those who have criticized this project for having a row based cursor and thus inefficient approach have not understood how the product works. I have used it for 10ish years and >99% of my processing is set based and efficient and supported by the product. It explicitly asks for set based vs row-based processing.
The schedular needs improvement
The scheduled jobs which are run by the WhereScape scheduler seem to be a strangely separate animal. Unlike all other WhereScape objects, jobs cannot be added to WhereScape projects. Also, unlike all other objects, jobs also cannot be deleted using a WhereScape deployment application.
Jobs cannot be deleted via the deployment package. When deploying from dev to QA or production, a job has to be retired. The job has to be manually removed from the target environment.
I'm working at a manufacturing company with 10,001+ employees.
I'm trying to understand the way to host/use WhereScape RED on the Cloud. How do I implement it? Do I need a VM (IaaS) or just a DB (PaaS)?
Should I worry about any difficulties or disadvantages of using Wherescape RED on the Cloud?
When evaluating Data Integration tools, what aspects do you think are the most important to look for? Let the community members know what you think.
Thank you for sharing your knowledge!