Installing SQL Server on Windows

Introduction

Installing Microsoft SQL Server means setting up a database engine that can store databases, execute Transact-SQL, enforce constraints, coordinate transactions, manage security, and serve client applications. For a Windows learning environment, the practical combination is SQL Server 2025 Developer edition plus SQL Server Management Studio, commonly called SSMS.

SQL Server and SSMS are separate products with separate responsibilities. SQL Server Database Engine runs as a service and owns databases. SSMS is a graphical client that connects to an instance, displays objects, submits T-SQL, and provides administration tools. Installing SSMS alone does not create a local database server, and closing SSMS does not stop an installed SQL Server service.

This tutorial follows the current SQL Server 2025 installation model. SQL Server setup, SSMS versions, cumulative updates, operating-system support, and optional cloud integration can change, so confirm requirements in Microsoft Learn before installation. The durable workflow is to choose the correct edition, prepare Windows, install one controlled Database Engine instance, add yourself as an administrator, install SSMS, connect, and verify database creation with a complete T-SQL test.

What You Need to Install

A local SQL Server learning setup has two essential layers. The Database Engine is the server process that parses queries, manages data and log files, writes transactions, enforces permissions, and returns results. SSMS is the management client used to connect to that engine. Additional services are optional and should be installed only when a course or project needs them.

ComponentPurposeBeginner recommendation
SQL Server Database EngineStores databases and executes T-SQLRequired
SQL Server Management StudioGraphical query and administration clientRecommended
sqlcmdCommand-line query and automation clientUseful later
SQL Server AgentSchedules jobs where supported by the editionUseful for administration topics

Reporting Services is no longer installed as a SQL Server 2025 Database Engine feature, and other specialized services have their own requirements or lifecycle. A beginner should avoid selecting every available component merely because it appears in setup.

Choose Developer or Express Edition

Microsoft provides free Developer editions for non-production development and testing. SQL Server 2025 distinguishes Standard Developer and Enterprise Developer choices. Enterprise Developer exposes the broader enterprise feature set for learning and testing, while Standard Developer lets teams develop against the Standard-edition feature boundary. Neither Developer choice is licensed for production workloads.

SQL Server Express is also free and can support lightweight desktop, web, development, and small-server workloads within its documented resource and feature limits. It is useful when a small footprint or Express-specific deployment is the target. For a broad SQL Server course on a capable Windows computer, Enterprise Developer is usually the most flexible learning choice.

EditionBest fitImportant boundary
Enterprise DeveloperLearning and testing the broad feature setNon-production only
Standard DeveloperDevelopment against Standard featuresNon-production only
ExpressSmall and lightweight applicationsDocumented feature and resource limits

SQL Server 2025 and Support Lifecycle

SQL Server 2025, version 17.x, is Microsoft's current major on-premises SQL Server release in 2026. Microsoft lists its lifecycle start as November 18, 2025, mainstream support through January 7, 2031, and extended support through January 7, 2036.

A supported major version still requires servicing. Apply current cumulative updates after reviewing release notes and compatibility guidance. Record the edition, full build number, update level, instance name, and installation date so later troubleshooting does not depend on memory.

Check Windows and Hardware Requirements

Modern SQL Server releases are 64-bit applications. SQL Server 2025 support varies by Windows edition, SQL Server edition, and feature. Review Microsoft's current hardware and software requirements for the exact combination rather than assuming every server feature is supported on every desktop edition.

Apply Windows updates and restart before setup, especially when an update has left a pending reboot. Confirm sufficient memory, CPU capacity, and disk space for setup files, database files, transaction logs, temporary database activity, backups, and future practice data. SQL Server installation writes temporary files to the system drive even when other directories are selected.

  • Use a supported 64-bit Windows edition.
  • Apply updates and clear pending restart requirements.
  • Run setup with local administrator permission.
  • Check for existing SQL Server instances and services.
  • Confirm enough storage exists for data, logs, tempdb, and backups.
  • Record any corporate antivirus, firewall, or endpoint restrictions.

Download SQL Server from Microsoft

Use the official Microsoft SQL Server downloads page. Select the appropriate SQL Server 2025 Developer download for non-production learning or Express for a lightweight installation. Avoid repackaged installers from unrelated download sites.

