Prepare the database and connect DataServer

Before you start

Complete Environment setup. This procedure creates a fresh test installation. For an existing server, back up SQL and apply only the release’s upgrade scripts; do not rerun creation scripts over player data.

• SQL Server is running and you can connect with SQL Server Management Studio.
• Your package contains DB, 1. DataServer, and IGCData folders. Keep a clean copy.
• Record the SQL instance name shown in SSMS. A named instance uses HOST\INSTANCE; localhost alone does not identify a named instance.

Match the package layout

Current Kantru source uses DataServer.ini and AllowedIPList.xml beside DataServer, ConnectServer.ini and ServerList.xml beside ConnectServer, and Data\Server\MapServerInfo.xml. Older Season 6 packages instead use IGCDS.ini, IGC_AllowedIPList.xml, IGCCS.ini, IGC_ServerList.xml, and IGCData\IGC_MapServerInfo.xml. Use the set shipped with your executable; renaming files does not upgrade a package. Numbered service folders in these examples refer to the corresponding folder in your installation.

1. Create and populate the databases

The Season 6 package has scripts for MuOnline, Me_MuOnline, Events, and Ranking. Use these names for a fresh installation unless your release specifies others.

1. In SSMS, right-click Databases → New Database. Create MuOnline, then repeat for Me_MuOnline, Events, and Ranking.
2. Open DB\MuOnline\MuOnline.sql. Confirm its USE statement selects MuOnline and run Execute (F5). Resolve errors in the Messages pane before continuing.
3. Run DB\Me_MuOnline\Me_MuOnline.sql against Me_MuOnline, then DB\Ranking and Events\Events.sql and Ranking.sql against their corresponding databases. A script’s USE statement overrides the toolbar database selection.
4. Refresh Databases. Expand MuOnline → Tables and confirm Character exists; expand Me_MuOnline → Tables and confirm MEMB_INFO exists. Keep the execution error if an object is missing.

2. Create the DataServer login

1. In SSMS, right-click the server → Properties → Security. If SQL logins are disabled, enable SQL Server and Windows Authentication mode, then restart SQL Server through SQL Server Configuration Manager.
2. Open Security → Logins → New Login. Choose SQL Server authentication and create a dedicated game-service login with a unique password. Do not require a password change on the next login for this unattended service.
3. In User Mapping, map the login to the four game databases. The legacy package may require db_owner within those databases; do not grant server-wide sysadmin or reuse sa.
4. Reconnect SSMS with the new login and exact instance name. Confirm all four databases can be opened.

3. Configure DataServer.ini

Open 1. DataServer\DataServer.ini. In [SQL], set the following keys to the actual names of your databases.

1. Set MuOnlineDB=MuOnline, MeMuOnlineDB=Me_MuOnline, EventDB=Events, and RankingDB=Ranking. Restored databases with custom names must use those actual names instead.
2. Set SQLServerName to the instance tested in SSMS. Set User and Pass to the dedicated SQL login. Never include this file in the client patch.
3. Match PasswordEncryptType to the account schema and registration tool. The supplied varchar(20) scripts use legacy unencrypted accounts (mode 0); this is a compatibility setting for the test package, not a recommended public-launch password design. Do not change an existing database to MD5 by changing only the INI. Obtain the matching account migration and registration configuration first.
4. Keep UseJoinServer, UseDataServer, and UseExDataServer enabled for the combined service. Keep MapServerInfoPath pointing to ..\Data\Server\MapServerInfo.xml.
5. Retain the internal ports 56970, 56960, and 56906 for a standard installation. Keep them private using the firewall guide.

4. Start and verify

Run DataServer from its own folder so relative paths resolve correctly.

• The log has no SQL login, missing database, or missing table error.
• JoinServer, DataServer, and ExDataServer start on their configured ports.
• If login fails, test the same instance and credentials in SSMS. If that succeeds, compare database names and login mappings.
• If a table or procedure is missing, inspect that database’s script output. Creating an empty database with a similar name does not fix a failed import.

Continue

Next: Configure connections and routing.

Reference: IGCN — Database configuration. These instructions use the Season 6 file layout; keep configuration files and tools from the same release.