SQL Server Tuning Case Study
This is the case when tuning sometimes can not be done perfectly.
We are trying to change DB code, so nothing else needs to change.
In some cases, even though the result set is exactly the same, rows may come back in the different order back to the app.
In those cases, we have to work with the client application team to review that different order of the rows is not going to break the application.
I know a lot of you will say “it shouldn’t” – but for the large enterprise apps you never know what type of stupidity is inside them. It may not. Or it may.
The point is to be careful.
Here are more details on what we did.
Table ‘tblLineItems’. Scan count 5, logical reads 36, physical reads 0