Hello Panoply pals, I'm really struggling with a query performance issue and I'm hoping someone can give me some additional things to try. I have a table with 600,000 transactions and a view to calculate the latest status for each person in the table. The view returns 1 record per person and takes about 90 seconds to run. When I join the table to the view (so my users can select current_status from a filter and see the transaction history for folks with that status), it takes 30 minutes to run! What can I do to speed things up?
- I'm using person id for the join which is configured as the DISTKEY in the transaction table
- probably not applicable for this question, but the transaction date is configured as SORTKEY
- the current status view returns 4 columns
- the view that joins the transactions table to the current view returns 30 columns
Please sign in to leave a comment.