Your client reported that a form in the application is very slow to load. You investigate and find a query entity which is nor performing well. Which…

Optimizing a slow query requires a combined approach that addresses both the application layer (Appian) and the database layer. In Appian, applying appropriate filters within the query itself ensures that only the necessary subset of data is requested, minimizing data transfer and in-memory processing. In the database, creating indices on the columns that are frequently used for filtering (in WHERE clauses) and sorting (in ORDER BY clauses) allows the database engine to locate and retrieve the requested records efficiently, avoiding slow full-table scans.

A. This is an incomplete solution. While a view can pre-filter data, it doesn't address inefficient sorting or the need for dynamic filters from the Appian application itself.

B. Indexing all fields is a poor database practice. While indices speed up reads, they slow down write operations (inserts, updates, deletes) and consume storage space.

1. Appian Documentation

Querying Data from an RDBMS: "To ensure your queries execute quickly

we recommend following these best practices: ... Filter your queries to return the minimum necessary data. ... Add database indices to columns that are frequently filtered or sorted. This is the most effective way to improve query performance."

2. Appian Documentation

Data Store Best Practices: "Create indexes on columns that will be frequently queried

especially foreign key columns. Indexes can dramatically improve the performance of your queries." This supports the database-side optimization mentioned in the correct answer.

3. Appian Documentation

Performance Best Practices: "When querying data

only retrieve the data you need. The more data you retrieve

the more memory is consumed and the longer it will take to transfer the data over the network." This supports the application-side filtering aspect of the correct answer.