Optimizing CPU usage for this query
I have seen a query that is called tens of millions of times a day cause CPU pressure. It's a relatively benign query calling in data from a view that joins several tables together. 1 table has maybe 80k rows and the other ones are small. I was able to improve CPU usage a bit with adding indexes but I'm curious what else I can do to help the devs and have this code not use such a expensive hash match, or any other ideas you might have. I'm an ops guy but this query could cause issues so I wanted to optimize the CPU usage as much as possible, even by modifying/adding indexes. Thanks.