System-versioned ledger tables: things you can’t do
This is the third post in the series about system-versioned ledger tables, a new feature introduced in Azure SQL Database. You can read Part 1 and Part 2 if...
2021-10-13
23 reads
This is the third post in the series about system-versioned ledger tables, a new feature introduced in Azure SQL Database. You can read Part 1 and Part 2 if...
2021-10-13
23 reads
I’ve had the privilege of presenting all over the world about temporal tables in SQL Server including the United Kingdom, Canada, and the United States. The theme of the...
2021-10-06
23 reads
In the first post of this series, we learned about a new type of system-versioned table that also works at the database level and introduces a mechanism that demonstrates...
2021-09-29
56 reads
Choosing the right typeface for your presentation (or for that matter anything you create that contains words) is fraught. In a previous post I wrote about the difference between...
2021-09-22
44 reads
As long-time readers of this blog know, I’m a big fan of temporal tables, also known as system-versioned temporal tables. Until recently, temporal tables were synonymous with system-versioned tables,...
2021-09-15
272 reads
Right off the top here, I must note that the term “dead man’s switch” is archaic, so for the rest of this post I’ll refer to it as “operator...
2021-09-08
42 reads
I have previously written about accessibility in video captions, presentation slides, and disabilities, and I thought I should expand on the latter topic as it relates to typefaces, or...
2021-09-01
34 reads
During routine maintenance on a customer’s production server, I discovered that they have one table consuming 40% of the storage in their database. That table contains just under 10...
2021-08-25
61 reads
I may be completely off base here, but I’ve noticed a correlation between folks who use Amazon Web Services and their understanding that once you scale up a service...
2021-08-18
97 reads
This coming Friday the 13th (August 2021) is the first ever Dativerse virtual conference, hosted by our DataGrillen friends William and Benjamin. According to their site: We try to...
2021-08-11
14 reads
By Steve Jones
Superheroes and saints never make art. Only imperfect beings can make art because art...
One feature that I have been waiting for years! The new announcement around optimize...
Following on from my last post about Getting Started With KubeVirt & SQL Server,...
Comments posted to this topic are about the item The AI Bubble and the...
Hi, in a simple oledb source->derived column->oledb destination data flow, 2 of my...
hi, i noticed the sqlhealth extended event is on by default , and it...
I am currently working with Sql Server 2022 and AdventureWorks database. First of all, let's set the "Read Committed Snapshot" to ON:
use master; go alter database AdventureWorks set read_committed_snapshot on with no_wait; goThen, from Session 1, I execute the following code:
--Session 1 use AdventureWorks; go create table ##t1 (id int, f1 varchar(10)); go insert into ##t1 values (1, 'A');From another session, called Session 2, I open a transaction and execute the following update:
--Session 2 use AdventureWorks; go begin tran; update ##t1 set f1 = 'B' where id = 1;Now, going back to Session 1, what happens if I execute this statement?
--Session 1 select f1 from ##t1 where id = 1;See possible answers