SQL Server Error 3169

Error number

3169

Severity

16 (user-correctable error)

State

Not documented by Microsoft (not reproduced here)

Product

Microsoft SQL Server Database Engine

Versions

All supported SQL Server versions (2016 to 2025), Azure SQL Managed Instance

Category

Backup & Restore

Last reviewed

23 October 2026

What it means

Error 3169 means the backup was taken on a newer SQL Server version than the one you are restoring to, and backups can never be restored to an older version.

Each SQL Server release has an internal database format (the database version, for example 998 on SQL Server 2025 RTM). A restore can upgrade a database from an older format to the server's own, but nothing can convert a newer format back to an older one. When the backup header shows a database version higher than this server supports, RESTORE stops with 3169 and then Msg 3013 ... RESTORE DATABASE is terminating abnormally. In the message, NNN is the version stored in the backup and MMM is what this server supports; earlier versions print product build numbers such as 15.00.2000 (SQL Server 2019) instead.

The compatibility level of the source database does not matter: a SQL Server 2022 database at compatibility level 130 still has the SQL Server 2022 file format and cannot be restored on SQL Server 2016. Azure SQL Managed Instance follows the same rule through its update policy: Microsoft documents that only instances on the SQL Server 2022 or SQL Server 2025 update policy produce backups that SQL Server 2022 or SQL Server 2025 can restore, and that backups from the Always-up-to-date policy restore only to other Always-up-to-date instances.

Common causes

• A backup from a newer SQL Server release (for example 2022) is being restored on an older one (for example 2019 or 2016), often a developer laptop or a test server that was never upgraded.
• A vendor or another team sent a backup taken on their newer server.
• A copy-only backup from Azure SQL Managed Instance on the Always-up-to-date update policy, or on a newer update policy than your SQL Server version, is being restored to SQL Server.
• The restore was pointed at the wrong instance on a machine that runs several SQL Server versions side by side.

Diagnose it

Read-only These queries only read metadata and dynamic management views. They do not change data, permissions or configuration, so they are safe to run first.

SELECT @@SERVERNAME AS server_name,
       SERVERPROPERTY('ProductVersion') AS product_version,
       SERVERPROPERTY('ProductMajorVersion') AS major_version,
       DATABASEPROPERTYEX(N'master', 'Version') AS internal_db_version;

SELECT TOP (10) database_name, backup_finish_date,
       software_major_version, software_minor_version, software_build_version,
       database_version, compatibility_level
FROM msdb.dbo.backupset
ORDER BY backup_finish_date DESC;

How to fix it

Each fix is labelled with what it changes. Try read-only checks and the least invasive fix first, and test changes outside production.

Examples

Restoring a newer backup on an older server

Shown as documented by Microsoft; not reproduced here, because the lab runs SQL Server 2025 and has no newer engine to produce such a backup. NNN and MMM stand for the two internal database versions.

-- On an older SQL Server, restoring a backup taken on a newer one
RESTORE DATABASE AppDb
FROM DISK = N'D:\Backups\AppDb_from_newer_server.bak';

The database was backed up on a server running database version NNN. That version is incompatible with this server, which supports version MMM. Either restore the database on a server that supports the backup, or use a backup that is compatible with this server.
Msg 3013, Level 16, State 1, Line 2
RESTORE DATABASE is terminating abnormally.

How to prevent it

Keep development, test and disaster recovery servers on the same or a later SQL Server version than production, and upgrade them first. Before anyone sends you a backup, agree the version it will be restored on.

For Azure SQL Managed Instance, choose the update policy with your restore needs in mind: Microsoft notes that moving to a newer policy upgrades the database format permanently.

Common questions

Learn more on CodeWithSQL

• Working with large databases

Official documentation

• MSSQLSERVER_3169 (Microsoft Learn)
• Update policy: Azure SQL Managed Instance
• RESTORE statements: HEADERONLY (Transact-SQL)

Last technically reviewed 23 October 2026; examples and diagnostics run on SQL Server 2025 (17.0.1145.4). Message text checked against the engine's sys.messages catalogue.