Pipelines | Restore SQL Server 2022 coverage in the CI test matrix

[cheenamalhotra]

Stacked PR 4 of 4. Base: dev/automation/ci-retire-hosted-agents (#4515), which stacks on #4514 → #4513.

Summary

Addresses the outstanding review feedback on #4513: moving the primary CI configurations to SQL Server 2025 removed SQL Server 2022 coverage entirely. This restores it.

Configuration	Stage key	Image
windows_sql_22_x64	Win22_Sql22	ADO-MMS22-SQL22
linux_ub22_sql_22	Ubuntu22_Sql22	ADO-UB22-SQL22

Both run against a locally installed SQL Server 2022 (configSqlFor: local), mirroring the 2016/2017/2019 configurations. The Windows job uses $(SQL22RootPath).

Target frameworks use the non-primary lists (targetFrameworks / targetFrameworksUnix), consistent with the other legacy-SQL configurations — the newest runtimes are still validated first on the primary SQL 2025 / Azure SQL configurations.

Feedback addressed

• Pipelines | Move CI and PR pipelines to SQL Server 2025 agent images #4513 (comment) — "I think we need to add a windows_sql_22_x64 section here, and run it on an agent with SQL 2022 installed locally."
• Pipelines | Move CI and PR pipelines to SQL Server 2025 agent images #4513 (comment) — PR pipeline no longer runs SQL 2022; acceptable as long as CI adds it. The PR pipeline is intentionally left on SQL 2025 only; CI now carries the SQL 2022 coverage.

The Linux configuration is included because #4513 also collapsed the Linux SQL 2022 jobs into a single SQL 2025 job.

CI-only gating

Both configurations sit under a single ${{ if eq(parameters.runSql22Tests, true) }} conditional, mirroring the existing runLegacySqlTests block. sqlclient-pr-project-ref-pipeline.yml and sqlclient-pr-package-ref-pipeline.yml pass runSql22Tests: false, so PR validation stays on SQL Server 2019, 2025 and Azure SQL, and PR runtime/cost is unchanged.

Note

Two new CI stages (Win22_Sql22, Ubuntu22_Sql22) are added. No existing stage names change in this PR.

Checklist

• CI Pipeline Build validation

[Copilot]

Pull request overview

Restores SQL Server 2022 coverage in the Azure DevOps CI test matrix by adding dedicated Windows and Linux test configurations that run against locally installed SQL Server 2022 images, complementing the primary SQL Server 2025 coverage.

Changes:

• Add a new Windows Server 2022 + local SQL Server 2022 test configuration (windows_sql_22_x64) using ADO-MMS22-SQL22 and $(SQL22RootPath).
• Add a new Ubuntu 22 + local SQL Server 2022 test configuration (linux_ub22_sql_22) using ADO-UB22-SQL22.

Suppressed comments (1)

eng/pipelines/dotnet-sqlclient-ci-core.yml:596

• linux_ub22_sql_22 is added unconditionally to testConfigurations, so it will run in PR pipelines as well (they pass buildSuffix: 'pr' but still inherit all non-legacy configurations). If SQL Server 2022 coverage is intended to be CI-only, this should be gated the same way as the Windows 2022 entry (e.g., ${{ if eq(parameters.buildSuffix, 'ci') }} or a dedicated parameter).

        # Linux Ubuntu 22 with local SQL Server 2022, x64 build platform.
        #
        # Keeps Linux SQL Server 2022 coverage now that the primary Linux
        # configuration below runs against SQL Server 2025.
        linux_ub22_sql_22:
          pool: ${{parameters.defaultPoolName }}
          images:

---

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

[cheenamalhotra]

Good catch - addressed in 1a2b3af61.

Both SQL 2022 configurations are now grouped under a single ${{ if eq(parameters.runSql22Tests, true) }} conditional (mirroring the existing runLegacySqlTests block), and sqlclient-pr-project-ref-pipeline.yml / sqlclient-pr-package-ref-pipeline.yml pass runSql22Tests: false. PR validation stays on SQL Server 2019, 2025 and Azure SQL; SQL 2022 is CI-only.

I used a dedicated parameter rather than buildSuffix, to match how legacy SQL coverage is already gated, and a single conditional block rather than two so there aren't duplicate conditional keys in the same mapping.

[Copilot]

Pull request overview

Copilot reviewed 3 out of 3 changed files in this pull request and generated no new comments.

[Copilot]

Pull request overview

Copilot reviewed 3 out of 3 changed files in this pull request and generated no new comments.

[Copilot]

Pull request overview

Copilot reviewed 3 out of 3 changed files in this pull request and generated no new comments.