Filtered Indexes: The Developer’s Secret Weapon in SQL Server
Learn about filtered indexes in SQL Server, how they work, and how they can help improve performance.
2025-11-24
5,198 reads
Learn about filtered indexes in SQL Server, how they work, and how they can help improve performance.
2025-11-24
5,198 reads
I recently resolved an issue where a query pulling data from the last 30 days would time out due to the table’s size and the lack of a supporting index. Creating a supporting index is possible, but not ideal; it will be very large and may not be useful for most queries and use cases. I wonder how I could implement a filtered index that follows time and is always limited to the last n days.
2025-09-10
In this article, I share how an SQL Server filtered index solved the problem of preventing duplicates for new rows in a table.
2024-07-03
By James Serra
Most enterprise questions do not live neatly in one place. The numbers may be...
Redshift keeps its SYS_* monitoring views for seven days in cluster, which is fine...
By Steve Jones
I was updating my session for the Data API Builder (DAB) recently, mostly to...
Telp/Wa 62 8218200233 PQHX+93W, Jl. RS. Fatmawati Raya No.6 A, RT.1/RW.5, Cipete Sel., Kec....
Telp/Wa 62 8218200203 Gedung Gajah Tebet, Jl. Dr. Saharjo No.Raya 111 Unit N &...
Telp/Wa:62 8218200174 Jl. Tebet Barat IX No.40, RT.6/RW.4, Tebet Bar., Kec. Tebet, Kota Jakarta...
I have 3 instances of a brand new long running query that are executing on a SQL Server 2025 instance. Query store is enabled. One of the queries is killed by the administrator, one is cancelled by the user. The other runs to completion. How many rows are in Query Store for this query?
See possible answers