Lesson 5: Install SQL Server (Edition Guidance + Components)

Section 5 — Lesson 5: Install SQL Server (Edition Guidance + Components)

Welcome back. Now that your OS is installed and hardened, and you understand service accounts,
it is time to install SQL Server the way a real DBA would: with clear purpose, correct components,
and repeatable decisions.

The biggest beginner mistake is clicking “Next, Next, Next” and accepting defaults without understanding what you installed.
In real DBA work, the installation choices directly affect performance, security, manageability, and troubleshooting.
This lesson teaches you the professional approach.

Lesson description: You will learn how to choose the correct SQL Server edition for a lab,
which components you actually need (and which ones you should avoid installing “just because”),
how DBAs plan instance naming and feature selection,
and how to install SQL Server with a clean, supportable configuration.
You will also learn the essential post-install checks DBAs perform to confirm the install is healthy.

1) What You Are Installing (SQL Server Components Overview)

SQL Server is not “one thing.” It is a platform made of services and features.
For DBA fundamentals, your primary focus is:

• Database Engine Services (required) — this is the core SQL Server database service
• SQL Server Agent (recommended) — scheduling jobs, backups, maintenance, automation

Other components exist, but you should install them only when you have a reason.

2) Edition Guidance (What You Should Choose for This Course)

2A) Best choice for most labs: Developer Edition

SQL Server Developer Edition is the best option for learning because it includes the full feature set
(like Enterprise) but is intended for development and learning environments.
It is excellent for a DBA lab because you can practice advanced features later if needed.

2B) Other common editions (know what they are)

• Express: free but limited (not ideal for DBA labs; missing Agent and has resource caps)
• Standard: common in many businesses, feature set is more limited than Enterprise
• Enterprise: full feature set, typically used by large organizations (licensed)
• Evaluation: time-limited Enterprise-like edition for trial environments

Course recommendation: Use Developer Edition in your lab unless you have a specific reason not to.

3) Default Instance vs Named Instance (Choose One)

3A) Default instance

• Service name typically: MSSQLSERVER
• Common for single-instance servers
• Simpler connection string: just server name

3B) Named instance

• Example: SQLLAB01\DEV
• Useful when running multiple instances on one server
• More moving parts (ports, Browser, naming)

Course recommendation: Use a default instance for your first lab build.
It is simpler, stable, and more than enough for learning.
You can add a named instance later if you want advanced practice.

4) Choose Features (Install Only What You Need)

During install, you will see a feature selection screen.
For this course, the recommended minimum is:

• Database Engine Services (required)
• SQL Server Replication (optional; only if you plan to practice replication later)
• Full-Text and Semantic Extractions (optional; common in some apps)

Strong recommendation: Install SQL Server Agent as part of Database Engine Services.
Agent is critical for learning real DBA automation.

Components you should typically skip for a first DBA lab install

• SSRS/SSAS/SSIS (unless you specifically plan to learn them now)
• Machine Learning Services (not needed for DBA fundamentals)
• PolyBase (advanced; not needed for your core DBA path)

DBA rule: Every extra component increases patching surface area, security surface area, and troubleshooting complexity.

5) Authentication Mode (Windows vs Mixed) — Choose Correctly

Windows Authentication

• Most secure and recommended when possible
• Uses Windows identities
• Clean auditing and policy control

Mixed Mode Authentication (Windows + SQL logins)

• Needed when apps require SQL logins
• Requires strong password practices
• Creates additional security responsibility

Course recommendation: Use Mixed Mode in your lab so you can practice both,
but secure it properly:
set a strong sa password and keep it stored safely.

DBA best practice: In production, use Windows authentication wherever possible and limit SQL logins.

6) Add SQL Server Administrators (Critical Step)

During install you must specify who will be SQL Server administrators.
Add:

• your primary lab admin account (your Windows login inside the VM)
• optionally, a dedicated DBA admin account if you created one

DBA warning: If you forget to add yourself as a SQL admin, you can lock yourself out and waste time fixing it.

7) Data Directories and Default Locations (Don’t Ignore This)

SQL Server stores:

• data files (.mdf/.ndf)
• log files (.ldf)
• tempdb files
• backups

For your first lab build, you can accept defaults to keep momentum.
But you must understand that in professional environments,
DBAs usually separate data/log/tempdb and control growth strategy.

Course plan: You will configure file locations more intentionally in a later lesson in this section.

8) The Installation (Step-by-Step Checklist)

1. Download SQL Server installer (Developer Edition recommended).
2. Run installer as administrator.
3. Select New SQL Server stand-alone installation.
4. Choose edition: Developer (or your chosen edition).
5. Feature selection: choose Database Engine Services (and Agent), optional extras only if needed.
6. Instance configuration: choose Default instance (recommended).
7. Server configuration: keep service accounts as recommended (virtual accounts for lab are fine).
8. Database Engine configuration:
   • Authentication: Mixed Mode (recommended for lab) or Windows-only
   • Set strong SA password if Mixed Mode
   • Add your Windows user as SQL admin
9. Install and wait for completion.
10. Reboot if required.

9) Post-Install Health Checks (DBA Must-Do)

After installation, confirm the system is healthy:

• SQL Server service is running
• SQL Server Agent service is running (if installed)
• You can connect using SSMS (next lesson covers tooling)
• Check SQL Server error log for startup errors
• Confirm you can run a basic query: SELECT @@VERSION;

Quick health check script (run after SSMS is installed)

SELECT
    @@SERVERNAME AS ServerName,
    @@VERSION    AS VersionInfo,
    SERVERPROPERTY('Edition') AS Edition,
    SERVERPROPERTY('ProductVersion') AS ProductVersion,
    SERVERPROPERTY('ProductLevel') AS ProductLevel;

DBA habit: Always document what you installed: edition, instance name, selected components, install date.

Practice (Required Before Moving On)

1. Install SQL Server Developer Edition (or your chosen edition).
2. Install Database Engine Services and ensure Agent is available.
3. Use Mixed Mode in lab (recommended) and set a strong SA password.
4. Add your Windows user as SQL admin.
5. Confirm SQL Server service is running.
6. Write down your install choices in your DBA notebook (edition, instance type, authentication mode).

Lesson Summary

• Choose the correct edition: Developer is best for learning and full-feature practice.
• Install only necessary components to reduce complexity and risk.
• Default instance is the simplest and best starting point.
• Authentication mode and admin assignment are critical installation decisions.
• DBAs always perform post-install health checks and document the install.

Next Lesson: Install SSMS and Essential Tooling

Next, you will install SQL Server Management Studio (SSMS) and the essential DBA tools
you will use throughout the course for administration, troubleshooting, and scripting.