• Interests: SQL Server Performance and Code-Quality

SQLServerCentral Article

The Fundamentals of SQL Server Replication by Sebastian Meine

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 implemen­tation of such a requirement.

2 (7)

You rated this post out of 5. Change rating

2013-09-30

6,577 reads

Blogs

How to: Regain SysAdmin Access to a SQL Server Instance Without the SA Password

By

Hello, reader! Today, I’m going to walk you through a scenario that many DBAs...

Secure Your SQL Estate: Best Practices for Azure SQL Security

By

The Castle and the Keys Imagine your Azure SQL environment as a sprawling digital...

The Book of Redgate: Meetings

By

I think we might have forgotten this a bit, but on one of the...

Read the latest Blogs

Forums

MySQL 5.6 not writing any logs

By Forum Researcher

We are using MySQL version 5.6 in our Windows Server 2012 R2 environment. We...

How to resolve issue of custom Audit log table containing incorrect data?

By Kevin8

We have created a parent table, child table & Audit log table in SQL...

Change Tracking Default Retention

By Steve Jones - SSC Editor

Comments posted to this topic are about the item Change Tracking Default Retention

Visit the forum

Question of the Day

Change Tracking Default Retention

I run this command on my SQL Server 2022 database:

ALTER DATABASE AdventureWorks2017 SET CHANGE_TRACKING = ON;
What is the default data retention period?

See possible answers