INFRASTRUCTURE LEARNINGINFRASTRUCTURE LEARNING
インフラ大全インフラ大全IT INFRASTRUCTURE / LEARNING
Infrastructure learning guide
Find a lesson or lab/

Esc to close · Search terms stay on your device

LEARNING日本語

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.

What you will learn

Describe an environment using five attributes, separating feature availability, usage conditions, client and engine.

Prerequisite

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

Five attributes to record separately
AttributeWhat to recordCommon confusion
Engine version/build2022/16.x or 2025/17.x and servicing stateSeparate from the SSMS release
EditionVersion-specific Standard, Enterprise or Developer capabilitiesNot determined solely by the engine year
DB compatibility levelPer-database T-SQL/query-processing compatibilityDoes not downgrade the engine
ClientSSMS/driver release and connection settingsNew client software does not add server features
Hosting and purposeOwn systems, EC2 or RDS; learning, development or productionSeparate features, OS responsibilities and usage conditions
Client, engine and database settings are different checks
Client, engine and database settings are different checks1: Client — Connects to an identified server — SQL Server. 2: SQL Server — Also inspect the selected database — Target database12ClientSQL ServerTarget databaseClient, engine and database settings are different checks1: Client — Connects to an identified server — SQL Server. 2: SQL Server — Also inspect the selected database — Target database12ClientSQL ServerTarget database
  1. Client → SQL ServerConnects to an identified server
  2. 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.

Products reviewed at this date and what they mean
TargetFinding
SQL Server 2022 /16.xThe foundational fixture; use its own feature/support documentation
SQL Server 2025 /17.xUse the 2025 feature table; check edition changes
SSMS 22.11.1Official notes date it 2026-10-20; independent of the engine version

Check both features and the permitted purpose

Edition distinctions relevant to learning
CandidateWhat to verify
Standard / EnterpriseCheck required features, target-version rights and support
2025 Standard DeveloperStandard functionality for development/testing, not production
2025 Enterprise DeveloperEnterprise functionality for development/testing, not production
ExpressCheck feature/resource limits for that exact version
EvaluationTime-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

Read engine and DB attributes together
Illustrative environmentWhat it tells youWhat it does not establish
Engine 2022, DB compatibility 160A fixture using the 2022 default compatibilityPatch state, edition or other DB settings
Engine 2025, DB compatibility 160A 2025 engine with 160 configured for that DBIt has not become a 2022 engine
Engine 2025, new-DB default 170Use of the 2025 default compatibilityNo guarantee that existing DBs automatically change to 170

Match environment conditions to the learning objective

Choose checks from the current goal
GoalConditions to establish
Concepts and query resultsBegin with these static fixtures; a live DB is not required
Development/testing for a target systemMatch engine, edition capabilities, compatibility, collation and options
SSMS connectionsCheck client OS/tool, authentication, encryption/certificates and target DB
RDS for SQL ServerCheck separately the versions, editions, deployments and features RDS supplies
Production useEstablish entitlement, support and an appropriate change/operation plan
  1. Record the five attributes, marking unknowns explicitly.
  2. Map required skills to official engine/edition/database conditions.
  3. Before acquiring tools or engines, review purpose, management scope, costs and safeguards.
  4. 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.

Only SSMS was updated. What follows about the server?
Read the answer and reason

Answer: Verify engine version and DB options separately. · Client freshness does not establish server features or options.

Standard Developer 2025 is available. What should you verify?
Read the answer and reason

Answer: Separate development/testing from production usage rights. · Available Developer functionality is not production entitlement.

A DB uses compatibility 160 on a 2025 engine. Which is correct?
Read the answer and reason

Answer: That DB uses 160 compatibility on the 2025 engine. · Compatibility is per database; it does not replace the engine.

You read self-managed SQL Server 2025 features. Are they all available in RDS?
Read the answer and reason

Answer: Check RDS-supported versions, editions and feature conditions. · Map product capabilities to the configurations the service actually supplies.

Check, then explain in your own words

  1. Write engine, edition, compatibility, client and hosting separately.
  2. Distinguish the 2022 fixture from dated 2025 documentation.
  3. Match Developer usage conditions and target-system capabilities.
  4. 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.