Practical articles about ClickHouse, SQL Server, analytics architecture, performance, migration, and database operations.
Query previous row versions with temporal tables while distinguishing system time, business effective dates, transaction boundaries, and audit requirements.
Read articleCreate a bounded Extended Events capture for slow completed requests, verify duration units, inspect event files, and distinguish evidence from assumptions.
Read articleCompare ROW_NUMBER and OUTER APPLY for latest-row queries, preserve customers with no rows, and choose a deterministic tie-breaking rule.
Read articleUnderstand heap row movement, measure forwarded records with a scoped inspection, and choose between rebuilding storage and changing the table design.
Read articleA long list of blocked sessions can make every query look guilty. Usually one transaction near the front of the chain controls the incident's duration and impact.
Read articleUnderstand why NOT IN can return no rows, choose a correct anti-join, and test NULL, duplicates, and predicate placement before tuning performance.
Read articleTurn daily events into reliable activity streaks, handle duplicate dates, and avoid confusing adjacent events with overlapping intervals.
Read articleA successful backup job proves that SQL Server wrote a backup stream. It does not prove that the organization can restore the right databases, keys, log chain, and dependencies on time.
Read articleSeparate connection, command, and lock timeouts, investigate cancellation, and design retries that do not duplicate writes after an uncertain response.
Read articleChoose linguistic search deliberately, configure language and indexing, return ranked results, and handle freshness, query syntax, and tenant filtering.
Read articleDefine duplicate identity and survivor rules, preview deterministic ROW_NUMBER results, and prevent duplicates from returning after cleanup.
Read articleAn Availability Group can show healthy replicas while recovery objectives remain at risk. Queue growth, listener behavior, backup placement, and failover readiness require explicit monitoring.
Read article