BI Analyst DW Architect at a mining and metals company with 10,001+ employees
Real User
2021-07-09T10:24:55Z
Jul 9, 2021
The scheduling part I don't like due to the fact that it allows you to schedule as a parent and child and other things, however, the error trackability has to be a little more user-friendly. It's also not user-friendly in the sense that it loads all the jobs and there are not enough filters so that it doesn't need to load everything. If the job fails, you don't get any type of alert or email. It would be ideal if there was some sort of automated alert message. Technical support isn't the best. It would be ideal if we understood how to do it in a card exception regarding exclusion, where the card is captured separately rather than filling the whole process on the data inbound side. Certain workloads like this are organized in such a way where you seem to be doubling the work as opposed to streamlining the process.
Manager IT - Business Intelligence & Analytics at a manufacturing company with 10,001+ employees
Real User
2021-02-15T18:45:19Z
Feb 15, 2021
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 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.
Director Information Systems & Software Development at HealthRIGHT 360
Real User
2018-05-21T18:57:00Z
May 21, 2018
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.
WhereScape is data warehouse software that automates the Data Warehouse lifecycle. From implementation to maintenance, WhereScape will ensure your data warehouse projects are completed up to 5x faster than manual coding.
The scheduling part I don't like due to the fact that it allows you to schedule as a parent and child and other things, however, the error trackability has to be a little more user-friendly. It's also not user-friendly in the sense that it loads all the jobs and there are not enough filters so that it doesn't need to load everything. If the job fails, you don't get any type of alert or email. It would be ideal if there was some sort of automated alert message. Technical support isn't the best. It would be ideal if we understood how to do it in a card exception regarding exclusion, where the card is captured separately rather than filling the whole process on the data inbound side. Certain workloads like this are organized in such a way where you seem to be doubling the work as opposed to streamlining the process.
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.