What needs improvement with WhereScape RED?


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?

ITCS user
55 Answers

author avatar
Top 5Real User

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.

author avatar
Top 10Real User

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.

author avatar
Top 20Real User

The schedular needs improvement

author avatar

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.

author avatar
Real User

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.

Find out what your peers are saying about WhereScape, Microsoft, Informatica and others in Data Integration Tools. Updated: July 2021.
521,690 professionals have used our research since 2012.