Interests: SQL Server Performance and Code-Quality

The Fundamentals of SQL Server Replication by Sebastian Meine

by Sebastian-Meine

SQLServerCentral.com

books

Many of my clients need to make data that lives on one server available on another server. There are many reasons for such a requirement. You might want to speed up cross-server queries by providing a local copy of the data. Or you might want to make the data available to resource intensive reporting queries without impacting the OLTP load, maybe even with an intentional delay so you're always reporting against complete days only. Finally, you might be looking to implement high availability. In all these situations, SQL Server Replication is a viable option to look at when planning for the implementation of such a requirement.

★ ★ ★ ★ ★ ★ ★ ★ ★ ★

(7)

You rated this post out of 5. Change rating

2013-09-30

6,726 reads

Discuss

All authors

Read the latest Blogs

Visit the forum

Question of the Day

The Read Committed Snapshot Isolation behaviour

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;
go

Then, 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

The Fundamentals of SQL Server Replication by Sebastian Meine

Blogs

Why Optimize CPU for RDS SQL Server is a game changer

Performance tuning KubeVirt for SQL Server

T-SQL Tuesday #193 – A Note to Your Past, and a Warning from Your Future

Forums

Refactoring SQL Code

The Read Committed Snapshot Isolation behaviour

Working with JSON/JSONB Data in PostgreSQL using Python

Question of the Day

The Read Committed Snapshot Isolation behaviour