- Impact and Lineage analysis.
- Auto Documentation.
- Recovery of jobs.
- Text Data Processing.
I've done a migration project (from OWB to BODS) in Singapore. The reason customer opted for BODS over OWB was automated trigger E-mail when job fails and the recovery of the jobs from the point it failed in the last execution. Also, when loading data from flat files, once the data loading from a file is complete BODS is capable enough to call any batch files to move the processed files to another location after completion.
When working with custom functions, many times it fails to execute (from 4.0 onwards) because of the data types mismatch errors. This has to be corrected.
More than 6 Years.
No issues with deployment.
No issues with stability.
No issues with scalability.
100% as no manual intervention is required once the solution is implemented.Technical Support:
It was quite straightforward for me as I had experience with other ETL tools and the concepts.
Through vendor team and the level of expertise was satisfactory.