Optimizing Dynamic Search Screens – Fixing the Performance of Common Code Paths
One of the common challenges that arises in many applications is around how to optimize the SQL Server performance of dynamic search queries. For example, we’ve all seen applications with screens like this:
![]()
Often, there will be many, many more fields to be searched. What I often hear from developers is that there is no way to optimize the query because you don’t know in advance which options the user will choose. While this is partly true, it assumes that human behaviour is much more random than it really is. Let me explain:
2015-04-01

