...
Installing Trinity Database (
...
TDB)
About once per month all of the updates made from all previous months are combined into a few bulk .sql files to easily import them into your databases. These updates are similar to how Service Packs are released for Windows. Furthermore, smaller, individual .sql updates are occasionally added as the core is fixed by the developers (these can be seen in Git Extensions while selecting individual commits in the commit view with the Diff tab selected). This offers two options:
- (Beginner) It is highly recommended to keep your current revision (the commit in bold text in Git Extensions) on a commit with a description similar to "DB: TrinityDB revision XX: move SQL updates to the old directory" (example). These commit descriptions mark each monthly compilation, and are also useful for knowing when a new compilation is released and can be downloaded/imported. Doing this will keep your databases 100% up-to-date each month.
- (Advanced) If you decide to update your revision outside of a commit with the above description, you must also import all of the smaller .sql updates (C:\Trinity\sql\updates folder) that have been done with EACH commit up to yours, if there are any. Not importing these additional updates cause a majority of user errors. This will ensure that your databases are 100% up-to-date.
This is described in more detail in the following instructions.
Downloading the Database
Download the latest database compilation from TrinityCore Downloads.
...
| Advertencia | ||
|---|---|---|
| ||
Note: There are multiple .sql files to choose from in the .7z archive. If this is your first time installing TrinityCore, you will want to import ONLY the file with "TDB_full" at the beginning. If you downloaded TDB 53 or higher NEVER apply sql files on sql\old directory, those files are only needed for people updating core between TDB releases dates. NEVER ENABLE CONTINUE ON ERROR ON YOUR SQL CLIENT. Also, you don't need to run sql files inside update_only on 1st installations.
|
Installing The Trinity Databases
Trinity needs 3 databases to run - Auth, Characters, and World:
...
| Advertencia | ||
|---|---|---|
| ||
IF THIS IS YOUR FIRST TIME INSTALLING TrinityCore DON'T apply any *.sql fileon sql\updates\auth or sql\updates\characters. Continue with SETTING UP THE SERVER. NOTICE YOU STILL NEED TO APPLY sql\updates\world files. |
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.
...
| Sugerencia | ||
|---|---|---|
| ||
If your world database is ever corrupted (ex. creatures or objects are accidentally deleted), it is easy to revert it back to its original state by re-importing the TDB_FULL.sql into your world database. If you updated your core using the (Advanced) instructions, make sure you also re-import all of the necessary C:\Trinity\sql\updates as explained above. |