List three query design guidelines that can help reduce demands on the physical resources while providing an improvement in performance.

What will be an ideal response?

Avoid operators, such as LIKE, that add significant overhead to the query. Useful in certain
circumstances, the LIKE operator will result in a full table scan that causes the database to
evaluate every row in a table to produce a result set.

In the SELECT statement, specify only data that is actually needed in the result set. Avoid using * as a substitute for column names.

Sorting is a memory-intensive operation and should only be performed if absolutely necessary.

Use fully qualified names when referring to database objects in a query. This saves the overhead of the database engine having to resolve the logical name each time the query is run.

Include all columns that are part of a foreign key in a JOIN clause.

Avoid placing implicit or explicit functions in the WHERE clause; for example, subqueries will significantly degrade performance.