The initial download may be a bootstrap application that offers Basic, Custom, or Download Media choices. Basic uses a simplified path with more defaults. Custom exposes the installation media and full SQL Server Setup workflow. Download Media prepares files for offline or repeatable installation. For learning how instances and features work, Custom is the more instructive route.

Basic, Custom, and Download Media

Basic installation is convenient when the goal is a quick local instance and the defaults are acceptable. It provides less opportunity to understand features, instance naming, service configuration, authentication, directories, and administrators.

Custom installation downloads media and launches SQL Server Installation Center, where you can make deliberate choices. Download Media is useful when several computers need the same source files, internet access is limited, or an organization requires controlled installation media.

This tutorial uses the Custom path conceptually. Wizard wording may vary slightly by edition and update, but the major decisions remain the same.

Open SQL Server Installation Center

Run setup.exe from the downloaded or mounted installation media. SQL Server Installation Center provides Planning, Installation, Maintenance, Tools, Resources, and Advanced sections. Choose Installation, then select New SQL Server standalone installation or add features to an existing installation.

Installation media
    -> setup.exe
    -> SQL Server Installation Center
    -> Installation
    -> New SQL Server standalone installation

Do not choose the add-features path for an existing production instance merely to experiment. Confirm the target computer and intended instance before proceeding.

Select the Edition and Accept Terms

On the Edition page, select the free Developer option appropriate for your learning boundary, or provide the edition and licensing information required by your organization. Read the displayed license terms and privacy information before accepting them. Developer edition's zero purchase price does not remove its non-production licensing restriction.

Setup can also present cloud-connected or Azure extension choices. SQL Server 2025 can be installed without connecting the local learning instance to Azure. Enable optional integration only when you have an active requirement, understand the account and subscription implications, and intend to manage that connection.

Review Setup Rules and Updates

Setup runs global and installation rules to detect blocking conditions such as unsupported configurations, pending restarts, service conflicts, or missing prerequisites. Open failed or warning items and resolve their actual causes. Do not ignore a failure simply because the Next button remains available elsewhere.

Allow setup to discover applicable product updates when policy and connectivity permit. After installation, still verify the installed build against Microsoft's current SQL Server 2025 update history because media can lag behind the newest cumulative update.

Select Database Engine Services

On Feature Selection, choose Database Engine Services for core SQL learning. Additional feature labels can vary by edition and release. Install only what the course or application needs, because each feature increases disk use, servicing scope, attack surface, and administration work.

Client tools such as the current SSMS are installed separately. Sample databases are also not installed automatically by Database Engine setup. This separation lets Microsoft service SQL Server, SSMS, and samples on independent schedules.

Understand SQL Server Instances

An instance is one independently configured installation of the SQL Server Database Engine. One Windows computer can host multiple instances, each with its own services, system databases, settings, security boundary, and database collection. Instances still share operating-system resources.

Windows computer
    -> default instance: MSSQLSERVER
        -> databases
    -> named instance: SQLLEARNING
        -> separate databases and configuration

A first learning computer usually needs only one instance. Multiple instances are useful for version testing or isolation but introduce additional ports, services, memory use, patching, and connection-name complexity.

Default and Named Instances

The default Database Engine instance uses the internal instance name MSSQLSERVER. Clients normally connect with the computer name, localhost, or a local shorthand without adding an instance suffix.

A named instance uses a chosen identifier such as SQLLEARNING or the conventional Express name SQLEXPRESS. Clients include the name after a backslash:

localhost\SQLLEARNING
localhost\SQLEXPRESS
COMPUTERNAME\SQLLEARNING

Record the choice exactly. Many connection problems are simply attempts to reach a default instance when setup created a named instance, or vice versa.

Configure SQL Server Services

SQL Server Setup creates a Database Engine service. A default instance commonly appears as SQL Server (MSSQLSERVER), while a named instance appears as SQL Server (InstanceName). Service accounts and startup types should follow Microsoft guidance and organizational policy.

For a dedicated local learning instance, automatic startup is convenient. Production service identity requires deliberate least privilege, password management, permissions, and service-account planning. Do not replace managed service identities with a personal administrator account merely to bypass a setup issue.

Choose Authentication Mode

Windows Authentication uses the identity already authenticated by Windows. It integrates with Windows security, avoids a separate SQL password for that login, and is the recommended starting choice for a local learning installation.

