Install SQL Server 2014/2017/2019 for MU Online
Complete guide to installing modern SQL Server versions (2014, 2017, 2019) for MU Online: when modern SQL is the right choice vs SQL Server 2008 R2, the Express vs Developer vs Standard edition comparison, the full installation walkthrough with the critical Mixed Mode authentication step, why SSMS is now a separate download and how to get it, enabling TCP/IP in Configuration Manager, database compatibility levels for running classic S6 distributions on modern SQL (setting level 100 for SQL 2008 compatibility), creating the MuServer login user with T-SQL, and the most common compatibility problems when migrating a classic distribution from SQL 2008 to SQL 2019.
Modern SQL Server versions (2014, 2017, 2019) are the right choice for current MU Online distributions and for those who want a more current, supported database platform. The installation process is similar to SQL 2008 R2 with a few important differences.
Modern SQL Server versions (2014, 2017, 2019) are the right choice for current MU Online distributions and for those who want a more current, supported database platform. The installation process is similar to SQL 2008 R2 with a few important differences.
When to use modern SQL Server vs 2008 R2
DECISION GUIDE:
USE MODERN SQL SERVER (2017 or 2019) WHEN:
→ Your distribution was compiled or updated after 2018
→ Modern S6 packs and post-S6 seasons typically support SQL 2017/2019
→ You're running Windows Server 2019 or 2022
→ SQL 2008 R2 can have installation issues on very modern Windows
→ You want long-term Microsoft support (SQL 2019 is supported until 2030)
→ Your VPS provider pre-installs SQL 2019 on their Windows images
USE SQL SERVER 2008 R2 INSTEAD WHEN:
→ Your distribution is from 2012-2016 and says "SQL Server 2008 R2" in the readme
→ You're setting up a server for the first time and want maximum predictability
→ The stored procedures in the distribution use SQL 2008-specific syntax
IN DOUBT:
→ Check your distribution's readme → follow its recommendation
→ If no recommendation: try SQL 2017 first with compatibility level 100 setEdition comparison
EDITION | COST | DATABASE SIZE LIMIT | RAM LIMIT | WHEN TO USE
----------|---------|----------------------|------------|--------------------------------
Express | Free | 10 GB per database | 1 GB | Testing, small servers (< 5K chars)
Developer | Free | None (full features) | None | Development and testing ONLY
Standard | ~$900 | None | 128 GB | Production with paying players
Enterprise| ~$15K | None | None | Very large servers, HA
FOR PRIVATE SERVER DEVELOPMENT: Developer Edition is the best free choice.
FOR PRODUCTION: Express (if DB stays under 10 GB) or Standard.Step-by-step installation (SQL Server 2019 example)
INSTALLATION WALKTHROUGH:
STEP 1 — DOWNLOAD:
→ Search "SQL Server 2019 Developer download" on Microsoft's website
→ The Developer Edition download is free
→ Download the installer (SQL2019-SSEI-Dev.exe or similar)
STEP 2 — BASIC VS CUSTOM INSTALLATION:
→ Run the installer as Administrator
→ Choose "Basic" for a quick default install (recommended for most)
→ Or "Custom" for more control over components
STEP 3 — FEATURE SELECTION (Custom path):
→ Select: "Database Engine Services" (required)
→ Optionally: SQL Server Replication, Full-Text Search
→ Leave the instance name as "MSSQLSERVER" (default instance)
STEP 4 — SERVER CONFIGURATION:
→ Service Accounts tab: keep defaults
→ Collation tab: SQL_Latin1_General_CP1_CI_AS (good for LATAM)
STEP 5 — DATABASE ENGINE CONFIGURATION (CRITICAL):
→ Authentication Mode tab:
→ Select: "Mixed Mode (SQL Server and Windows Authentication)"
← THIS IS MANDATORY — MuServer uses SQL authentication, not Windows authentication
← If you skip this step, MuServer cannot connect and shows Connect Fail
→ Set the sa password: choose a strong password
→ Write down the sa password
STEP 6 — INSTALL:
→ Review the summary → click Install
→ Takes 5-20 minutes
→ Restart the server after installationInstall SSMS separately
SSMS IS NOT INCLUDED IN THE SQL SERVER INSTALLER:
SINCE SQL SERVER 2016, SSMS IS A SEPARATE DOWNLOAD.
DOWNLOAD AND INSTALL SSMS:
→ Search "SSMS download" on Microsoft's website
→ Download the latest version (SSMS 19.x or newer — works with all SQL Server versions)
→ Run as Administrator → click Install → wait 5-10 minutes → restart
CONNECT TO SQL SERVER AFTER SSMS INSTALLS:
1. Open SSMS
2. Server name: localhost or . (period) or (local)
3. Authentication: SQL Server Authentication
4. Login: sa
5. Password: the password you set during SQL Server installation
6. Click Connect
IF IT CONNECTS: SQL Server installation is complete and working.Enable TCP/IP at port 1433
CONFIGURE NETWORK ACCESS:
1. Open SQL Server Configuration Manager:
Start → SQL Server 2019 Configuration Manager (or search for it)
2. Expand "SQL Server Network Configuration"
3. Click "Protocols for MSSQLSERVER"
4. Right-click "TCP/IP" → Enable (if Disabled)
5. Right-click "TCP/IP" → Properties
6. "IP Addresses" tab → scroll to "IPAll":
→ "TCP Dynamic Ports": delete any value (leave blank)
→ "TCP Port": type 1433
7. Click OK
8. Restart the SQL Server service:
→ "SQL Server Services" → "SQL Server (MSSQLSERVER)" → right-click → Restart
9. Verify in CMD: netstat -an | find "1433"
→ Should show: TCP 0.0.0.0:1433 LISTENINGDatabase compatibility levels for classic distributions
RUNNING CLASSIC S6 ON MODERN SQL SERVER:
WHY COMPATIBILITY LEVELS MATTER:
→ S6 distributions have stored procedures written for SQL Server 2008 syntax
→ SQL Server 2019 may interpret some queries differently or reject deprecated syntax
→ Setting the compatibility level tells SQL 2019 to process queries like SQL 2008
SET COMPATIBILITY LEVEL IN SSMS:
-- Method 1: T-SQL (recommended)
ALTER DATABASE MuOnline SET COMPATIBILITY_LEVEL = 100;
ALTER DATABASE EventMU SET COMPATIBILITY_LEVEL = 100;
ALTER DATABASE RankingMU SET COMPATIBILITY_LEVEL = 100;
ALTER DATABASE LogServer SET COMPATIBILITY_LEVEL = 100;
-- Compatibility level numbers:
-- 100 = SQL Server 2008/2008 R2 (what you want for classic S6)
-- 110 = SQL Server 2012
-- 120 = SQL Server 2014
-- 140 = SQL Server 2017
-- 150 = SQL Server 2019
-- Method 2: SSMS GUI
-- Right-click database → Properties → Options
-- "Compatibility Level" dropdown → "SQL Server 2008 (100)"
CREATE THE MUSERVER USER:
CREATE LOGIN mu_server
WITH PASSWORD = 'MuServerPass2024!',
DEFAULT_DATABASE = MuOnline,
CHECK_EXPIRATION = OFF,
CHECK_POLICY = OFF;
USE MuOnline;
CREATE USER mu_server FOR LOGIN mu_server;
EXEC sp_addrolemember 'db_owner', 'mu_server';
-- Repeat for EventMU, RankingMU, LogServerContinue with the SQL Server configuration for MU Online tutorial (database restore and ODBC setup — the same steps apply for SQL 2008 R2 and SQL 2019), the MuServer configuration tutorial (connecting the game server after the database is ready), and the SQL Server 2008 R2 tutorial (if you decide the classic version is more compatible with your distribution).
Frequently asked questions
Can I use SQL Server 2019 with MU Online Season 6?
It depends on the distribution. Classic S6 distributions from 2011-2016 were optimized for SQL Server 2008 R2 and may have stored procedures with deprecated syntax that fails on SQL 2019. Distributions from 2018 onward often support SQL 2017/2019. The test: restore the databases on SQL 2019 and run the stored procedures. If they execute without errors, the distribution is compatible. If not, setting the database compatibility level to 100 (SQL 2008 mode) usually resolves most issues.
What is the difference between Express, Developer, and Standard?
Express: free with limits (10 GB max per database, 1 GB RAM for the engine, 4 cores). Developer: free, no technical limits, but licensed for development/testing only — not for production with real players. Standard: paid, for production use, up to 128 GB RAM and 24 cores. For a private server that's in development: use Developer. For a public production server: use Standard or Express (if under 10 GB).
SSMS is no longer bundled with SQL Server?
Correct. Since SQL Server 2016, SSMS (SQL Server Management Studio) is downloaded separately from the engine installer. The engine installer sets up the database service; SSMS is the graphical management tool. Both are needed. SSMS is free and works with all SQL Server versions (2008 R2 through 2022).
How do I fix stored procedure errors when migrating from SQL 2008 to SQL 2019?
The most common fix is setting the database compatibility level to 100 (the SQL 2008 level). In SSMS: right-click the database → Properties → Options → Compatibility Level → 'SQL Server 2008 (100)'. Apply to MuOnline, EventMU, RankingMU, and LogServer. This makes SQL 2019 interpret queries using SQL 2008 rules. It solves most issues but not all — some very old syntax (like *= for outer joins) may still need manual rewriting.