Home › Discussions › Questions & Answers › Accuracy of Automated Migration: User Review of Blitz Report’s Discoverer EUL Import Utility

Accuracy of Automated Migration: User Review of Blitz Report’s Discoverer EUL Import Utility

Avatar photoCustomer Questions & Answers 5 replies

Our Oracle Discoverer replacement project hinges on finding a solution that accurately translates complex EUL query logic into a supported format without manual intervention . We are evaluating the Enginatics automated import tool and are specifically concerned about the fidelity of the SQL conversion process, particularly for highly customized workbooks . Can former Discoverer users confirm the reliability and accuracy of this feature, or do we still need extensive post-migration validation for each imported report?

5 replies

  • Support Enginatics

    The Blitz Report Discoverer report import feature is designed for high fidelity, providing automated migration of worksheet SQLs along with associated security and parameters . One banking customer, Raiffeisen Bank International, successfully transitioned their complex reports, confirming the tool’s ability to handle challenging workbook conversions .

  • Support Enginatics

    Prior to actual migration, we recommend utilizing the ‘DIS Worksheet SQL’ Blitz Report to document the underlying SQL queries from your EULs, facilitating quick validation of the imported report definitions post-conversion .

  • If we opt for bulk migration using the API, how quickly should we expect the process to run? Our current volume of active reports is significant, around 1,000 unique worksheets.

  • Support Enginatics

    The mass import utility is highly efficient; migration via the API typically processes around 1,000 reports in approximately 10 minutes . This rapid turnaround greatly accelerates your Discoverer replacement project timeline.

  • Support Enginatics

    This automated solution minimizes the need for extensive manual post-migration rework, focusing developer time on validating the output rather than rebuilding core logic.

  • You must be logged in to reply to this post.