Mixed Mode enables both Windows Authentication and SQL Server Authentication. Setup then requires a strong password for the built-in SQL login named sa. Choose Mixed Mode only when a client or exercise requires SQL authentication and you understand the additional password, auditing, and attack-surface responsibilities.

ModeLogin sourceLearning guidance
Windows AuthenticationWindows account or domain identityPreferred starting option
Mixed ModeWindows identities plus SQL loginsEnable only for a defined requirement

What Is the sa Login?

sa is the built-in SQL Server system administrator login used with SQL Server Authentication. It has extremely broad privileges. It is not the same as a Windows administrator account, and ordinary applications should never depend on it.

If Mixed Mode is enabled, protect the sa password in a password manager and do not place it in source code, screenshots, scripts, or shared notes. Prefer named, least-privilege logins or Windows identities so activity is attributable and compromise has a narrower impact.

Add the Current User as Administrator

On Database Engine Configuration, add the Windows account that will administer the local instance. The button to add the current user is convenient for a personal learning computer. Confirm that at least one appropriate Windows identity or group receives SQL Server system administrator access before completing setup.

Windows local administrator status does not automatically guarantee SQL Server administrative access after setup. Database permissions are managed by SQL Server security, which is why this setup page matters.

Plan Data, Log, Backup, and tempdb Locations

SQL Server databases commonly use primary data files with an .mdf extension, optional secondary data files with .ndf, and transaction log files with .ldf. Production systems often separate data, logs, tempdb, and backups according to storage performance and recovery requirements.

Default paths are acceptable for a small local learning instance when storage is sufficient. Record them and avoid saving irreplaceable backups on the same location as the only database copy. Directory design for production should account for capacity, throughput, failure domains, permissions, encryption, and backup retention.

Complete and Review Installation

Before applying changes, review the configuration summary or generated configuration file. After setup finishes, inspect every feature's status rather than assuming an overall completion screen means all components succeeded. Save the summary, setup log path, instance name, and installed features.

Restart Windows if setup or a prerequisite requires it. Then verify that the SQL Server service starts. Installation is not complete from a learner's perspective until a client can connect and successfully create, write, and read data.

Install SQL Server Management Studio

SSMS is a separate download and installation. Use the official SSMS installation documentation to obtain the current Microsoft-hosted installer. In 2026, SSMS 22 is the current product line.

Install SSMS after or before the Database Engine; the order does not change their separate roles. SSMS can connect to SQL Server running locally, on another computer, in a virtual machine, or in supported cloud services. It does not store the database itself.

Connect to the Local Instance

Open SSMS and create a Database Engine connection. For a default local instance, use localhost, ., or the computer name. For a named instance, use localhost\InstanceName. Select Windows Authentication for the recommended local setup.

Server type: Database Engine
Server name: localhost
Authentication: Windows Authentication

If encryption settings produce a certificate trust error, do not disable security blindly. Understand whether the connection is local, what certificate the server presents, and how the current SSMS encryption options should be configured. Production systems should use a trusted certificate and documented encryption policy.

Explore Object Explorer

After connecting, Object Explorer displays Databases, Security, Server Objects, Replication where available, Management, and other instance nodes. Expand Databases to find System Databases and user databases. Right-click the server and inspect Properties to confirm the instance, edition, version, and connection.

Object Explorer is a graphical view of metadata and administrative actions. Learn the equivalent T-SQL for important operations so your knowledge is reproducible and not limited to one interface.

Verify Version, Edition, and Connection

Open a New Query window and run:

SELECT @@VERSION AS full_version;

SELECT
    SERVERPROPERTY('ProductVersion') AS product_version,
    SERVERPROPERTY('ProductLevel') AS product_level,
    SERVERPROPERTY('Edition') AS edition,
    SERVERPROPERTY('ServerName') AS server_name;

SELECT
    SUSER_SNAME() AS login_name,
    DB_NAME() AS current_database;

These results confirm which instance answered, which build and edition are installed, which login is active, and which database is selected. This is stronger evidence than seeing an SSMS connection icon.

Understand the System Databases

A new SQL Server instance contains system databases. master stores instance-level metadata and configuration. model acts as a template for new databases. msdb supports jobs, backup history, alerts, and other SQL Server Agent or management information. tempdb provides temporary workspace and is recreated whenever the service starts.

