---
id: 9e6138fb-6ff9-4328-ba61-79fa55ac59d1
---

# SQL Server database not marked for replication sync.
---

This incident type refers to a situation where a SQL Server database is not marked for replication sync, which means it may not be synced with its backup. This can result in data loss or inconsistencies between the primary database and its backup. It is important to address this issue promptly to ensure data integrity and prevent potential downtime or data loss.

### Parameters
```shell
# Environment Variables

export SERVER_NAME="PLACEHOLDER"

export REPLICA_NAME="PLACEHOLDER"

export BACKUP_NAME="PLACEHOLDER"

export DATABASE_NAME="PLACEHOLDER"

export SQL_SERVER_SERVICE_NAME="PLACEHOLDER"

export HOST_NAME_OR_IP_ADDRESS="PLACEHOLDER"

export PORT_NUMBER="PLACEHOLDER"
```

## Debug

### Check if SQL Server service is running
```shell
Get-Service -Name MSSQLSERVER
```

### Check the replication status of a database
```shell
sqlcmd -S ${SERVER_NAME} -E -Q "SELECT name, is_published, is_subscribed, is_merge_published, is_distributor FROM sys.databases"
```

### Check if the database is sync with the backup
```shell
sqlcmd -S ${SERVER_NAME} -E -Q "SELECT [name], [is_sync_with_backup] FROM sys.databases"
```

### Check replication monitor for errors
```shell
sqlcmd -S ${SERVER_NAME} -E -Q "SELECT * FROM [distribution].[dbo].[MSrepl_errors]"
```

## Repair

### Next Step
```shell
@echo off
```

### Next Step
```shell
set DATABASE_NAME=${DATABASE_NAME}

set BACKUP_NAME=${BACKUP_NAME}

set REPLICA_NAME=${REPLICA_NAME}
```

### Next Step
```shell
:: check replication settings

sqlcmd -S ${SERVER_NAME} -d %DATABASE_NAME% -Q "exec sp_helpdb %DATABASE_NAME%" | findstr /i "%REPLICA_NAME%"
```

### Next Step
```shell
if %errorlevel% == 0 (

    echo Replication is enabled for %DATABASE_NAME%.

    goto :end

) else (

    echo Replication is not enabled for %DATABASE_NAME%. Enabling replication...

)
```

### Restart the SQL Server service to see if it resolves the issue.
```shell


@echo off



REM Stop the SQL Server service

net stop ${SQL_SERVER_SERVICE_NAME}



REM Start the SQL Server service

net start ${SQL_SERVER_SERVICE_NAME}



echo SQL Server service restarted successfully.


```

### Check the database replication settings and ensure that it is set to sync with its backup.
```shell


@echo off

set database=${DATABASE_NAME}



echo Checking replication settings for %database%...

sqlcmd -S ${SERVER_NAME} -d %database% -Q "SELECT name, is_published, is_subscribed, is_merge_published, is_distributor FROM sys.databases WHERE name='%database%';"



echo Setting replication to sync with backup...

sqlcmd -S ${SERVER_NAME} -d %database% -Q "EXEC sp_replicationdboption @dbname = '%database%', @optname = N'publish', @value = N'true';"



echo Replication settings updated successfully.


```

### Check the network connectivity and ensure that it is not blocking the replication process.
```shell


@echo off



set host=${HOST_NAME_OR_IP_ADDRESS}

set port=${PORT_NUMBER}



echo Testing network connectivity...

ping %host% -n 1 -w 1000 >nul



if errorlevel 1 (

    echo Network connectivity issue detected.

    echo Attempting to resolve issue...

    netsh advfirewall firewall add rule name="Allow SQL Server replication" dir=in action=allow protocol=TCP localport=%port%

    echo Firewall rule added to allow SQL Server replication.

) else (

    echo Network connectivity is working properly.

)



pause


```

This incident type refers to a situation where a SQL Server database is not marked for replication sync, which means it may not be synced with its backup. This can result in data loss or inconsistencies between the primary database and its backup. It is important to address this issue promptly to ensure data integrity and prevent potential downtime or data loss.


Tomcat Servlet Session Replication Failures occur when a Tomcat server fails to replicate session data between instances. This can result in users losing their session data or being redirected to a different instance, causing disruption to the application's functionality.


Tomcat Servlet Session Replication Failures.

A SQL Server deadlock incident occurs when two or more processes are blocked and waiting on each other to release a resource. This results in a situation where none of the processes can continue executing, causing a system slowdown or complete system failure. The incident requires immediate attention from a software engineer to identify and resolve the issue.


SQL Server Deadlock Incident

This incident type refers to a situation where a SQLServer database goes offline, which can potentially cause disruptions in software or applications that rely on it. The incident is triggered by a monitoring system that detects the database's state is not available. A prompt response is necessary to resolve the issue and prevent any adverse impact on the system.


