Query definitions

Users typically have a well-defined set of columns that they want to query in each application. You can identify these columns by asking users or by examining reports of slow-running SELECT statements. Indexing these columns can improve system performance.

Users can create and save their own queries and share queries with other users. Saved queries are stored in a table named QUERY. You must periodically review these saved queries for inefficient conditions and use of unindexed columns.

With SQL statements, you can create special-purpose queries for example, return all Preventive Maintenance work orders created since Monday of this week. When you create these queries, you can save users the effort of querying larger sets and sorting and scrolling through the sets.

You also can provide users with an efficient default query for frequently used applications so that they can see a preferred record set when they access the application. For example, in the Work Order Tracking application, you can specify a default query for supervisor Smith. With this default query in place, initially the user can see only work orders with SMITH in the Supervisor field.