Do not use system databases for ordinary practice tables. Protect and back up system databases according to Microsoft's recovery guidance because they are important to instance operation and disaster recovery.

Create Your Practice Database

Create a dedicated user database and explicitly change the query context:

CREATE DATABASE sql_mastery;
GO

USE sql_mastery;
GO

SELECT DB_NAME() AS current_database;
GO

The database appears under Databases after Object Explorer refreshes. The GO lines are client batch separators recognized by tools such as SSMS and sqlcmd; they are not T-SQL statements sent to the Database Engine.

Create a Table and Verify Data

Use an end-to-end test that creates a table, inserts a row, and reads it:

USE sql_mastery;
GO

CREATE TABLE dbo.students (
    student_id int IDENTITY(1, 1) PRIMARY KEY,
    student_name varchar(100) NOT NULL,
    email varchar(150) UNIQUE
);
GO

INSERT INTO dbo.students (student_name, email)
VALUES ('John', 'john@test.com');
GO

SELECT student_id, student_name, email
FROM dbo.students;
GO

If the row appears, the service, authentication, database context, schema, table, transaction log, and query path are working. Disconnect and reconnect later, select sql_mastery, and query again to verify persistence.

Database, Schema, and Object Hierarchy

A SQL Server instance contains databases. Each database contains schemas, and schemas contain tables, views, procedures, functions, and other objects. The common default schema is dbo.

SQL Server instance
    -> database: sql_mastery
        -> schema: dbo
            -> table: students
                -> rows

Use two-part names such as dbo.students to make object ownership and resolution clear. A database and schema are not interchangeable in SQL Server.

T-SQL and Standard SQL

SQL Server implements Transact-SQL, or T-SQL, Microsoft's extension of SQL. Standard concepts such as SELECT, JOIN, GROUP BY, constraints, and transactions remain central. T-SQL adds product-specific syntax, system functions, procedural control flow, error handling, and administrative commands.

Examples include TOP, IDENTITY, GETDATE(), TRY...CATCH, variables beginning with @, and the GO client batch convention. When writing portable SQL, distinguish standard behavior from SQL Server-specific features.

SQL Server Configuration Manager

SQL Server Configuration Manager manages SQL Server services, service accounts, startup behavior, and network protocols for installed components. Use it rather than treating service and protocol settings as unrelated Windows changes.

For purely local SSMS connections, shared memory can work without TCP/IP. Applications, containers, remote computers, and explicit network tests generally need TCP/IP enabled and configured. Changes to protocols or ports commonly require a Database Engine service restart.

TCP/IP, Ports, and SQL Server Browser

A default SQL Server instance commonly uses TCP port 1433 when configured for a fixed standard port, but actual configuration can differ. Named instances often use dynamically assigned ports unless configured otherwise. Do not assume 1433 without checking SQL Server Configuration Manager and the server error log.

SQL Server Browser can help clients discover named instances and their ports. It is not always required when clients specify a known host and fixed port directly. Enabling Browser and opening firewall ports should be based on a defined connectivity requirement, not used as a blanket fix.

Keep a Learning Instance Local

A local SQL learning instance normally does not need inbound access from other computers. Avoid opening SQL Server ports to public networks. Remote access requires deliberate TCP/IP configuration, firewall scope, authentication, encryption, certificates, patching, monitoring, and network segmentation.

Use a VPN, private network, secure tunnel, or managed architecture when remote connectivity is required. Restrict source ranges and accounts. A strong sa password alone is not an adequate perimeter control.

Create a Least-Privilege Login and User

After verifying installation as an administrator, create a less-privileged identity for ordinary practice or applications. With Windows Authentication, create a login for an appropriate Windows user or group, map it to a database user, and grant only required roles or permissions.

USE master;
GO
CREATE LOGIN [COMPUTERNAME\SqlStudent]
FROM WINDOWS;
GO

USE sql_mastery;
GO
CREATE USER [COMPUTERNAME\SqlStudent]
FOR LOGIN [COMPUTERNAME\SqlStudent];
GO
ALTER ROLE db_datareader ADD MEMBER [COMPUTERNAME\SqlStudent];
ALTER ROLE db_datawriter ADD MEMBER [COMPUTERNAME\SqlStudent];
GO

