Topic lessonTopic: SQL Server versions and learning environments
SQL Server versions, editions and learning environments
Engine version, edition, database compatibility level, SSMS version and hosting are separate attributes. Distinguish the SQL Server 2022 teaching fixture from 2025 features and usage conditions, then choose a learning environment for the skills and target system you need.
Describe an environment using five attributes, separating feature availability, usage conditions, client and engine.
SQL Server is the database engine, T-SQL is its query language and SSMS is a management client. This lesson installs nothing, purchases no rights and provisions no environment.
Do not describe the environment with one version number
| Attribute | What to record | Common confusion |
|---|---|---|
| Engine version/build | 2022/16.x or 2025/17.x and servicing state | Separate from the SSMS release |
| Edition | Version-specific Standard, Enterprise or Developer capabilities | Not determined solely by the engine year |
| DB compatibility level | Per-database T-SQL/query-processing compatibility | Does not downgrade the engine |
| Client | SSMS/driver release and connection settings | New client software does not add server features |
| Hosting and purpose | Own systems, EC2 or RDS; learning, development or production | Separate features, OS responsibilities and usage conditions |
- Client → SQL ServerConnects to an identified server
- SQL Server → Target databaseAlso inspect the selected database
- Client
- SSMS/driver version and connection settings.
- SQL Server
- Engine version, build and edition.
- Target database
- Compatibility and options for that database.
Separate the 2022 example from 2025 feature conditions
The basic lessons stipulate SQL Server 2022/16.x, Standard and compatibility 160. That is a teaching fixture, not a latest-version recommendation. At the 2026-10-25 review, Microsoft publishes SQL Server 2025/17.x feature tables and SSMS 22 release notes.
| Target | Finding |
|---|---|
| SQL Server 2022 /16.x | The foundational fixture; use its own feature/support documentation |
| SQL Server 2025 /17.x | Use the 2025 feature table; check edition changes |
| SSMS 22.11.1 | Official notes date it 2026-10-20; independent of the engine version |
Check both features and the permitted purpose
| Candidate | What to verify |
|---|---|
| Standard / Enterprise | Check required features, target-version rights and support |
| 2025 Standard Developer | Standard functionality for development/testing, not production |
| 2025 Enterprise Developer | Enterprise functionality for development/testing, not production |
| Express | Check feature/resource limits for that exact version |
| Evaluation | Time-limited evaluation conditions; not a permanent production entitlement |
A Standard target does not automatically support features learned on an Enterprise-capability environment. Technical availability and permission for production use are different questions. Check current vendor terms and entitlement for the intended environment.
Compatibility level does not replace the engine
| Illustrative environment | What it tells you | What it does not establish |
|---|---|---|
| Engine 2022, DB compatibility 160 | A fixture using the 2022 default compatibility | Patch state, edition or other DB settings |
| Engine 2025, DB compatibility 160 | A 2025 engine with 160 configured for that DB | It has not become a 2022 engine |
| Engine 2025, new-DB default 170 | Use of the 2025 default compatibility | No guarantee that existing DBs automatically change to 170 |
Match environment conditions to the learning objective
| Goal | Conditions to establish |
|---|---|
| Concepts and query results | Begin with these static fixtures; a live DB is not required |
| Development/testing for a target system | Match engine, edition capabilities, compatibility, collation and options |
| SSMS connections | Check client OS/tool, authentication, encryption/certificates and target DB |
| RDS for SQL Server | Check separately the versions, editions, deployments and features RDS supplies |
| Production use | Establish entitlement, support and an appropriate change/operation plan |
- Record the five attributes, marking unknowns explicitly.
- Map required skills to official engine/edition/database conditions.
- Before acquiring tools or engines, review purpose, management scope, costs and safeguards.
- After a real installation/update, verify recorded versions, options and application results; no such operation occurs here.
Distinguish tool, engine, database and purpose
Choose an option to see the result and explanation.
Check, then explain in your own words
- Write engine, edition, compatibility, client and hosting separately.
- Distinguish the 2022 fixture from dated 2025 documentation.
- Match Developer usage conditions and target-system capabilities.
- Do not mark unverified entitlement or installation as complete.
Check your understanding: Do identical engine versions establish equivalent learning and production environments?
No. Also check edition, DB options, permitted purpose and hosting.
Shared SQL syntax does not establish identical features, performance, entitlement or operational responsibilities.
Sources and conditions checked
Primary references are collected here with their scope, conditions and corresponding sections. Independent expert review and live-environment validation have not been performed.
Scope and conditions2025 editions and non-production Developer use; do not transfer 2022 limits.
Used in this lessonDo not describe the environment with one version number Separate the 2022 example from 2025 feature conditions Check both features and the permitted purpose Distinguish tool, engine, database and purpose
Scope and conditionsEngine version versus per-database compatibility; distinguish 2022/160 and 2025/170.
Used in this lessonDo not describe the environment with one version number Compatibility level does not replace the engine Distinguish tool, engine, database and purpose
- Microsoft: SSMS 22 release notesChecked:
Scope and conditions22.11.1 release dated 2026-10-20 verified; not an installed-environment claim.
Used in this lessonDo not describe the environment with one version number Separate the 2022 example from 2025 feature conditions Distinguish tool, engine, database and purpose
- Microsoft: Optimized lockingChecked:
Scope and conditionsSQL Server 2025 availability/default OFF, ADR prerequisite and RCSI-dependent LAQ; distinguish SQL 2022 and Azure defaults.
Used in this lessonSeparate the 2022 example from 2025 feature conditions