What breaks MU databases most often, and what the pack files themselves show:
- UPDATE while the server runs: the server writes online characters back from memory (IGCN maintenance scripts: "Take server offline before proceeding").
- No WHERE:
UPDATE Character SET ...without WHERE changes every character. Always SELECT with the same WHERE first. - Running a full creation script on a live database: IGCN CreateDatabase.sql has
@DropExistingDatabases = 1(drops MuOnline, Me_MuOnline, Events, Ranking, BattleCore); full MuOnline scripts create the tables again. On a live server use only the update scripts, in version order (IGCN: BattleCore before MuOnline of the same version). - Password form not matching the server setting (IGCN PasswordEncryptType, MuEmu MD5Encryption) or the website setting (WebEngine none / wzmd5 / phpmd5 / sha256).
- Missing procedures after a website install: DmN setup drops and replaces WZ_CONNECT_MEMB / WZ_DISCONNECT_MEMB.
- Dropping primary keys (some Unicode migration scripts do it and never put them back): duplicates and slow queries follow.
- Collation: keep it case insensitive (IGCN documentation); all databases of one server on the same collation.
- Version: a backup never restores on an older SQL Server than the one that made it.
Always:
BACKUP DATABASE [MuOnline] TO DISK = N'C:\MUBackup\MuOnline_before_fix.bak' WITH INIT;and try risky changes on a copy (RESTORE ... WITH MOVE into MuOnline_test).
Source: IGCN CreateDatabase.sql and Maintenance Scripts, IGCN 2. Update Scripts/README.txt, DmN CMS 1.2.3 setup, WebEngine 1.2.7 install/definitions.php; Microsoft RESTORE documentation (version rule) as noted in the MuADMINS SQL guide research.