
SQL Server Build Data and API
Download SQL Server build numbers, update names, release dates, and KB links in one file. The public API covers Windows and Linux Database Engine releases and supports filters for version, platform, and servicing branch.
Download SQL Server builds as JSON, CSV, TSV, or Excel
Use the workbook for Excel, CSV or TSV for imports, and JSON when you need the KB and alias lists as arrays. If you import a CSV into Excel, use Data → From Text/CSV with UTF-8 and set the build and file-version columns to Text to preserve the version strings.
SQL Server build API v1 filters and response fields
GET /api/sql-server-builds/v1/builds is public and requires no API key.
| Parameter | Accepted values |
|---|---|
release | 2025, 2022, 2019, 2017, 2016, 2014, 2012, 2008-r2, 2008, 2005, 2000, 7-0, 6-5, 6-0 |
platform | windows, linux |
branch | rtm, cu, cu-gdr, gdr, service-pack, hotfix, preview, other |
format | json (default), csv, tsv, xlsx |
- SQL Server 2022 Windows CUs as JSON
?release=2022&platform=windows&branch=cu - All SQL Server 2022 branches as CSV
?release=2022&format=csv
Filters are optional and combine with AND. An invalid, repeated, or unknown parameter returns HTTP 400. A valid query with no matches returns HTTP 200 and an empty record list or a header-only delimited file.
The JSON response has schemaVersion, revision, checkedAt, detailCheckedAt, and records. A recheck can advance the UTC timestamps even when the build rows stay the same. For conditional downloads, pass the previous ETag as If-None-Match on the same URL. HTTP 304 means the cached export is still valid.
Each row includes the engine build, platform, aliases, update, service pack, branch, release date, status, KB references, and source URL. File version and missing dates are null in JSON and blank in CSV or TSV. CSV and TSV store the aliases and KB lists as JSON strings inside cells.
Release metadata as JSON returns a releases array with version prefixes, compatibility levels, observed internal database versions, and lifecycle dates.
Match installed SQL Server builds to an inventory
Collect the full ProductVersion and operating system from each instance. Join on platform and normalized build. Include the documented aliases if you have older entries with leading zeroes, and keep unmatched entries for review.
Fetch a release in PowerShell
$uri = 'https://kerteszmihaly.com/api/sql-server-builds/v1/builds?release=2022&platform=windows&branch=cu'
$catalogue = Invoke-RestMethod -Uri $uri
$catalogue.records | Select-Object build, update, releaseDate, statusMatch a local inventory CSV to the build catalogue
Keep one row per instance. This downloads one public catalogue and joins it to your inventory locally.
# instances.csv columns: instance,platform,build
# Use ProductVersion for build and windows or linux for platform.
$catalogue = Invoke-RestMethod -Uri 'https://kerteszmihaly.com/api/sql-server-builds/v1/builds'
$byBuild = @{}
function ConvertTo-BuildKey([string]$Version) {
($Version.Trim().Split('.') | ForEach-Object { $_ -replace '^0+(?=\d)', '' }) -join '.'
}
foreach ($row in $catalogue.records) {
foreach ($version in (@($row.build) + @($row.aliases))) {
$byBuild[$row.platform + '/' + (ConvertTo-BuildKey $version)] = $row
}
}
Import-Csv ./instances.csv | ForEach-Object {
$build = ConvertTo-BuildKey $_.build
$match = $byBuild[$_.platform.Trim().ToLowerInvariant() + '/' + $build]
[pscustomobject]@{
Instance = $_.instance
Build = $build
Release = $match.release
KB = $match.knowledgeBase.id -join ', '
Status = if ($match) { $match.status } else { 'unmatched' }
}
} | Format-Table -AutoSizeSave a CSV with curl
curl --fail --location "https://kerteszmihaly.com/api/sql-server-builds/v1/builds?format=csv" --output sql-server-builds.csvRead the saved JSON in SQL Server
Fetch the JSON in your client, then bind its contents as @catalogue. OPENJSON requires SQL Server 2016 or later and database compatibility level 130 or higher.
-- @catalogue contains the JSON export supplied by a client.
SELECT build, [update], releaseDate, [status]
FROM OPENJSON(@catalogue, '$.records')
WITH (
build varchar(24) '$.build',
[update] nvarchar(160) '$.update',
releaseDate date '$.releaseDate',
[status] varchar(16) '$.status'
);Get an instance’s build or look up a list of buildsBuild data sources and update status
The catalogue combines Microsoft’s published build history, platform-specific release notes, and archived KBs for older versions. current identifies a build listed in the servicing summary at the source check time. Check the row’s platform, branch, and KB prerequisites before using it to decide whether an instance needs an update.
Microsoft build historyMicrosoft’s build workbookSQL Server build tables
