Diagnosing and Resolving TempDB Contention in SQL Server
A diagnostic guide to identifying and resolving TempDB contention in SQL Server using wait statistics, I/O monitoring, and targeted configuration changes.
ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
A diagnostic guide to identifying and resolving TempDB contention in SQL Server using wait statistics, I/O monitoring, and targeted configuration changes.
SQL Server Agent Alert Configuration for Critical Event Filtering Without Missing Application Issues SQL Server Agent provides severity-based alerting system that can be configured to trigger on specific error levels (0-24) to reduce notification noise from informational messages. The sp_add_alert system stored procedure supports optional delay between respo
Hibernate ORM and SQL Server Interoperability When integrating Java applications using Hibernate ORM with Microsoft SQL Server, the framework relies on the configured Dialect to generate pagination T-SQL. For SQL Server 2012 and later, Hibernate typically utilizes the OFFSET-FETCH clause via setFirstResult and setMaxResults . However, older versions of SQL S
Comparing Online ADD NOT NULL with DEFAULT versus Full Table Rebuild When a small application requires a new column that cannot be null and must be initialized with a constant, two documented paths exist in SQL Server 2019 and later: an online ALTER TABLE that attempts to add the column without rebuilding the entire table, and a traditional rebuild that lock
Lock Escalation Behavior Microsoft SQL Server utilizes lock escalation to manage memory overhead by converting numerous fine-grained locks (row, key, or page) into a single table-level lock. While this reduces the resource cost of lock management, it can introduce significant latency in multi-session environments by transforming short-duration row waits into
The goal is to understand whether a page-level restore using RESTORE WITH PAGE automatically marks the repaired pages as clean, or if the pages remain listed in msdb.dbo.suspect_pages until a manual DBCC CHECKDB is executed. Constraints include version‑dependent behavior: in some releases the suspect_pages entry persists after RESTORE WITH PAGE, requiring an
Goal Configure SQL Server Agent alerts to deliver actionable notifications without overwhelming operators. Constraints SQL Server Agent alerts use sp_add_alert with severity or performance‑counter thresholds, but lack native rate‑limit or deduplication. Operators are defined in msdb.dbo.sysoperators and require Database Mail profiles; permission boundaries a
I'm planning a schema migration on SQL Server (Enterprise Edition, recent version) that alters a large, heavily queried table. Two documented approaches are on the table: an online index rebuild with ONLINE = ON , which permits concurrent DML, or an offline change wrapped in BEGIN TRANSACTION so the DDL can roll back if anything fails mid-deployment. The ten
Context SQL Server 2016 introduced online ALTER COLUMN for certain data type changes, allowing concurrent reads and writes during the operation. For incompatible conversions (e.g., int to bigint ), a data-copy phase occurs followed by a brief schema modification (Sch-M) lock to switch metadata. Unresolved behavior The documentation does not specify a maximum