Question: How to skip top N Rows in SQL Server and retrieve the rest of the rows? Answer: I had asked the above question in one of the interviews last week.
WMI Invalid Class: Patch Rule Fails on Cluster Service Check
A WMI invalid class error can sit behind a patch rule failure that looks like a cluster problem. The rule was Not clustered or the cluster service is up and online. Recompiling the WMI MOF files with mofcomp fixed it for my client.
THREADPOOL Waits: When Raising Max Worker Count Helps
THREADPOOL waits mean tasks waited for a worker thread. Five read-only queries separate real thread starvation from blocking and busy CPUs. The post lists five signs and shows how to raise the cap in small steps.
Delete the Wrong Row: A Cheap Answer That Passes the Test
A cheap answer to the multiple table delete puzzle reads only 6 pages and passes the check. It can still delete the wrong row. This post shows the answer, asks you to find the row it removes by mistake, and fixes it with a delete that costs 5 reads.
Max Worker Count: Why Typing 10000 Slowed a Server
Max worker count looks like a speed dial but behaves like a safety limit. A client typed 10000 on an 8 processor server and slowed it, and a reset to 0 fixed it in minutes. Two read-only queries show your value and whether workers run short.
OFFSET FETCH in SQL Server: Get Rows 21 to 30 After ORDER BY
OFFSET FETCH reads a block of rows from the middle of a sorted result. The demo returns rows 21 to 30, builds pages from a page number and measures why deep pages cost more. A seek based alternative reads the same two pages every time.
Frequently Run Stored Procedures: Find Them in the Cache
Frequently run stored procedures leave an execution count in the plan cache. A tested demo ranks three procedures by count, reads and calls per minute. It also shows what the cache forgets and when to use Query Store instead.
How to Write in Text File from T-SQL in SQL Server? – Interview Question of the Week #236
Question: How to Write in Text File from T-SQL in SQL Server?
The question above was actually asked in an interview and also was not asked in the same word.
SQL SERVER – Historical PHYSICAL_ONLY Bug and Version Specific Evidence
A historical SQL Server 2017 Bug affected CHECKDB with PHYSICAL_ONLY and clustered columnstore data. One client observed a dump.
Setup Error 0x800F0831: .NET Framework Install Fails During Upgrade
Setup error 0x800F0831 broke an in-place upgrade from SQL Server 2014 to SQL Server 2016. It is the hex form of exit code -2146498511. The CBS log showed store corruption with a missing package, and installing that package fixed the upgrade.