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 and database foundations

SQL Server fundamentals and learning path

Microsoft SQL Server is a relational database management system. T-SQL expresses queries and operations; SSMS is a connection and management tool. Separate these roles, then connect structure → connections → permissions → query results → transactions.

What you will learn

Distinguish SQL Server, SQL/T-SQL and SSMS, then choose a path for connections, reading or changes.

Prerequisite

A basic idea of tables, rows, columns and primary keys, briefly reinforced here. No database installation is required.

SQL Server, T-SQL and SSMS have different roles

Separate the tool, language and engine
CLIENT
SSMS

The tool used to select a connection, inspect configuration and write SQL.

LANGUAGE
T-SQL

The language expressing retrieval and changes, not a network route.

ENGINE
SQL Server

The DBMS processing requests and managing data and permissions.

A fictional teaching example. Containment, communication and permission relationships have different meanings.

SQL is a language for expressing data queries and other work. Transact-SQL (T-SQL) is the SQL dialect and extensions used by SQL Server and related products. SQL Server processes the work; SSMS is one client for writing it. Applications may connect through a driver.

What participates in a document-list query?

Break down one document read
ElementOur exampleKeep separate
ClientSSMS / client-ANot the engine managing the data
Instancesql-demo-1Not itself a database name
Database and objectCorpDocs.app.DocumentsDifferent from the same name in another DB
Principal and permissionreader_demo / SELECTConnecting does not imply update rights
Query and data stateOpen rows / committed T0Changed data can change results

Connected, authenticated, allowed to read a table and receiving the intended documents are different observations. The lessons use the same five documents to trace the conditions behind each conclusion.

Start with structure and work toward query results

Course order and outcomes
StageSubjectOutcome
1StructureDistinguish instance, database, schema and table
2SSMSCheck the server and current database
3AccessSeparate login, user, role and SELECT
4T-SQLPredict WHERE, NULL and JOIN results
5TransactionsExplain commit and rollback of two updates

For connection questions, study structure, SSMS and access. Continue to T-SQL to read queries, then transactions to understand committed changes. Indexes, plans, locking and restore internals are not prerequisites for the first read.

Learn SQL Server from database foundations

Follow tables and keys → engine and tools → structure → SSMS → permissions → query results → commit and rollback. One document dataset connects the lessons; no server is required.

There are 7 available lessons.

For connection questions, choose SSMS and access control. To predict rows, study T-SQL; to understand committed changes, continue to transactions.

SQL Server versions and learning environments

SQL Server performance and concurrency

SQL Server connection troubleshooting

Optional study: relational and NoSQL models

After the foundations: recovery and AWS

Review recovery and RDS/SQL Server responsibilities, then continue to connections, deployment, availability, costs and migration to AWS.

Optional: compare and investigate AWS databases

Explore designs beyond SQL Server: DynamoDB keys, Aurora architecture, selection requirements and engine-specific connection investigation.

Separate versions, editions and hosting from tools and language

Illustrative conditions and independent attributes
AttributeIllustrationMeaning
Engine versionSQL Server 2022 / 16.xProduct version; not a latest-version recommendation
EditionStandard, hypotheticallyFeature and usage conditions; no license entitlement asserted
DB compatibility160, hypotheticallyDatabase behavior compatibility, separate from engine version
ClientDocumented SSMS 20+ fieldsTool version and saved settings
HostingOwn systems, VMs or managed servicesResponsibility for OS and engine management

The same distinctions matter on AWS: engine, client and database permissions remain separate. Choosing RDS or EC2 is a later question about required features and management responsibilities. No specific configuration is asserted to be built, eligible or free.

Check product, language and tool roles

Choose an option to see the result and explanation.

Which component is SQL Server itself?
Read the answer and reason

Answer: The database engine that processes queries and manages data · This is the engine, not SSMS.

What is T-SQL?
Read the answer and reason

Answer: A SQL dialect/extension used by SQL Server · The language is distinct from the engine.

Does installing SSMS alone prove a database engine is installed?
Read the answer and reason

Answer: No · SSMS is a connecting client.

Check, then explain in your own words

  1. Describe SSMS, T-SQL and SQL Server in one sentence each.
  2. Identify the server, database, principal and operation for a document read.
  3. Start with structure, then follow the connection, access or query path.
  4. Read version, edition, compatibility and hosting as separate attributes.
Check your understanding: When SQL is written in SSMS, which component processes it?

The connected SQL Server Database Engine.

SSMS is the client, T-SQL expresses the work, and the engine processes it.

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.