---
title: "DB24 | Docs - Central Sync"
url: https://db24.ai/docs/central-sync
description: "DB24 Central is the central DB24 service that publishes reference data to customer environments."
lang: en
---

# Central Sync

Last updated: October 15, 2026

## DB24 Central Sync

## Introduction

DB24 Central is the central DB24 service that publishes reference data to customer environments. Central Sync is the connection between your local DB24 Datastore and DB24 Central.

Keep your environment up to date by connecting to DB24 Central. When Central Sync is enabled, your Datastore periodically contacts DB24 Central to:

- Receive updated **SQL Server build and patch data**, so lifecycle and patching reports always reflect the latest available updates from Microsoft.
- Receive the latest **DB24 product version information**, so you can see when a newer DB24 release is available.

No customer data leaves your environment as part of these checks — the sync downloads reference data and reports basic health/version status.

Central Sync is configured under **Settings → Organization → Central Sync** and requires the **Admin** role.

* * *

## How It Works

The Central Sync toggle controls two background tasks performed by the DB24 Datastore worker:

- **Ping** — a lightweight periodic heartbeat to DB24 Central that verifies connectivity and exchanges version status.
- **Delta check** — periodically downloads the reference data that has changed since the last check (SQL Server builds, patches and DB24 product versions).

Both are enabled and disabled together by the toggle.

* * *

## Network requirement: DB24 Central connectivity

The DB24 worker service must be able to reach DB24 Central over HTTPS.

| Direction | Destination | Protocol / Port |
| --- | --- | --- |
| Outbound | `db24-central-prod-api.azurewebsites.net` | HTTPS / TCP 443 |

If this traffic is blocked, the worker service cannot communicate with DB24 Central.

> **Note:** Azure App Service IP addresses can change. Use a hostname/FQDN-based firewall rule rather than whitelisting specific IP addresses.

* * *

## Enabling Central Sync

- **Central Sync (ON/OFF)**
  Switch Central Sync on or off. The change is applied immediately; there is no separate save step. The portal confirms with `Central Sync enabled` or `Central Sync disabled`.

We recommend keeping Central Sync enabled to ensure your environment has the most accurate and up-to-date information.

* * *

## Sync Status

The status panel shows the most recent activity:

| Field | Meaning |
| --- | --- |
| **Last ping** | When the Datastore last contacted DB24 Central. `Never` means no contact has been made yet. |
| **Last ping status** | Whether the most recent ping succeeded or failed. Shown as `Successful` or `Failed`. |
| **Last delta check** | When reference data was last checked for updates. `Never` means no delta check has completed yet. |

Timestamps are shown as `yyyy-MM-dd HH:mm`. A recent successful ping together with a recent delta check means the environment is fully in sync.

* * *

## Where Central Sync Data Is Used

- **Dashboard – Central Sync widget**
  Shows **Status** (`Enabled` / `Disabled`), **Last Ping** and **New Version** (`Up to date`, or the available DB24 version). If the most recent ping failed the widget shows `Last Central Sync attempt failed`. When a newer DB24 release is available it shows `v<version> is available for download`.
- **Lifecycle and Patching reports**
  These reports rely on the synced SQL Server build and patch data. When the data has not been refreshed for more than two months, a warning is shown:
  - With Central Sync enabled: `DB24 Central Sync is enabled, but SQL Server Build & Patch data hasn't refreshed since <date>. The information below may be outdated.`
  - With Central Sync disabled: `SQL Server Build & Patch information may be outdated (last synced: <date>). Enable DB24 Central Sync to automatically receive the latest SQL Server releases so we can give accurate advice.`
  - For instances running a release not in the catalog: `We don't have SQL Server Build & Patch information for: <instances>. They may be running a release that is not yet in our catalog.`
  Admins get a link **Go to Central Sync settings**. Other users are asked to contact their administrator to enable DB24 Central Sync.
- **New DB24 version notice**
  When a newer DB24 product version has been synced, the portal navigation shows `DB24 v<version> is available!` with the release date, release notes and a download link.

* * *

## When Sync Is Disabled

Disabling Central Sync stops all communication with DB24 Central. The environment keeps working, but:

- SQL Server build and patch information becomes stale, so patching and lifecycle reports may miss newly released updates.
- You will not be notified about new DB24 product versions.

We recommend keeping Central Sync enabled unless the environment must be fully isolated.

* * *

## Troubleshooting

- **Last ping status is Failed** — the Datastore could not reach DB24 Central. Check that the Datastore server has outbound internet access and that no firewall or proxy blocks the connection.
- **Last ping shows Never** — the sync has not run yet. Verify that the toggle is on and that the DB24 Datastore worker service is running.
- **Delta check is much older than the last ping** — the heartbeat works but data downloads fail; check the Datastore worker logs under Organization → Logs.
* * *

## Good to Know

- Viewing the sync status requires the **Member** role. Changing the toggle requires the **Admin** role.
- The **Last ping**, **Last ping status** and **Last delta check** values are written by the DB24 Datastore worker. The portal only displays them.
- The Central Sync toggle is shown as **ON** only when both the ping and the delta check are enabled.

## Related Documentation

- DB24 Overview (https://db24.ai/docs/overview) - Platform introduction
- LDAP Authentication (https://db24.ai/docs/ldap-authentication) - Directory sign-in for DB24 Portal users

Previous Notifications: https://db24.ai/docs/notifications
Next Change Tracking: https://db24.ai/docs/change-tracking

## Structured data

```json
{
  "@context": "https://schema.org",
  "@type": "Organization",
  "name": "DB24",
  "url": "https://db24.ai",
  "logo": "https://db24.ai/logo.png",
  "description": "SQL Server on autopilot. DB24 monitors, backs up and documents SQL Server automatically for organisations that run it without a dedicated DBA.",
  "contactPoint": {
    "@type": "ContactPoint",
    "contactType": "sales",
    "email": "sales@db24.ai"
  },
  "sameAs": [
    "https://www.linkedin.com/company/db24"
  ]
}
```