How to install SQL Server 2000 for a classic MU Online server

SQL Server 2000 is the database era of MU Online's origins — versions 0.97 and 0.99. If you're running a true classic server from that era, this guide covers the complete installation with all the caveats of running old software on modern hardware.

When to use SQL Server 2000

THE DECISION:

USE SQL SERVER 2000 WHEN:
→ Your distribution is MU Online 0.97 or 0.99
→ The distribution's readme explicitly states "SQL Server 2000 required"
→ You're trying to faithfully recreate the original server experience
→ The stored procedures in the database use SQL 2000-specific syntax
  that breaks on SQL 2008 R2

USE SQL SERVER 2008 R2 INSTEAD WHEN:
→ You're starting fresh and want reliability
→ Your distribution is Season 1 through Season 6
→ The distribution's readme doesn't specifically require SQL 2000
→ You're on modern Windows and want a smooth installation
→ SQL 2008 R2 can be tested first — if the distribution works, use it

THE REALITY:
→ Most 0.97 and 0.99 distributions can actually be migrated to SQL 2008 R2
→ The migration adds a few hours of work
→ The payoff: stable service on modern hardware, actual security patches
→ Running SQL 2000 natively on Windows 10/11 is a constant battle

The virtual machine approach (recommended)

WHY A VIRTUAL MACHINE IS THE BEST APPROACH:

THE PROBLEM WITH NATIVE INSTALLATION:
→ SQL Server 2000 predates modern Windows security models
→ On Windows 10/11: the service may fail to start
→ On Windows Server 2019/2022: similar issues
→ Compatibility mode doesn't fully fix deep OS integration issues

THE SOLUTION — RUN EVERYTHING IN A VM:

TOOLS:
→ VirtualBox (free from virtualbox.org) — runs Windows XP/2003 guest
→ VMware Workstation Player (free for personal use)

OPERATING SYSTEM FOR THE VM:
→ Windows XP SP3 — easiest to get SQL 2000 running, lighter on resources
→ Windows Server 2003 SP2 — more stable for production, closer to original MU hosting

