SQL Server Versioning Scheme: Year Labels, Internal Build Numbers & Modern Servicing Model (CU / GDR)

▸1. SQL Server Versioning: Marketing Labels vs Internal Engines

In Microsoft SQL Server, marketing branding (e.g. "SQL Server 2025") is distinct from the internal engine version evaluated by query processors and system tables:

Marketing Name	Internal Engine Version	Database Compatibility Level	RTM Baseline Build
SQL Server 2025	v17.0	`170`	`17.0.1000.x` (CU8: `17.0.4075.5`, CU8 + GDR: `17.0.4085.5`)
SQL Server 2022	v16.0	`160`	`16.0.1000.6`
SQL Server 2019	v15.0	`150`	`15.0.2000.5`
SQL Server 2017	v14.0	`140`	`14.0.1000.169`
SQL Server 2016	v13.0	`130`	`13.0.1601.5` (Final: SP3)
SQL Server 2014	v12.0	`120`	`12.0.2000.8` (Final: SP3)

[!NOTE] Microsoft officially states that SQL Server 2025 is the latest major release; there is no SQL Server 2026 release.

[!TIP] A database backup (.bak) can never be restored onto an instance running an older internal build. For example, a backup created on SQL Server 2025 (v17.0) cannot be restored to SQL Server 2022 (v16.0).

▸2. The End of Service Packs & Modern Servicing Model (MSM)

Following SQL Server 2016 SP3, Microsoft abolished the legacy Service Pack (SP) release pipeline:

•Modern Servicing Model (SQL Server 2017, 2022, 2025):

1Cumulative Updates (CU): Published periodically. CUs bundle performance optimizations, bugfixes, and security hotfixes (e.g., SQL Server 2025 CU8 / CU10).
2General Distribution Releases (GDR): Security-only targeted patches issued strictly for critical CVE mitigations without pulling in broad codebase changes.

text

          ┌───────────────────────────────────────────────┐
          │      SQL Server 2025 RTM (17.0.1000.x)        │
          └──────────────────────┬────────────────────────┘
                                 │
                 ┌───────────────┴───────────────┐
                 ▼                               ▼
        [ CU Track Baseline ]           [ GDR Track Baseline ]
        e.g., CU/GDR (17.0.4085)        e.g., GDR (17.0.1145)
       (All bugfixes + CVEs)               (Security patches only)

▸3. T-SQL Build & Patch Level Inspection

Senior DBAs inspect patch level baselines using standard SERVERPROPERTY metadata calls:

sql

SELECT 
    SERVERPROPERTY('MachineName') AS HostMachine,
    SERVERPROPERTY('ServerName') AS InstanceName,
    SERVERPROPERTY('ProductVersion') AS ProductVersion,     -- e.g., 17.0.4085.5
    SERVERPROPERTY('ProductLevel') AS ProductLevel,         -- e.g., RTM
    SERVERPROPERTY('ProductUpdateLevel') AS CULevel,        -- e.g., CU10
    SERVERPROPERTY('ProductUpdateReference') AS KBArticle,  -- e.g., KB5037331
    SERVERPROPERTY('Edition') AS Edition,                   -- e.g., Enterprise Edition (64-bit)
    @@VERSION AS FormattedBanner;

▸4. Enterprise 10-Year Lifecycle (5+5 Policy)

•Mainstream Support (First 5 Years): Feature refinement, functional Cumulative Updates (CUs), and security bulletins.
•Extended Support (Final 5 Years): Strictly security-focused GDR releases. No new functional feature backports.