Support for SQL 2025 - #621
Draft
Freddy Kristiansen (freddydk) wants to merge 2 commits into
Draft
Conversation
Freddy Kristiansen (freddydk)
marked this pull request as draft
August 22, 2026 05:35
Contributor
|
Freddy Kristiansen (@freddydk) please read the following Contributor License Agreement(CLA). If you agree with the CLA, please reply with the following information.
Contributor License AgreementContribution License AgreementThis Contribution License Agreement (“Agreement”) is agreed to by the party signing below (“You”),
|
Contributor
Author
|
@microsoft-github-policy-service agree |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This pull request updates the build and installation scripts to support SQL Server 2025 Express instead of SQL Server 2022 Express. The changes ensure that all references, downloads, configurations, and clean-up steps now target SQL Server 2025, and also update the base image logic to handle new OS and .NET Framework versions. Additional improvements include enhanced error reporting during cumulative update installation and refactoring of image selection logic.
SQL Server 2025 Express migration:
All references, download URLs, and configuration steps in
SetupGeneric1.ps1,navinstall.ps1, andSQLConf.iniare updated from SQL Server 2022 to SQL Server 2025, including registry paths, installer names, and clean-up commands. ([[1]](https://github.com/microsoft/nav-docker/pull/621/files#diff-8a26c1d5f5ea9bfdf757fd78753aa33a08aa0377461bb6e10d9b4e090e5431e5L50-R101),[[2]](https://github.com/microsoft/nav-docker/pull/621/files#diff-0b99aaaf68bf25903b0bcdf779d5cd8c9bec808cb8cd2c0f555d59f7b8ca3aa4L75-R77),[[3]](https://github.com/microsoft/nav-docker/pull/621/files#diff-99f520408309beefe831f616807e24b1357509ce3672cde12100dcf651551a93L75-R77),[[4]](https://github.com/microsoft/nav-docker/pull/621/files#diff-c1ee8fc93e893b8182d1d36af4deba5c6db2c85c32c84eff8312147181fe9befL75-R77),[[5]](https://github.com/microsoft/nav-docker/pull/621/files#diff-ac7fc184a992a65c89cee4d4fb7093d6bd2df45becfed3c63f8fd4416e7ee4c0L75-R77),[[6]](https://github.com/microsoft/nav-docker/pull/621/files#diff-d4aa42aa21bb46758c860a6515aef1eda3690c67166f81e5f4c09ac19d56dfb7L76-R78),[[7]](https://github.com/microsoft/nav-docker/pull/621/files#diff-4f775553e20bb749c002151b51dbaf527814f67c1535caebeb3d071f35a28c81L76-R78),[[8]](https://github.com/microsoft/nav-docker/pull/621/files#diff-51d406f9c40889e5ea046ebd517ccb8604c5f1afcd55d49d91f10cca03dc316cL1-R1),[[9]](https://github.com/microsoft/nav-docker/pull/621/files#diff-ae58eedbdb884edb549c297b37b1c75212327a759842b8c36a046a138c7969e2L1-R7))The SQL Server download and cumulative update URLs are replaced with those for SQL Server 2025. (
[generic/Run/SetupUrls.ps1L1-R7](https://github.com/microsoft/nav-docker/pull/621/files#diff-ae58eedbdb884edb549c297b37b1c75212327a759842b8c36a046a138c7969e2L1-R7))Build process enhancements:
The
build.ps1script is refactored to dynamically select and pull the appropriate base image for the detected OS version, including support for .NET Framework 4.8.1 on newer Windows versions. ([[1]](https://github.com/microsoft/nav-docker/pull/621/files#diff-9b51a9f0545ea68f34817beaf48fe8b04c774b0ec6b2381f1677a5ecf5b23b24L11-R43),[[2]](https://github.com/microsoft/nav-docker/pull/621/files#diff-9b51a9f0545ea68f34817beaf48fe8b04c774b0ec6b2381f1677a5ecf5b23b24L33-R61),[[3]](https://github.com/microsoft/nav-docker/pull/621/files#diff-9b51a9f0545ea68f34817beaf48fe8b04c774b0ec6b2381f1677a5ecf5b23b24L54-R83))The script now tags and pushes the built image to the
freddyk/businesscentralrepository with the-sql2025suffix, ensuring availability and versioning for SQL Server 2025 builds. ([generic/build.ps1R124-R126](https://github.com/microsoft/nav-docker/pull/621/files#diff-9b51a9f0545ea68f34817beaf48fe8b04c774b0ec6b2381f1677a5ecf5b23b24R124-R126))Error handling improvements:
[generic/Run/SetupGeneric1.ps1L50-R101](https://github.com/microsoft/nav-docker/pull/621/files#diff-8a26c1d5f5ea9bfdf757fd78753aa33a08aa0377461bb6e10d9b4e090e5431e5L50-R101))Other updates:
[generic/Run/SetupGeneric1.ps1L50-R101](https://github.com/microsoft/nav-docker/pull/621/files#diff-8a26c1d5f5ea9bfdf757fd78753aa33a08aa0377461bb6e10d9b4e090e5431e5L50-R101))These changes collectively ensure that the build and deployment process is ready for SQL Server 2025 Express and compatible with the latest Windows and .NET Framework versions.