2025-10-22
1,534 reads
2025-10-22
1,534 reads
I don’t think I’ve ever had a great impression of Azure SQL Database as a place for production applications. In its early days, it was missing several important features (like data compression). While that hole has been plugged, there are still other limitations and differences you should be aware o
2024-02-02
Learn about how SQL Server uses locks when modifying data and how data is committed to a database after data changes.
2023-10-23
2023-10-09
486 reads
In any database, mismanagement of transactions often leads to contention and performance problems in systems that have many users. As the number of users that access the data increases, it becomes important to have applications that use transactions efficiently. This guide describes the locking and row versioning mechanisms the SQL Server Database Engine uses to ensure the physical integrity of each transaction and provides information on how applications can control transactions efficiently.
2022-10-05
This article isn’t about the act of lock escalation itself, which is already well documented and generally well understood. Some myths (like row locks escalating to page locks) persist, but challenging those yet again probably wouldn’t change much.
2022-09-19
2021-01-04
656 reads
2020-11-02
525 reads
Learn about the impact of locking and blocking in sessions through some demonstrations of different types of actions.
2020-06-11
8,350 reads
2020-02-20
697 reads
A RAG pipeline that answers questions in the demo is not the same thing...
By Steve Jones
“A multitude of bad ideas is necessary for one good idea” – from Excellent...
Yesterday I gave a talk for MSSQLTips called “Building a DBA Agent for Your...
Telp/Wa 62 821-8200-233 Jl. Raya Cilandak KKO No.9, RT.1/RW.5, Ragunan, Ps. Minggu, Kota Jakarta...
Telp/Wa 62 821-8200-203 Gedung Perkantoran Hijau Arkadia, Tower C - Ground Floor, unit C103,...
Telp/Wa 62 821-8200-174 Menara Karya, Jl. H. R. Rasuna Said Ground floor, RT.1/RW.2, Kuningan,...
Which number will the COUNT() return after executing the following statements:
DROP TABLE IF EXISTS #test; CREATE TABLE #test (id INT) INSERT INTO #test (id) SELECT * FROM GENERATE_SERIES(1, 3) AS gs ; ALTER TABLE #test ADD flag BIT CONSTRAINT DF_#test_flag DEFAULT 0; go UPDATE #test SET flag = 0 WHERE id = 1 UPDATE #test SET flag = 1 WHERE id = 2 INSERT INTO #test (id) VALUES (4) SELECT COUNT(*) FROM #test AS t WHERE flag = 0See possible answers