Home Discussions Questions & Answers Extracting Source SQL for Discoverer Migration

Extracting Source SQL for Discoverer Migration

Avatar photoCustomer December 2, 2024 at 1:26 pm

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?

Viewing 6 reply threads
  • Author
    Replies
    • Support December 3, 2024 at 7:20 pm  

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

    • Avatar photoCustomer December 4, 2024 at 7:03 am  

      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 December 5, 2024 at 3:22 pm  

      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`.

    • Avatar photoCustomer December 6, 2024 at 7:25 pm  

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

    • Support December 8, 2024 at 9:25 pm  

      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.

    • Avatar photoCustomer December 10, 2024 at 8:33 am  

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

    • Support December 12, 2024 at 2:47 am  

      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’.

Viewing 6 reply threads
  • You must be logged in to reply to this post.

Login with: