How to Migrate SQL Server 2000 Database to SQL Server 2019 in MU

Migrating a MU Online database from SQL Server 2000 to SQL Server 2019 requires intermediate steps — there is no direct upgrade path. This guide covers the complete process, from the initial backup to reconnecting the GameServer.

Why an intermediate server is required

SQL Server 2019 does not support restoring backups generated by SQL Server 2000 (compatibility level 80). The mandatory upgrade path is:

SQL Server 2000 → SQL Server 2008 R2 (intermediate) → SQL Server 2019

If your server already runs SQL Server 2008 or 2012, you can skip the first leg and start from the intermediate server step.

Step 1 — Full backup on SQL Server 2000

1.1 Open SQL Server Enterprise Manager (SQL 2000) → expand the server → right-click MuOnline under Databases → All Tasks → Backup Database.

1.2 Configure the backup:

• Backup type: Database - complete
• Destination: add path C:\Backup\MuOnline_2000.bak
• Check Overwrite existing media

1.3 Click OK and wait for completion. Verify the backup file:

-- Run in Query Analyzer to verify integrity
RESTORE VERIFYONLY FROM DISK = 'C:\Backup\MuOnline_2000.bak'

Step 2 — Restore on SQL Server 2008 R2 (intermediate server)

2.1 On the server running SQL Server 2008 R2, open SQL Server Management Studio (SSMS).

2.2 Right-click Databases → Restore Database:

• To database: MuOnline_v2008
• From device: select C:\Backup\MuOnline_2000.bak
• Options tab: check Overwrite the existing database (WITH REPLACE)

2.3 Run the restore. If a physical file error appears (.mdf/.ldf), adjust paths in the Files tab:

RESTORE DATABASE MuOnline_v2008
FROM DISK = 'C:\Backup\MuOnline_2000.bak'
WITH MOVE 'MuOnline_Data' TO 'C:\SQL\Data\MuOnline_v2008.mdf',
     MOVE 'MuOnline_Log'  TO 'C:\SQL\Log\MuOnline_v2008.ldf',
     REPLACE;

2.4 Raise the compatibility level to 100 (SQL 2008):

USE master;
ALTER DATABASE MuOnline_v2008 SET COMPATIBILITY_LEVEL = 100;
GO

2.5 Identify deprecated data types before proceeding:

USE MuOnline_v2008;
GO
SELECT TABLE_NAME, COLUMN_NAME, DATA_TYPE
FROM INFORMATION_SCHEMA.COLUMNS
WHERE DATA_TYPE IN ('text', 'ntext', 'image')
  AND TABLE_CATALOG = 'MuOnline_v2008'
ORDER BY TABLE_NAME;

2.6 Convert each flagged column. Example for T_Character:

-- Convert deprecated types to modern equivalents
ALTER TABLE T_Character  ALTER COLUMN MemoInfo    NVARCHAR(MAX);
ALTER TABLE T_GuildMember ALTER COLUMN GuildMasterMemo NVARCHAR(MAX);
-- Repeat for every row returned by the query above

Step 3 — Generate a clean backup on SQL 2008 R2

3.1 With the database fixed, generate a clean backup:

BACKUP DATABASE MuOnline_v2008
TO DISK = 'C:\Backup\MuOnline_2008.bak'
WITH FORMAT, COMPRESSION, STATS = 10;

3.2 Verify backup integrity:

RESTORE VERIFYONLY FROM DISK = 'C:\Backup\MuOnline_2008.bak';

Step 4 — Restore on SQL Server 2019

4.1 Copy MuOnline_2008.bak to the server running SQL Server 2019.

4.2 In SSMS connected to SQL 2019, run:

RESTORE DATABASE MuOnline
FROM DISK = 'C:\Backup\MuOnline_2008.bak'
WITH MOVE 'MuOnline_Data' TO 'C:\Program Files\Microsoft SQL Server\MSSQL15.MSSQLSERVER\MSSQL\DATA\MuOnline.mdf',
     MOVE 'MuOnline_Log'  TO 'C:\Program Files\Microsoft SQL Server\MSSQL15.MSSQLSERVER\MSSQL\DATA\MuOnline_log.ldf',
     REPLACE, STATS = 5;
GO

4.3 Raise compatibility to SQL 2019:

ALTER DATABASE MuOnline SET COMPATIBILITY_LEVEL = 150;
GO

4.4 Enable recommended performance options:

ALTER DATABASE MuOnline SET RECOVERY SIMPLE;
ALTER DATABASE MuOnline SET AUTO_UPDATE_STATISTICS ON;
ALTER DATABASE MuOnline SET PAGE_VERIFY CHECKSUM;
GO

Step 5 — Recreate SQL login and permissions

SQL 2000 logins are not automatically transferred to SQL 2019.

5.1 Create the login used by GameServer (e.g., muonline):

USE master;
CREATE LOGIN muonline WITH PASSWORD = 'YourStrongPassword123!',
    DEFAULT_DATABASE = MuOnline,
    CHECK_EXPIRATION = OFF,
    CHECK_POLICY = OFF;
GO

5.2 Map the login to the database and grant permissions:

USE MuOnline;
CREATE USER muonline FOR LOGIN muonline;
ALTER ROLE db_owner ADD MEMBER muonline;
GO

Step 6 — Reconfigure ODBC and GameServer.ini

6.1 On the game server Windows machine, open the 64-bit ODBC manager: C:\Windows\System32\odbcad32.exe

6.2 Go to System DSN tab → Add → select ODBC Driver 17 for SQL Server (download from https://aka.ms/downloadmsodbcsql if not installed).

6.3 Configure:

• Name: GameServer (or whatever name already appears in the ini)
• Server: 127.0.0.1 or the SQL 2019 server IP
• SQL Authentication: login muonline and password

6.4 Edit GameServer/GameServer.ini:

[ServerInfo]
DBAddr    = 127.0.0.1
DBPort    = 1433
DBID      = muonline
DBPwd     = YourStrongPassword123!
DBName    = MuOnline

Step 7 — Post-migration verification

7.1 Verify row counts on key tables to confirm data integrity:

USE MuOnline;
SELECT 'T_Account'   AS TableName, COUNT(*) AS Total FROM T_Account
UNION ALL
SELECT 'T_Character', COUNT(*) FROM T_Character
UNION ALL
SELECT 'T_Item',      COUNT(*) FROM T_Item
UNION ALL
SELECT 'T_Guild',     COUNT(*) FROM T_Guild;

7.2 Start DataServer.exe and check the log at DataServer/Log/DataServer_YYYYMMDD.log — no connection errors should appear.

7.3 Start GameServer.exe and ConnectServer.exe. Test login with a GM account.

7.4 Confirm character stats, positions, and items are intact:

SELECT Name, Class, Level, Strength, Dexterity, Vitality, Energy
FROM T_Character
WHERE Name = 'YourCharacterName';

Common troubleshooting

Perguntas frequentes