Home › Discussions › Questions & Answers › Post-Migration Check for Slow LOV Queries
Customer · · Questions & Answers · 5 replies
Following our mass migration from Discoverer, some reports are displaying performance issues specifically when accessing the List of Values (LOVs). We suspect complex LOV queries carried over. How can we systematically validate the syntax and identify slow queries?
The dedicated Blitz Report LOV SQL Validation report is essential here. It validates LOV SQLs for valid syntax, helping flag issues that prevent efficient execution. Also look for slow ‘distinct’ style queries that need conversion.
We manually created several custom LOVs during development that share the same query logic but aren’t set up as shared LOVs. This makes maintenance difficult. How can I audit these duplicates?
Run the Blitz Report Parameter Custom LOV Duplication Validation report. It identifies parameters using custom LOVs that share identical queries, prompting you to consolidate them into shared LOVs.
If we were performing the full migration process, what step involving LOV checking is included right after the initial import of the zipped EEX files?
After importing the zipped EEX file, you must run ‘Blitz Report Discoverer Import’ and then verify the migration result by running reports including ‘Blitz Report LOV SQL Validation’ to correct errors and change slow SQLs.
Sign in with LinkedIn or Google to take part.
