We’ve all been there. You’ve got a query where the JOIN or WHERE predicate is not SARGable. You’ve read about how this can be a problem, and how bad it is for performance. Alas, you cannot change the query. Sometimes this reason is political, sometimes … [Read More]
There is a corner case where it makes sense to have a non-clustered index “duplicating” the clustered index. If you have a query that frequently scans the table, and ONLY makes use of the clustering key column, the query optimizer will prefer to use the non-clustered index.
SQL Server supports two kinds of data compression on rowstore data. Columnstore compression is for a different day. You can compress heaps, clustered indexes (on both tables and views), and nonclustered indexes (on both tables and views). Compression requirements Data compression is available in SQL … [Read More]
SQL Server supports two kinds of data compression on rowstore data. Columnstore compression is for a different day. You can compress heaps, clustered indexes (on both tables and views), and nonclustered indexes (on both tables and views). Compression requirements Data compression is available in SQL … [Read More]
SQL Server supports two kinds of data compression on rowstore data. Columnstore compression is for a different day. You can compress heaps, clustered indexes (on both tables and views), and nonclustered indexes (on both tables and views). Compression requirements Data compression is available in SQL … [Read More]
At work, we make extensive use of views & synonyms. The reasons are complex (and fodder for another post), but here’s a simplified example: Pricing data is updated multiple times per day, and we want to keep multiple generations of the pricing table online. By … [Read More]
Copyright © 2024 | Andy Mallon | am2.co