Follow and repeat the steps for each of server database.
Open SQL Management Studio
Navigate to Object Explorer and click with right mouse button on Databases and select New Database...
In Database name area enter desired database name, by default MuOnline, Ranking and Events
In Owner area enter database owner, recommended is sa
Follow to Options in Select page area and in Recovery model set Simple
Optionally, if you want to use different Collation than configured for SQL Server itself set desired setting for Collate
Confirm changes by clicking OK
1.2 Executing Database Script
Follow to \Database\Scripts\ and find available scripts. Databases are available in selection of configuration
Me_MuOnline.sql - this is database for purpose of advanced server configuration (shared account among different servers)
MuOnline.sql - this is database for regular server configuration
Events.sql- this is database storing sort of Events information
Ranking.sql - this is database storing range of ranking information
BattleCore.sql - this is database storing data for Battle Core server purpose (Database name for BattleCore is unchangeable and must stay BattleCore)
Server Database scripts by default are configured on SQL_Latin1_General_CP1_CI_AS collation. If you need to restore your databases with different collation than default open each of selected database script in Notepad++ and replace each found SQL_Latin1_General_CP1_CI_AS with desired by you collation, e.g. for Spanish it will be Modern_Spanish_CI_AS and save the files
Navigate to SQL Management Studio and open your database scripts in it. Now by pressing F5 execute them over previously created databases. If your database names are different than default modify USE statement at beginning of each script, e.g. USE [My_Database_Name]
1.3 Configuring SQL Database User
Before going to next step create database user and set him owner privileges to previously created databases - SQL Management Studio → ObjectExplorer → Security → Right Mouse Click on Logins → New Login...
In Login name enter name of your database user (own input)
Select SQL Server authentication
In Password area enter password for the database user, make it strong enough
In Confirm password retype the password from step above
Unchecked Enforce password policy, otherwise make sure that Enforce password Expiration and User must change password at next login are unchecked.
In Default language set English
Navigate to User Mapping in Select page area
On right side in databases list click on your previously created database name and check the box in Map column then in Database role membership area below check db_owner
Repeat last step for every of server Database
2. Configuring DataServer to start
The tutorial will describe option that are necessary to be modified with your individual values for purpose of server start. Purpose and functionality of rest of the option is explained directly in the file within comments.
Follow to \Server\Files\DataServer and open IGCDS.ini file
Find WanIP = PUBLIC_IP and replace the PUBLIC_IP with your actual WAN IP, not sure? check it here
Find following part and configure database names if did not restore them with default names
Follow to the next part and configure username and password for the database user of the above - it is not advised to use super admin (sa) user
Follow to next part and configure SQL Server IP or Instance Name to Data Server will connect to. It is usually 127.0.0.1 or instance name. You can check instance name by running SQL management Studio → Right mouse click on the top level position of the tree → select Properties and in newly appeared window on the right side follow to copy value of Name property.
2.1 Battle Core Data Server
The Battle Core Data Server (IGC.DataServer_B.exe) is dedicated for purpose of Battle Core database management. Its configuration must be same as of regular Data Server with few differences only.
Battle Core Data Server does not use ExDataServer module at all, it should stay disabled so. However, it uses own Join and Data Servers - keep them enabled as on example above.
The Battle Core Data Server is operating over BattleCore database (the name of it cannot be changed). The MuOnlineDB, EventDB and RankingDB should always be configured with BattleCore database as on example above.
The MeMuOnlineDB setting should point to MuOnline database (or whatever is the name of your MuOnline database) in case you use single database, otherwise if using Me_MuOnline (shared accounts system) it should point to Me_MuOnline database (or whatever the name is in your case)
3. Running Data Server
To run Data Server simply double click IGC.DataServer.exe. If it runs and you can see logs with no error in the window then it is configured fine.
If your Data Server window hangs and freeze then configuration is not valid and Data Server cannot connect to SQL. In this case follow the tutorial again and double check configuration of the application and SQL Server.