Home › Discussions › Questions & Answers › Extracting Source SQL for Discoverer Migration

Extracting Source SQL for Discoverer Migration

Avatar photoCustomer Questions & Answers 7 replies

As part of our Discoverer migration, we need to extract the underlying SQL queries from all Discoverer worksheets to convert them into Blitz Reports. Which report facilitates this SQL extraction?

7 replies

  • Support Enginatics

    Use the DIS Worksheet SQLs report. This report retrieves Discoverer worksheet SQL queries.

  • The standard location (`eul5_documents.doc_document`) stores the workbook in a binary format, making extraction difficult. How does this report manage to retrieve the SQL?

  • Support Enginatics

    The report leverages an active trigger function, `eul_trigger$post_save_document`, which writes each worksheet’s SQL query to the table `ams_discoverer_sql`.

  • During the migration, how can we track user adoption to see who is still relying on Discoverer versus those transitioning to Blitz Report?

  • Support Enginatics

    Run the DIS Discoverer and Blitz Report Users report. It tracks user adoption by showing the monthly execution counts of Discoverer worksheets and Blitz Reports per user.

  • Is there a full checklist of validation reports recommended after importing Discoverer EEX files?

  • Support Enginatics

    Yes, after running ‘Blitz Report Discoverer Import,’ you should verify the results using several reports, including ‘Blitz Report LOV SQL Validation’, ‘Blitz Report SQL Validation’, and ‘Blitz Report Parameter Uniqueness Validation’.

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