Replace the example with the actual Windows identity. Object creation may require carefully selected additional permission; do not grant sysadmin simply to avoid learning the permission model.

Install and Use sqlcmd When Needed

sqlcmd is a command-line client for executing queries and scripts. Current installation and packaging can be separate from the Database Engine and SSMS, so follow Microsoft's current sqlcmd documentation rather than assuming an old executable is already on PATH.

sqlcmd -S localhost -E -Q "SELECT @@VERSION;"

-S selects the server, -E uses a trusted Windows connection, and -Q executes a query and exits. Command-line access is useful for repeatable verification, build scripts, and environments without SSMS.

Apply Cumulative Updates

Download media can contain an older build than the latest serviced SQL Server 2025 release. Review Microsoft's update history, read known issues, test the cumulative update, back up important databases, and apply the appropriate supported build.

After patching, rerun SERVERPROPERTY('ProductVersion') and record the result. Production patching also requires high-availability sequencing, rollback planning, application testing, and maintenance communication.

Sample Databases and AdventureWorks

SQL Server Setup does not install sample databases automatically. Microsoft provides sample databases such as AdventureWorks separately. Restoring a sample is useful for joins, reporting, query plans, and administration exercises once the core instance works.

Begin with a small schema you understand before importing a large sample. Creating customers, products, orders, departments, employees, students, courses, and enrollments teaches data modeling and makes errors easier to diagnose.

Troubleshoot Cannot Connect to Server

A connection failure can occur because the Database Engine service is stopped, the server or instance name is wrong, the protocol is disabled, the port differs, the firewall blocks traffic, or encryption negotiation fails. Preserve the complete error message and number before changing settings.

  • Confirm the SQL Server service for the intended instance is Running.
  • Match the connection name to default or named instance setup.
  • Test locally before diagnosing remote networking.
  • Verify protocols and actual port in Configuration Manager.
  • Review SQL Server setup and error logs for the first cause.
  • Handle certificate and encryption settings according to a documented trust model.

Troubleshoot Login Failed

A login failure means the client reached SQL Server but authentication or authorization failed. Confirm the authentication mode, login identity, password where applicable, and whether the login is enabled. With Windows Authentication, verify which Windows account launched the client.

A login can also succeed at the server but fail to open its default database. Connect to an available database such as master with an administrator and repair the user's mapping or default database. Do not enable sa or grant sysadmin as a generic response.

Troubleshoot a Wrong Instance Name

A default instance and named instance use different connection syntax. Check Windows Services or SQL Server Configuration Manager for the exact service name. A service displayed as SQL Server (MSSQLSERVER) is the default instance; SQL Server (SQLEXPRESS) is a named instance.

Default: localhost
Named:   localhost\SQLEXPRESS

If a named instance uses a known fixed port, a client can also connect using the server and port syntax supported by that client. Document the selected form consistently.

Read Setup and Server Logs

SQL Server Setup writes detailed summary and component logs. The Database Engine writes an error log containing startup information, configured network endpoints, recovery messages, and failures. These logs are more useful than repeatedly rerunning setup.

Find the earliest relevant error around the failure time. Later entries may only be consequences. Review logs before sharing because they can expose computer names, instance names, file paths, accounts, database names, or query information.

Back Up the Practice Database

As exercises become valuable, back up the user database and test restoration into a separate name. A basic local example is:

BACKUP DATABASE sql_mastery
TO DISK = 'C:\SQLBackups\sql_mastery.bak'
WITH INIT, CHECKSUM, STATS = 10;
GO

The SQL Server service account needs permission to the destination directory. A backup on the same disk is useful for exercises but not sufficient disaster recovery. Production design needs retention, encryption, off-host copies, monitoring, integrity checks, and tested restores.

Verify Installation After Restart

Restart Windows after the initial setup and updates. Confirm the intended SQL Server service starts automatically, reconnect using SSMS, inspect version and edition, and query the row in sql_mastery.

USE sql_mastery;
GO
SELECT * FROM dbo.students;
GO
SELECT
    @@SERVERNAME AS server_name,
    SUSER_SNAME() AS login_name,
    DB_NAME() AS database_name;
GO

This validates service startup, authentication, instance targeting, persistent data, and query execution rather than relying only on the installer's completion status.

Build a Reusable Practice Schema