VM SETUP REQUIREMENTS:
→ Guest OS disk: 20 GB minimum
→ RAM for the VM: 512 MB - 1 GB (SQL 2000 is very light by modern standards)
→ Network: NAT (the VM shares your host's internet connection)
→ Network: Host-only adapter (for connections between host and VM)

PORT FORWARDING IN THE VM:
→ Port 1433 (SQL Server): forward from host to VM if game files are on host
→ Or: run the ENTIRE MuServer stack inside the VM alongside SQL 2000

Installation procedure

INSTALLING SQL SERVER 2000:

PREREQUISITES (install first):
→ Windows XP/2003 (native or VM)
→ Windows Installer 3.1 (may need updating on XP)
→ Internet Explorer 6.0 or later (used internally by the SQL installer)

STEP 1 — RUN THE INSTALLER:
→ Run setup.exe as Administrator
→ Choose: "SQL Server 2000 Components" → "Install Database Server"

STEP 2 — LOCAL INSTALLATION:
→ Choose: "Local Computer"
→ Installation type: "Create a new instance of SQL Server, or install Client Tools"
→ Click Next

STEP 3 — INSTANCE CONFIGURATION:
→ Default instance (MSSQLSERVER) — keep this unless you have a reason not to
→ This means you'll connect with just the computer name or "localhost" (no instance name)
→ Click Next

STEP 4 — SERVICE ACCOUNTS:
→ "Use the Local System account" for both SQL Server and SQL Server Agent
→ This is simplest for a local test environment
→ Click Next

STEP 5 — AUTHENTICATION MODE (CRITICAL):
→ Select: "Mixed Mode (Windows Authentication and SQL Server Authentication)"
→ Enter a password for the 'sa' account
→ WRITE THIS PASSWORD DOWN — you'll need it forever
→ Click Next

STEP 6 — COLLATION SETTINGS:
→ Collation: SQL_Latin1_General_CP1_CI_AS (default — good for English/LATAM)
→ Or your region's specific collation
→ Click Next → Install

STEP 7 — INSTALLATION:
→ Runs for 5-15 minutes
→ If it fails: try running in compatibility mode (XP SP2)

Applying Service Pack 4 (mandatory)

SERVICE PACK 4 — NEVER SKIP THIS:

WHY SP4 IS NOT OPTIONAL:
→ SQL Server 2000 without SP4 has critical security vulnerabilities
→ The Slammer worm of 2003 exploited a pre-SP4 SQL 2000 vulnerability
→ Without SP4, the database can crash more easily and has stability issues

INSTALL SP4 IMMEDIATELY AFTER SQL 2000:
→ Search "SQL Server 2000 SP4 download" — Microsoft still hosts it
→ Run SQL2000-KB884525-SP4-x86-ENU.exe
→ Follow the wizard — it installs over the existing SQL 2000
→ Restart the service after SP4 installs

VERIFY SP4 IS APPLIED:
→ Open Enterprise Manager (Start → Programs → SQL Server 2000 → Enterprise Manager)
→ Connect to local server
→ Right-click the server name → Properties
→ "General" tab → "Product" → should show "8.00.2039" (the SP4 build number)
→ If it shows an older build number: SP4 didn't apply correctly — reapply

Enterprise Manager and Query Analyzer

SQL SERVER 2000 MANAGEMENT TOOLS:

ENTERPRISE MANAGER:
→ The graphical tool for SQL Server 2000 (predecessor to SSMS)
→ Open: Start → Programs → Microsoft SQL Server → Enterprise Manager
→ Expand "SQL Server Group" → connect to "(local)"
→ Browse databases, tables, and execute management tasks

QUERY ANALYZER:
→ The T-SQL query editor for SQL Server 2000
→ Open: Start → Programs → Microsoft SQL Server → Query Analyzer
→ Connect with sa + your password
→ Use this to restore databases, create users, and run SQL commands

CONNECT TO THE SERVER:
→ Server name: (local) or localhost or your computer name
→ SA Login + password

RESTORE A DATABASE (.bak FILE):
-- In Query Analyzer:
RESTORE DATABASE MuOnline
FROM DISK = 'C:\databases\MuOnline.bak'
WITH REPLACE;

-- After restore: verify
SELECT COUNT(*) FROM MuOnline.dbo.Character;

Enabling TCP/IP for MuServer

ENABLE SQL SERVER 2000 TCP/IP:

1. Open "SQL Server Network Utility":
   Start → Programs → Microsoft SQL Server → Server Network Utility

2. In "General" tab: select your instance name
3. In "Enabled protocols": click "Add"
4. Select "TCP/IP" from the list → Add
5. Configure TCP/IP:
   → Default port: 1433
   → Check "Hide server" if desired
6. Click OK → restart SQL Server service

RESTART SQL SERVER SERVICE:
→ Start → Programs → Microsoft SQL Server → Service Manager
→ Select "SQL Server" → click Stop → then Start
→ Or: right-click My Computer → Manage → Services → find "MSSQLSERVER" → restart

Migration path to SQL Server 2008 R2

IF YOU WANT TO MIGRATE FROM SQL 2000 TO SQL 2008 R2:

STEP 1 — BACK UP ALL DATABASES IN SQL 2000:
BACKUP DATABASE MuOnline TO DISK = 'C:\backup\MuOnline.bak';
-- Repeat for all databases

STEP 2 — INSTALL SQL SERVER 2008 R2 ON THE SAME OR DIFFERENT MACHINE

STEP 3 — RESTORE IN SQL 2008 R2:
RESTORE DATABASE MuOnline
FROM DISK = 'C:\backup\MuOnline.bak'
WITH REPLACE;

STEP 4 — SET COMPATIBILITY LEVEL:
ALTER DATABASE MuOnline SET COMPATIBILITY_LEVEL = 80;
-- 80 = SQL Server 2000 compatibility mode
-- This makes SQL 2008 R2 interpret queries the same way as SQL 2000

STEP 5 — TEST:
→ Run the MuServer and verify connections
→ Test character loading and in-game features
→ If stored procedures fail: review them for SQL 2000-specific syntax

COMMON MIGRATION ISSUES:
→ Stored procedures using deprecated SQL 2000 syntax may need rewriting
→ The *= and =* outer join operators (SQL 2000 style) are deprecated
   → Replace with ANSI JOINs (LEFT JOIN, RIGHT JOIN)
→ Most classic MU databases migrate cleanly without changes

Continue with the SQL Server configuration for MU Online tutorial (for restoring databases and creating users — applies to both SQL 2000 and 2008 R2), the SQL Server 2008 R2 tutorial (strongly recommended if you can migrate), and the classic server creation tutorial (the full setup process for 0.97/0.99 era servers).

Frequently asked questions