With SQL Server 2012 Microsoft introduced the AlwaysOn Availability Group feature, and since then many changes and improvements have been made. This article is an update to another article, and will cover the prerequisites and steps for installing AlwaysOn in your SQL Server 2019 environment. Prerequisites Before implementing your AlwaysOn Availability Group (AG), make sure […]
2025-11-25
89 reads
Is your SQL database log file too big? Maybe it is. But maybe it’s not. When log files keep growing and appear to be too big some might suggest switching to Simple recovery, shrinking the log file, and switching back to Full recovery. While this will work to shrink the file and free up disk […]
2022-02-16
30,833 reads
Keep column headers visible while scrolling down the page of SSRS reports.
2021-03-12 (first published: 2019-01-07)
8,547 reads
With SQL Server 2012 Microsoft introduced the AlwaysOn Availability Group feature, and since then many changes and improvements have been made. This article is an update to another article, and will cover the prerequisites and steps for installing AlwaysOn in your SQL Server 2019 environment. Prerequisites Before implementing your AlwaysOn Availability Group (AG), make sure […]
2020-12-07
151,199 reads
In part 2 of this article, learn how you can move incremental changes in a SQL Server table using Azure Data Factory.
2020-01-21
2,619 reads
Learn how to get started uploading data from a SQL Server to Azure Blob Storage.
2019-12-30
4,171 reads
2019-03-29 (first published: 2017-12-04)
5,774 reads
Whoever creates an AlwaysOn group is, by default, the owner of the endpoint. This is generally not a problem…unless that person leaves the company and you need to delete the login.
2018-10-25
15,398 reads
2017-07-04 (first published: 2015-12-14)
10,756 reads
2016-12-05
12,180 reads
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,...
By DesertDBA
I haven’t posted in a while (well, not here at least since I’ve been...
Comments posted to this topic are about the item Refactoring SQL Code, which is...
Comments posted to this topic are about the item The Read Committed Snapshot Isolation...
Comments posted to this topic are about the item Working with JSON/JSONB Data in...
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