A useful course database should grow through repeatable scripts. Customers, orders, order items, and products support joins, constraints, indexes, transactions, and aggregation. Departments and employees support one-to-many and hierarchical queries. Students, courses, and enrollments support many-to-many relationships.

customer -> sales_order -> order_item -> product

department -> employee

student -> enrollment -> course

Keep schema scripts and non-sensitive sample data in version control. Resetting a practice database should require running scripts, not reinstalling SQL Server.

Compare SQL Server, PostgreSQL, and MySQL Setup

ConceptSQL ServerPostgreSQLMySQL
Database engineSQL Server Database EnginePostgreSQL ServerMySQL Server
Common GUISSMSpgAdminMySQL Workbench
CLIsqlcmdpsqlmysql
Common port1433 when configured54323306
Common schemadbopublicDatabase often serves namespace role

All three products use client-server architecture, databases, permissions, transaction logs, and backups, but their installation terminology and administration tools differ.

Common Installation Mistakes

Common mistakes include installing only SSMS, choosing an edition without understanding licensing, selecting every feature, forgetting the instance name, omitting the current user from administrators, and assuming every SQL Server listens on port 1433.

Other risks include enabling Mixed Mode without need, using sa for applications, opening firewall ports broadly, ignoring cumulative updates, placing data and the only backup on one disk, treating certificate warnings as obstacles to bypass, and reinstalling because of a simple connection-name error.

A Systematic Troubleshooting Flow

Work from the server process outward. First confirm the intended instance service is running. Then verify default versus named instance syntax. Next check local connection, authentication, protocols, ports, firewall, encryption, database access, and object permissions.

Is the correct SQL Server service running?
    No  -> inspect setup and server logs
    Yes -> Is the instance name correct?
              No  -> correct localhost or localhost\InstanceName
              Yes -> Can SSMS connect locally?
                        No  -> check authentication and encryption
                        Yes -> Does remote TCP connectivity work if required?
                                  No  -> check TCP, port, firewall, and Browser
                                  Yes -> inspect database and object permissions

Installation Verification Checklist

  • The installer came from Microsoft's official SQL Server download page.
  • The edition matches the learning goal and license boundary.
  • Windows and hardware meet current SQL Server 2025 requirements.
  • Database Engine Services installed successfully.
  • The instance name, service name, edition, and build are documented.
  • An appropriate Windows identity has SQL Server administrator access.
  • Authentication mode is no broader than required.
  • SSMS was installed from Microsoft and connects to the intended instance.
  • The latest approved cumulative update was considered or applied.
  • A practice database and table can be created.
  • An inserted row remains after reconnecting and restarting.
  • A least-privilege practice identity has been tested.
  • A backup exists and restoration has been practiced.

Interview Questions and Answers

What is the difference between SQL Server and SSMS? SQL Server is the database engine. SSMS is a separate graphical client and administration tool.

What is a SQL Server instance? It is an independently configured Database Engine installation with its own services, system databases, security, settings, and user databases.

What is the difference between a default and named instance? A default instance is normally addressed by computer name alone; a named instance includes \InstanceName.

Which edition is appropriate for broad non-production learning? SQL Server 2025 Enterprise Developer provides the broad feature set but is licensed only for development and testing.

What is Mixed Mode? It permits both Windows Authentication and SQL Server Authentication.

What is GO? It is a batch separator recognized by clients such as SSMS and sqlcmd, not a T-SQL statement executed by the server.

What are master, model, msdb, and tempdb? They are system databases supporting instance metadata, new-database templates, management history and jobs, and temporary work respectively.

Key Takeaway

A dependable learning installation uses the official SQL Server 2025 download, a Developer edition appropriate to the feature boundary, Database Engine Services, Windows Authentication where possible, a documented instance name, and an explicit Windows administrator assignment. SSMS is then installed separately and used to verify the instance.

Official SQL Server 2025 download
    -> choose Developer or Express deliberately
    -> install Database Engine Services
    -> configure instance, services, and authentication
    -> add a Windows SQL administrator
    -> install current SSMS separately
    -> connect to the correct instance
    -> create sql_mastery
    -> create, insert, reconnect, and query

After verification, patch the instance, use least-privilege identities, keep repeatable schema scripts, back up valuable work, and troubleshoot service, instance, authentication, networking, and permission layers in order. Ordinary SQL learning should not require reinstalling the Database Engine.