---
id: f128ab1a-9a3b-42d0-a70d-ae2b02830ced
---

# Database Offline (SQLServer)
---

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.

### Parameters
```shell
# Environment Variables

export SQL_SERVER_SERVICE_NAME="PLACEHOLDER"

export PORT_NUMBER="PLACEHOLDER"

export SERVER_NAME="PLACEHOLDER"

export INSTANCE_NAME="PLACEHOLDER"

export DATABASE_PASSWORD="PLACEHOLDER"

export DATABASE_USERNAME="PLACEHOLDER"

export DATABASE_NAME="PLACEHOLDER"
```

## Debug

### Check if the SQL Server service is running
```shell
Get-Service -Name ${SQL_SERVER_SERVICE_NAME}
```

### Check the connection to the server
```shell
Test-NetConnection -ComputerName ${SERVER_NAME} -Port ${PORT_NUMBER}
```

### Check if the database is online
```shell
Invoke-Sqlcmd -Query "SELECT name, state_desc FROM sys.databases" -ServerInstance ${SERVER_NAME}\${INSTANCE_NAME}
```

### Check the SQL Server error log for any issues
```shell
Get-EventLog -LogName Application -Source MSSQLSERVER | Where-Object {$_.EntryType -eq "Error"}
```

### Restart the SQL Server service
```shell
Restart-Service -Name ${SQL_SERVER_SERVICE_NAME} -Force
```

### Database configuration issues: Incorrect configuration of the SQLServer database can cause it to go offline. This could be due to changes made to the database that are not compatible with its current configuration.
```shell


#!/bin/bash



# Set variables

DB_NAME=${DATABASE_NAME}

DB_USERNAME=${DATABASE_USERNAME}

DB_PASSWORD=${DATABASE_PASSWORD}



# Check if the SQL Server service is running

if (( $(sc query MSSQLSERVER | grep "STATE" | wc -l) > 0 )); then

    echo "SQL Server service is running"

else

    echo "SQL Server service is not running"

fi



# Check if the database is online

sqlcmd -S ${SERVER_NAME} -U $DB_USERNAME -P $DB_PASSWORD -Q "SELECT name, state_desc FROM sys.databases WHERE name = '$DB_NAME';"



# Check for any error logs related to the database

Get-EventLog -LogName Application -Source MSSQLSERVER | Select-String -Pattern "$DB_NAME"



# Check for any recent changes made to the database

sqlcmd -S ${SERVER_NAME} -U $DB_USERNAME -P $DB_PASSWORD -Q "SELECT create_date, modify_date FROM sys.databases WHERE name = '$DB_NAME';"


```

## Repair

### Restart the SQLServer database service to see if it can recover from the outage. This step is only recommended if the cause of the outage is unclear or if the service is not responding.
```shell


@echo off



set serviceName=${NAME_OF_THE_SQLSERVER_DATABASE_SERVICE}



echo Stopping %serviceName%...

net stop %serviceName%



echo Starting %serviceName%...

net start %serviceName%



echo %serviceName% restarted successfully.


```

### Check the server hosting the SQLServer database to ensure that it is running correctly and all services are operational.
```shell


@ECHO OFF

REM Check the server hosting the SQLServer database to ensure that it is running correctly and all services are operational.



REM Check if the SQLServer service is running

sc query MSSQLSERVER | findstr /i "STATE" | findstr /i "RUNNING" >nul

IF ERRORLEVEL 1 (

    ECHO SQLServer service is not running.

    REM Try to start the service

    sc start MSSQLSERVER

    ECHO SQLServer service has been started.

) ELSE (

    ECHO SQLServer service is running.

)



REM Check if the SQLServer database is online

sqlcmd -S ${SERVER_NAME} -U ${USERNAME} -P ${PASSWORD} -Q "SELECT name, state_desc FROM sys.databases WHERE name = '${DATABASE_NAME}'" | findstr /i "ONLINE" >nul

IF ERRORLEVEL 1 (

    ECHO SQLServer database is not online.

    REM Try to bring the database online

    sqlcmd -S ${SERVER_NAME} -U ${USERNAME} -P ${PASSWORD} -Q "ALTER DATABASE ${DATABASE_NAME} SET ONLINE"

    ECHO SQLServer database has been brought online.

) ELSE (

    ECHO SQLServer database is online.

)



PAUSE


```


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.


This incident type refers to a situation where the Tomcat server's JDBC connection pool usage surpasses its configured limits. This can lead to a shortage of available connections for incoming requests, resulting in slow response times or even server crashes. It is important to monitor and manage the JDBC connection pool usage to prevent such incidents from occurring.


Tomcat High JDBC Connection Pool Usage Incident.

Apache Spark driver failure refers to an incident where the driver program in an Apache Spark cluster fails to execute or crashes during runtime. This can happen due to a variety of reasons such as hardware failure, software bugs, resource constraints, or programming errors. As the driver program is responsible for coordinating the execution of tasks across the cluster, any failure in the driver can result in the entire Spark job failing. This can lead to data loss, processing delays, and impact the overall performance of the Spark cluster.


Spark driver failure incident.

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.


