Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from https://cloud.google.com/sql/docs/sqlserver/replication/replication-lag below:

Replication lag | Cloud SQL for SQL Server

Stay organized with collections Save and categorize content based on your preferences.

This page describes how to troubleshoot and fix replication lag for Cloud SQL read replicas.

Cloud SQL read replicas use

for replication. Changes are written to the transaction log in the primary instance. The primary instance forwards transactions to any secondary replica instances, where the changes are applied. The availability mode used is

.

Replication lag can happen in a few scenarios, such as:

• The primary instance can't send the changes fast enough to the replica.
• The replica can't receive the changes quickly enough.
• The replica can't apply the changes quickly enough.

The first two reasons above can be monitored with the

. The third reason is observed via the

metric. A high

metric means that the replica can't apply replication changes fast enough. These metrics are described in the

section below.

This section suggests some common query and schema optimizations you can make to improve replication performance.

Long-running queries in the replica might block replication for Cloud SQL. You might want to have separate replicas for online transaction processing (OLTP) and online analytical processing (OLAP) purposes and only send long-running queries to the OLAP replica.

Data definition language (DDL) commands, such as ALTER TABLE and CREATE INDEX, can cause replication lag in the replica due to exclusive locks. To avoid lock contention, consider scheduling DDL execution during times when the query load is lower on the replicas.

Additionally, DDL statements such as

,

, and

can cause replication lag due to the large number of transaction log records that these statements can generate.

If a read replica is receiving too many queries, replication could be blocked. Consider splitting the reads among multiple replicas to reduce the load on each one.

To avoid query spikes, consider throttling replica read queries in your application logic or in a proxy layer if you use one.

If there are spikes of activity on the primary instance, consider spreading out updates.

Consider sharding the primary database vertically (or horizontally) to prevent one or more lagging tables from holding back all the other tables.

You can use the replica_lag and network_lag metrics to monitor replication lag and identify whether the cause of the lag is in the primary database, the network, or the replica.

The number of seconds that the replica's state is lagging behind the state of the primary instance. This is the difference between the timestamp of the last redone log record on the secondary and the timestamp of the last sent log record on the primary.

The difference between the timestamp of the last received log entry on the replica and the last sent log entry on the primary.

To verify that replication is working, check the value of the

metric on the primary instance. If the state is

, then replication is healthy.

• Promote replicas for regional migration or disaster recovery

Except as otherwise noted, the content of this page is licensed under the Creative Commons Attribution 4.0 License, and code samples are licensed under the Apache 2.0 License. For details, see the Google Developers Site Policies. Java is a registered trademark of Oracle and/or its affiliates.

Last updated 2025-08-14 UTC.

[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Hard to understand","hardToUnderstand","thumb-down"],["Incorrect information or sample code","incorrectInformationOrSampleCode","thumb-down"],["Missing the information/samples I need","missingTheInformationSamplesINeed","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-08-14 UTC."],[],[]]

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4