How to install SQL Server 2008 R2 for MU Online

SQL Server 2008 R2 is the backbone of most Season 6 MU Online private servers. This guide covers the complete installation with the specific settings that make MuServer work correctly.

SQL Server 2008 R2 editions

CHOOSING YOUR EDITION:

EDITION   | COST    | LIMITATIONS                        | RECOMMENDATION
----------|---------|-------------------------------------|--------------------------------
Express   | Free    | 10 GB max/database, 1 GB RAM cap    | Small-medium servers (< 5000 chars)
Standard  | Paid    | 64 GB RAM, 4 sockets                | Production servers planning to grow
Enterprise| Paid    | No limits                           | Large servers, HA setups

FOR MOST PRIVATE MU SERVERS:
→ Express edition is sufficient
→ The average MuOnline database for a private server is 1-3 GB
→ Only exceeds 10 GB on very large servers (10,000+ active characters with long history)

WHERE TO GET SQL SERVER 2008 R2:
→ Microsoft's official download center still hosts it
→ Search: "SQL Server 2008 R2 Express download"
→ Filename typically: SQLEXPR_x64_ENU.exe (64-bit Express)

Step-by-step installation

INSTALLATION WALKTHROUGH:

PREREQUISITES:
→ Windows (Server 2008 R2, 2012, 2016, 2019, 2022 — all work; Desktop Windows also works)
→ .NET Framework 3.5 enabled (Control Panel → Windows Features)
→ Administrator account

STEP 1 — RUN THE INSTALLER:
→ Right-click SQLEXPR_x64_ENU.exe → "Run as administrator"
→ Extraction window appears → wait for it to complete
→ "SQL Server Installation Center" opens

STEP 2 — START A NEW INSTALLATION:
→ Left panel: click "Installation"
→ Click "New SQL Server stand-alone installation or add features to an existing installation"
→ Accept the license terms → Next

STEP 3 — FEATURE SELECTION:
→ Expand "Database Engine Services" → check:
  ☑ Database Engine Services (required)
  ☑ SQL Server Replication (optional, check anyway)
→ Expand "Management Tools" (if this option appears in your installer):
  ☑ Management Tools - Basic (includes SSMS for older Express installers)
→ Click Next

STEP 4 — INSTANCE CONFIGURATION:
→ Select "Default instance"
→ Instance name: MSSQLSERVER (this is the default — keep it)
→ Instance ID: MSSQLSERVER
→ Why default instance? MuServer typically connects to the default instance.
  Named instances require additional connection string configuration.
→ Click Next

STEP 5 — SERVER CONFIGURATION:
→ "Service Accounts" tab: leave defaults (NT Authority\SYSTEM or Network Service)
→ "Collation" tab: SQL_Latin1_General_CP1_CI_AS (default — good for MU Online)
→ Click Next

STEP 6 — DATABASE ENGINE CONFIGURATION — CRITICAL STEP:
→ "Server Configuration" tab:
   → Authentication Mode: select "Mixed Mode (SQL Server and Windows Authentication)"
   ← THIS IS THE MOST IMPORTANT SETTING FOR MUSERVER
   ← Without Mixed Mode, MuServer cannot authenticate — every component shows "Connect Fail"
   ← MuServer uses SQL authentication (username = sa, password), not Windows authentication
→ Set the sa password: type a strong password
→ WRITE DOWN THE SA PASSWORD — you will need it every time you manage the database
→ "Specify SQL Server administrators": click "Add Current User" → your Windows user appears
→ Click Next

STEP 7 — INSTALL:
→ Review the summary → click Install
→ Installation takes 5-20 minutes depending on hardware
→ Green checkmarks appear for each component as it installs
→ When complete: "SQL Server 2008 R2 setup completed successfully" — click Close

STEP 8 — RESTART:
→ Restart the server after installation completes

Installing SSMS

SQL SERVER MANAGEMENT STUDIO (SSMS):

In SQL Server 2008 R2 Express, SSMS is a separate download.

FOR SQL SERVER 2008 R2 EXPRESS:
→ Search: "SQL Server Management Studio 2018 download" (SSMS 18.x works with SQL 2008 R2)
→ Or use an older SSMS version that came with SQL 2008 R2
→ Filename: SSMS-Setup-ENU.exe

