These index design rules came from a client’s list of ten index don’ts, and readers argued with several of them. This post turns the checkable rules into read-only queries on a demo database, and it measures what each rule really costs. The rest are warnings, not laws, and the post says which is which.
Reasons for Slow Performance in SQL Server: The Top Five
The reasons for slow performance in SQL Server fall into five groups: schema design, T-SQL code, indexing, server deployment and hardware. This post tests three of them on a demo database, with logical reads as proof. It also shows a query that checks four deployment settings.
What is the Replacement of DBCC DBREINDEX? – Interview Question of the Week #263
Question: What is the Replacement of DBCC DBREINDEX?
Answer: The answer to this question is very simple.
Here is the syntax:
Dynamics SQL Server Settings: Five Checks for NAV, AX and CRM
Dynamics SQL Server settings decide most of the speed you get from NAV, AX and CRM, because you rarely control the application code. Five read-only checks cover tempdb, autogrowth, MAXDOP, automatic statistics and statistics age. Each one comes with a short query and a clear rule.
SQL SERVER – Heaps, Scans and RID Lookup
The question was do heaps are very bad and always force a table scan? Let us learn about RID Lookup, Heaps and table scan.
Why a Filtered Index Is Ignored by Parameterized Queries
Explain why a filtered index is ignored with parameters, inspect plan warnings, and compare literal filters, RECOMPILE, and coverage fixes.
Query Plan Join: Why a Query With No Join Shows One
A query plan join can appear even when the query has no join, because SQL Server joins a nonclustered index to the table itself. This post reads the plan of a one table query, removes the join with a covering index, and finds the row count where SQL Server stops using lookups.