ETO Results | Maximizing Query Performance

BO 4.3 Platform

Updated over a week ago

Guidelines to create an optimized Query for your reports:

1) Create a Universe with only the focus area and forms that you need for a specific Query. Although the maximum limit is 20, limiting the total number of kernels to around 10 or less will speed up performance.

2) Do not mix Assessments or Efforts/Points of Service with TouchPoint or Collections data in the same Query.

3) When reporting on TouchPoints using the Flattened Universe, include no more than 3 or 4 TouchPoints in each Query. Follow the same logic when reporting on Collections, Referrals, and Approvals.

4) Flattened demographics should be used whenever possible as opposed to Unflattened demographics.

5) Do not mix Unflattened data with Flattened data.

6) Avoid pulling data from multiple folders into the same Query.

7) When creating a Query filter, use the indexed fields over non-indexed fields when possible.

  • Indexed fields are identifiers like Site ID, Program ID, and standard fields like "Date Taken" in a TouchPoint. Any names or custom fields in the system are not indexed and are not optimized for reporting.

8) Avoid re-Queries (results from another Query) and sub Queries as much as possible. Re-Queries are OK for performance when only 1–10 responses are being passed from the primary Query to the secondary and when using an indexed field.

9) Avoid running reports at peak usage times. If this is difficult, schedule reports to run between 4:00a.m.–7:00a.m. or 6:00p.m.–9:00p.m.EST.

For more information on Scheduling Reports, click here.

Did this answer your question?