Trinity needs 3 databases to run at 3.3.5 branch - Auth, Characters, and World:

Open your worldserver.conf,  go to the "UPDATE SETTINGS" section and set the following settings:

Updates.EnableDatabases = 7

Copy the file starting with "TDB_full_" to the directory where your worldserver.exe is. Follow the next steps of the guide and at the first start of the server the databases will be set-up automatically.

Keeping the DB up to date

Both core and DB fixes will be committed to the TrinityCore repository, which you may also view in Git Extensions by following the "Fetch" instructions in Keeping the Source Up-to-Date. Pending fixes can be found on our tracker with data from the developers and contributors.

It is recommended to stay on the same revision as the TDB_full database (Beginner).

Note: You can run the following query on the World database to see your current DB and core revision:

SELECT * FROM `version`;

This assumes that you have completed the previous steps of the installation guide.

Note: If you have made any custom changes to your database, you may wish to backup (export) all three of them (world, characters, and auth) before performing the next few steps.

Thanks to the automatic DB updater the single step you have to do, is to fetch a new revision (Keeping the Source Up-to-Date) and the appropriate updates will we applied at server startup.

Trinity needs 4 databases to run at 6.x branch - Auth, Characters, Hotfixes and World:

The following steps are done using the database management program you installed in Step1: Requirements (ex. HeidiSQL or SQLYog):

• In HeidiSQL, click on the database you want to use in order to "select" it, then click Tools > Load SQL File... > (select the file) > Run file(s) directly.
• In SQLYog, click on the database you want to use in order to "select" it, then click Database > Import > Execute SQL Script.
• On mysql cli you must use mysql --default-character-set=utf8 to avoid import failures
  • WE STRONGLY RECOMMEND TO USE THIS METHOD over the SQLYog or HeidiSQL, it is by far the fastest method to import TDB and it's needed updates.

1. Create the three databases by importing ...\sql\create\create_mysql.sql from your cloned TrinityCore repository. You now have three databases - auth, characters, and world. You may need to refresh your program in order to see the new databases.
2. Click on the "auth" database and import the auth database structure by importing ...\sql\base\auth_database.sql from your cloned TrinityCore repository.
3. Click on the "characters" database and import the characters database structure by importing ...\sql\base\character_database.sql from your cloned TrinityCore repository.
4. Click on the "world" database and import the world database structure by extracting and importing the "TDB_full_*.sql" file you downloaded from the Database download section.
5. Click on the "Hotfixes" database and import the hotfixes database structure by extracting and importing the "TDB_hotfixes_*.sql" file you downloaded from the Database download section. ( it was in the same 7z file as the "TDB_full_*.sql")
6. Click on the "world" database and import any *.sql file available in your ...\sql\updates\world folder from your cloned TrinityCore repository. THIS IS MANDATORY or your core very likely will fail to start.
7. Click on the "hotfixes" database and import any *.sql file available in your ...\sql\updates\hotfixes folder from your cloned TrinityCore repository. THIS IS MANDATORY or your core very likely will fail to start.
8. NOTICE WE NEVER IMPORT sql\updates\auth or sql\updates\character files from your cloned TrinityCore repository or the ones on update_only inside TDB file on fresh installation, those files are for update trinitycore not for fresh install.
9. NEVER ENABLE CONTINUE ON ERROR ON YOUR SQL CLIENT

Keeping the DB up to date

Both core and DB fixes will be committed to the TrinityCore repository, which you may also view in Git Extensions by following the "Fetch" instructions in Keeping the Source Up-to-Date. Pending fixes can be found on our tracker with data from the developers and contributors.

As mentioned earlier, it is recommended to stay on the same revision as the TDB_full database (Beginner).

If you choose to brave the wilds beyond the current monthly revision, use the (Advanced) instructions below.

Note: You can run the following query on the World database to see your current DB and core revision:

SELECT * FROM `version`;

This assumes that you have already completed the (Beginner) Keeping the Source Up-to-Date, which means you now have a newly downloaded revision archive.

This instruction also assumes that you have completed the initial Downloading the Database which had you import the TDB_FULL.sql, and it is now approximately one month later - a new revision has been released.

Note: If you have made any custom changes to your database, you may wish to backup (export) all three of them (world, characters, and auth) before performing the next few steps.

• Beginners
  • Extract the TDB_FULL.sql file from the archive and import it into your world database.
  • If they exist, also import the characters_ and auth_ .sql files into their respective databases.
  • Once this is finished and you have already compiled your source, you may run the worldserver binary to load your server. The revision update is complete.

Note: It is at this point that most user errors occur. If your worldserver.exe closes abruptly, make sure that your core's version matches your database version. Check that the `version` table in your world database matches the commit hash listed beside the archive you downloaded at TrinityCore Downloads.

• Advanced Users

If you update your source beyond a monthly revision, you will likely have additional updates in the ...\sql\updates folder from your cloned TrinityCore repository. The folders within show which database they need to be imported to. For example, the "world" folder has all of the files that need to be imported to your world DB.

File naming conventions follow simple and consistent rules:

yyyy_mm_dd_id_world*.sql -> World DB

yyyy_mm_dd_id_character*.sql -> Characters DB

yyyy_mm_dd_id_auth*.sql -> Auth DB

Note: The incremental daily id starts at 00, with 00 needing to be imported first, then 01, then 02, etc.

It is imperative to know the date of your previous revision when updating in order to import all of the updates from that revision to your current one.

Then, simply follow these steps:

• Browse into your ...\sql\updates\world folder from your cloned TrinityCore repository and import all*_world*.sql files into your world DB that have a date later than your previous revision.
• Browse into your ...\sql\updates\hotfixes folder from your cloned TrinityCore repository and import all*_hotfixes*.sql files into your world DB that have a date later than your previous revision.
• Do the same above step for the characters and auth folders from your cloned TrinityCore repository, if they exist. If these folders don't exist, there have not been any characters or auth database updates.

copy /b world\*.sql /b all_world_updates.sql