In this book, Kalen Delaney explains how the 2016 In-Memory OLTP engine works, how it stores and manipulates data, and how, even with all data stored in memory and no locking or latching, it can still guarantee the ACID properties of all transactions.
2023-04-28 (first published: 2014-11-11)
962 reads
Your application can have impeachable indexes and queries, but they won't help you if you can't get to your data because another application has it locked. That's why every DBA and developer must understand SQL Server concurrency and how to troubleshoot excessive blocking or deadlocking. Kalen Delaney's book is your guide.
2012-10-02
3,628 reads
By Brian Kelley
In information security (INFOSEC), there several foundational concepts and principles. One of the ones...
By Steve Jones
the standard blues– n. the dispiriting awareness that the twists and turns of your...
By Chris Yates
A brief introduction to the tool and its advantages for database migrations DevOps is...
I'm tracing activity on one database and would like to include the client_app_name in...
select Custno, Addr1, City, Res_Phone, Bus_Phone, Fax_Phone, Marine_Phone, Pager_Phone, Other_Phone, email1, email2 from customer...
I'm only processing 50,000 records not everything from the Table where there are 250,00...
I want to mark a transaction in the log as a recovery point. How do I do this in my code if I use the transaction, myTran?
See possible answers