SQL Server database not marked for replication sync.

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 involves a high number of processes being blocked in SQLServer. It may cause delays or errors in database operations and can impact the performance of the system.


High number of processes blocked in SQLServer

```shell
# Environment Variables

export SQL_SERVER_SERVICE_NAME="PLACEHOLDER"

export PORT_NUMBER="PLACEHOLDER"

export SERVER_NAME="PLACEHOLDER"

export INSTANCE_NAME="PLACEHOLDER"

export DATABASE_PASSWORD="PLACEHOLDER"

export DATABASE_USERNAME="PLACEHOLDER"

export DATABASE_NAME="PLACEHOLDER"
```


### Check if the SQL Server service is running

```shell
Get-Service -Name ${SQL_SERVER_SERVICE_NAME}
```

### Check the connection to the server

```shell
Test-NetConnection -ComputerName ${SERVER_NAME} -Port ${PORT_NUMBER}
```

### Check if the database is online

```shell
Invoke-Sqlcmd -Query "SELECT name, state_desc FROM sys.databases" -ServerInstance ${SERVER_NAME}\${INSTANCE_NAME}
```

### Check the SQL Server error log for any issues

```shell
Get-EventLog -LogName Application -Source MSSQLSERVER | Where-Object {$_.EntryType -eq "Error"}
```

### Restart the SQL Server service

```shell
Restart-Service -Name ${SQL_SERVER_SERVICE_NAME} -Force
```

### Database configuration issues: Incorrect configuration of the SQLServer database can cause it to go offline. This could be due to changes made to the database that are not compatible with its current configuration.

```shell


#!/bin/bash



# Set variables

DB_NAME=${DATABASE_NAME}

DB_USERNAME=${DATABASE_USERNAME}

DB_PASSWORD=${DATABASE_PASSWORD}



# Check if the SQL Server service is running

if (( $(sc query MSSQLSERVER | grep "STATE" | wc -l) > 0 )); then

    echo "SQL Server service is running"

else

    echo "SQL Server service is not running"

fi



# Check if the database is online

sqlcmd -S ${SERVER_NAME} -U $DB_USERNAME -P $DB_PASSWORD -Q "SELECT name, state_desc FROM sys.databases WHERE name = '$DB_NAME';"



# Check for any error logs related to the database

Get-EventLog -LogName Application -Source MSSQLSERVER | Select-String -Pattern "$DB_NAME"



# Check for any recent changes made to the database

sqlcmd -S ${SERVER_NAME} -U $DB_USERNAME -P $DB_PASSWORD -Q "SELECT create_date, modify_date FROM sys.databases WHERE name = '$DB_NAME';"


```


### Restart the SQLServer database service to see if it can recover from the outage. This step is only recommended if the cause of the outage is unclear or if the service is not responding.

```shell


@echo off



set serviceName=${NAME_OF_THE_SQLSERVER_DATABASE_SERVICE}



echo Stopping %serviceName%...

net stop %serviceName%



echo Starting %serviceName%...

net start %serviceName%



echo %serviceName% restarted successfully.


```

### Check the server hosting the SQLServer database to ensure that it is running correctly and all services are operational.

```shell


@ECHO OFF

REM Check the server hosting the SQLServer database to ensure that it is running correctly and all services are operational.



REM Check if the SQLServer service is running

sc query MSSQLSERVER | findstr /i "STATE" | findstr /i "RUNNING" >nul

IF ERRORLEVEL 1 (

    ECHO SQLServer service is not running.

    REM Try to start the service

    sc start MSSQLSERVER

    ECHO SQLServer service has been started.

) ELSE (

    ECHO SQLServer service is running.

)



REM Check if the SQLServer database is online

sqlcmd -S ${SERVER_NAME} -U ${USERNAME} -P ${PASSWORD} -Q "SELECT name, state_desc FROM sys.databases WHERE name = '${DATABASE_NAME}'" | findstr /i "ONLINE" >nul

IF ERRORLEVEL 1 (

    ECHO SQLServer database is not online.

    REM Try to bring the database online

    sqlcmd -S ${SERVER_NAME} -U ${USERNAME} -P ${PASSWORD} -Q "ALTER DATABASE ${DATABASE_NAME} SET ONLINE"

    ECHO SQLServer database has been brought online.

) ELSE (

    ECHO SQLServer database is online.

)



PAUSE


```


Database Offline (SQLServer)

Overview

Parameters

Debug

Check if the SQL Server service is running

Check the connection to the server

Check if the database is online

Check the SQL Server error log for any issues

Restart the SQL Server service

Database configuration issues: Incorrect configuration of the SQLServer database can cause it to go offline. This could be due to changes made to the database that are not compatible with its current configuration.

Repair

Restart the SQLServer database service to see if it can recover from the outage. This step is only recommended if the cause of the outage is unclear or if the service is not responding.

Check the server hosting the SQLServer database to ensure that it is running correctly and all services are operational.

Learn more

Related Runbooks

Tomcat High JDBC Connection Pool Usage Incident.

Spark driver failure incident.

SQL Server database not marked for replication sync.

SQL Server Deadlock Incident

Support