Database Offline (SQLServer)

This incident type refers to an issue with Redis replication, which means that there is a problem with the synchronization of data between Redis instances. This issue could impact the availability and performance of the system and may require immediate attention to restore the replication and ensure data consistency. The incident could be caused by various factors, such as network problems, hardware failures, or configuration issues. The incident must be investigated and resolved as soon as possible to avoid any data loss or downtime.


Redis replication broken incident.

The Redis missing master incident occurs when the Redis cluster has no node marked as master. This can cause problems with the Redis service and may result in service disruptions or failures. It is important to address this issue promptly to ensure the smooth operation of the Redis service.


Redis missing master incident

```shell
# Environment Variables

export SERVER_NAME="PLACEHOLDER"

export REPLICA_NAME="PLACEHOLDER"

export BACKUP_NAME="PLACEHOLDER"

export DATABASE_NAME="PLACEHOLDER"

export SQL_SERVER_SERVICE_NAME="PLACEHOLDER"

export HOST_NAME_OR_IP_ADDRESS="PLACEHOLDER"

export PORT_NUMBER="PLACEHOLDER"
```


### Check if SQL Server service is running

```shell
Get-Service -Name MSSQLSERVER
```

### Check the replication status of a database

```shell
sqlcmd -S ${SERVER_NAME} -E -Q "SELECT name, is_published, is_subscribed, is_merge_published, is_distributor FROM sys.databases"
```

### Check if the database is sync with the backup

```shell
sqlcmd -S ${SERVER_NAME} -E -Q "SELECT [name], [is_sync_with_backup] FROM sys.databases"
```

### Check replication monitor for errors

```shell
sqlcmd -S ${SERVER_NAME} -E -Q "SELECT * FROM [distribution].[dbo].[MSrepl_errors]"
```


### Next Step

```shell
@echo off
```

### Next Step

```shell
set DATABASE_NAME=${DATABASE_NAME}

set BACKUP_NAME=${BACKUP_NAME}

set REPLICA_NAME=${REPLICA_NAME}
```

### Next Step

```shell
:: check replication settings

sqlcmd -S ${SERVER_NAME} -d %DATABASE_NAME% -Q "exec sp_helpdb %DATABASE_NAME%" | findstr /i "%REPLICA_NAME%"
```

### Next Step

```shell
if %errorlevel% == 0 (

    echo Replication is enabled for %DATABASE_NAME%.

    goto :end

) else (

    echo Replication is not enabled for %DATABASE_NAME%. Enabling replication...

)
```

### Restart the SQL Server service to see if it resolves the issue.

```shell


@echo off



REM Stop the SQL Server service

net stop ${SQL_SERVER_SERVICE_NAME}



REM Start the SQL Server service

net start ${SQL_SERVER_SERVICE_NAME}



echo SQL Server service restarted successfully.


```

### Check the database replication settings and ensure that it is set to sync with its backup.

```shell


@echo off

set database=${DATABASE_NAME}



echo Checking replication settings for %database%...

sqlcmd -S ${SERVER_NAME} -d %database% -Q "SELECT name, is_published, is_subscribed, is_merge_published, is_distributor FROM sys.databases WHERE name='%database%';"



echo Setting replication to sync with backup...

sqlcmd -S ${SERVER_NAME} -d %database% -Q "EXEC sp_replicationdboption @dbname = '%database%', @optname = N'publish', @value = N'true';"



echo Replication settings updated successfully.


```

### Check the network connectivity and ensure that it is not blocking the replication process.

```shell


@echo off



set host=${HOST_NAME_OR_IP_ADDRESS}

set port=${PORT_NUMBER}



echo Testing network connectivity...

ping %host% -n 1 -w 1000 >nul



if errorlevel 1 (

    echo Network connectivity issue detected.

    echo Attempting to resolve issue...

    netsh advfirewall firewall add rule name="Allow SQL Server replication" dir=in action=allow protocol=TCP localport=%port%

    echo Firewall rule added to allow SQL Server replication.

) else (

    echo Network connectivity is working properly.

)



pause


```


SQL Server database not marked for replication sync.

Overview

Parameters

Debug

Check if SQL Server service is running

Check the replication status of a database

Check if the database is sync with the backup

Check replication monitor for errors

Repair

Next Step

Next Step

Next Step

Next Step

Restart the SQL Server service to see if it resolves the issue.

Check the database replication settings and ensure that it is set to sync with its backup.

Check the network connectivity and ensure that it is not blocking the replication process.

Learn more

Related Runbooks

Tomcat Servlet Session Replication Failures.

SQL Server Deadlock Incident

Database Offline (SQLServer)

Redis replication broken incident.

Support