INSTALL SSMS:
→ Run as Administrator → click Install → wait 5-10 minutes → restart

CONNECT TO SQL SERVER AFTER INSTALL:
1. Open SSMS from the Start menu
2. Server name: localhost or . (period) or (local)
3. Authentication: SQL Server Authentication
4. Login: sa
5. Password: [the password you set during installation]
6. Click "Connect"
7. If you see the Object Explorer with your server listed: installation is complete

TROUBLESHOOTING SSMS CONNECTION:
→ "Login failed for user 'sa'": wrong password, or sa account is disabled
   → Enable sa: right-click server → Properties → Security → change to Mixed Mode
   → Then: Security → Logins → sa → right-click → Properties → Status → Login: Enabled
→ "Cannot connect to localhost": SQL Server service isn't running
   → Check Windows Services: 'SQL Server (MSSQLSERVER)' must be Started

Enabling TCP/IP and setting port 1433

CONFIGURE NETWORK PROTOCOLS:

The SQL Server service listens on TCP/IP by default on port 1433.
But in some installations, TCP/IP is disabled. Verify and enable:

1. Open "SQL Server Configuration Manager":
   → Start → All Programs → Microsoft SQL Server 2008 R2 → Configuration Tools
   → SQL Server Configuration Manager

2. Expand "SQL Server Network Configuration"
3. Click "Protocols for MSSQLSERVER"
4. Check the status of TCP/IP:
   → If "Disabled": right-click → Enable
   → If already "Enabled": verify the port

5. Right-click TCP/IP → Properties
   → "IP Addresses" tab → scroll to "IPAll" at the bottom
   → "TCP Dynamic Ports": clear this field (delete any value)
   → "TCP Port": type 1433
   → Click OK

6. Restart the SQL Server service:
   → "SQL Server Services" in Configuration Manager → "SQL Server (MSSQLSERVER)"
   → Right-click → Restart

VERIFY TCP/IP IS LISTENING:
→ Open Command Prompt → type: netstat -an | find "1433"
→ You should see: TCP 0.0.0.0:1433 LISTENING
→ If nothing appears: the configuration didn't apply — check that you restarted the service

Creating the MuServer connection user

CREATE SQL CREDENTIALS FOR THE MUSERVER:

The MuServer components connect to SQL Server using SQL authentication.
You can use the 'sa' account, but a dedicated user is better practice.

-- In SSMS → New Query:
CREATE LOGIN muserver
WITH PASSWORD = 'MuServerPassword2024!',
     DEFAULT_DATABASE = MuOnline,
     CHECK_EXPIRATION = OFF,
     CHECK_POLICY = OFF;

-- Grant access to the MU databases:
USE MuOnline;
CREATE USER muserver FOR LOGIN muserver;
EXEC sp_addrolemember 'db_owner', 'muserver';

USE EventMU;
CREATE USER muserver FOR LOGIN muserver;
EXEC sp_addrolemember 'db_owner', 'muserver';

-- (Repeat for any other MU databases in your distribution)

NOTE:
→ For simplicity, many admins just use the 'sa' account in MuServer config
→ This is acceptable for a private server — sa already has all permissions
→ The dedicated user approach is better practice but not strictly required

Verifying the installation

VERIFY SQL SERVER 2008 R2 IS READY:

CHECKLIST:
☑ SQL Server service is running (visible in Windows Services as "MSSQLSERVER")
☑ TCP/IP is enabled in SQL Server Configuration Manager
☑ Port 1433 is listening (netstat -an | find "1433")
☑ SSMS connects successfully with sa user
☑ Mixed Mode authentication is active (SSMS → server → Properties → Security)

AFTER VERIFICATION — NEXT STEPS:
→ Restore the MuOnline database from your distribution's .bak files
→ Create the ODBC DSN (Data Source Name) that MuServer uses to connect
→ Configure the MuServer .ini files to use this SQL connection
→ Start the MuServer components and test the game connection

See the "Configure SQL Server for MU Online" tutorial for these next steps.

Continue with the SQL Server configuration for MU Online tutorial (database restore, ODBC DSN creation, and MuServer .ini settings), the MuServer configuration tutorial (after the database is set up), and the common server errors tutorial (for diagnosing any Connect Fail issues that appear after following this guide).

Frequently asked questions