Optimize Slow Queries on Large Data

How do you optimize a query that is performing poorly on a large dataset in a banking environment?

You are given a query that returns slow results on a large transactional dataset. Improve it so it returns the same answer with better performance.

Output

1. Return the same result set as the original query
2. Keep the output columns and row order unchanged
3. Do not change the business logic or remove any required rows

Output details

• Return columns in this order: transaction_id, account_id, transaction_date, amount, region_name.
• Order rows by transaction_date descending, then break ties by transaction_id descending.
• Include rows where transaction_date is on or after DATE '2024-01-01'.
• Require status to equal POSTED and is_active to equal TRUE.