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-24 (first published: 2014-11-11)
1,088 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,715 reads
By Steve Jones
semaphorism – n. a conversational hint that you have something personal to say on...
This week I was at PASS Data Community Summit in Seattle, and I attended...
By James Serra
(This is the third post in a three-part series on how AI is changing...
Comments posted to this topic are about the item Pay for Performance, which is...
Comments posted to this topic are about the item Helping an English Student with...
I have a table, dbo.bittest, where I am testing an application response. This has this structure:
CREATE TABLE [dbo].[BitTest] ( [insertdate] [datetime] NULL CONSTRAINT [DF__BitTest__insertd__300F11AC] DEFAULT (getdate()), [a] [bit] NULL ) ON [PRIMARY] GOMy application runs this code:
INSERT dbo.BitTest
(
insertdate,
a
)
VALUES
(DEFAULT, 'true')
GO
See possible answers