New SQL File

Can someone upload a new full world SQL file release.

I’m using the script: TDB_full_world_335.64_2018_02_19.sql

Prior to running worldserver.exe and I’m running into several missing fields and general SQL fuckery.

fresh core install works fine, if you have issues you must have custom changes or you are trying to use the database on incorrect branch.

Thx man, think I used the wrong command when switching branches lol. Give us a bit then close issue if I dont run into errors though I dont think I will.

Still getting some errors:

	TrinityCore rev. 80c3304daf8a 2018-12-18 12:50:15 +0100 (3.3.5 branch) (Win64, Debug, Static) (worldserver-daemon)
<Ctrl-C> to stop.
	 ______                       __
/\__  _\       __          __/\ \__
\/_/\ \/ _ __ /\_\    ___ /\_\ \, _\  __  __
   \ \ \/\`'__\/\ \ /' _ `\/\ \ \ \/ /\ \/\ \
    \ \ \ \ \/ \ \ \/\ \/\ \ \ \ \ \_\ \ \_\ \
     \ \_\ \_\  \ \_\ \_\ \_\ \_\ \__\\/`____ \
      \/_/\/_/   \/_/\/_/\/_/\/_/\/__/ `/___/> \
                                 C O R E  /\___/
http://TrinityCore.org                    \/__/
	Using configuration file D:/WORKSPACE/TrinityCore/TrinityCoreBuild/bin/Debug/worldserver.conf.
Using SSL version: OpenSSL 1.0.2o  27 Mar 2018 (library: OpenSSL 1.0.2o  27 Mar 2018)
Using Boost version: 1.59.0
Updating Auth database...
>> Auth database is up-to-date! Containing 11 new and 115 archived updates.
Updating Character database...
>> Character database is up-to-date! Containing 8 new and 77 archived updates.
Updating World database...
>> World database is up-to-date! Containing 0 new and 0 archived updates.
Updating Hotfixes database...
>> Hotfixes database is up-to-date! Containing 0 new and 0 archived updates.
In mysql_stmt_prepare() id: 60, sql: "INSERT INTO creature (guid, id , map, spawnDifficulties, PhaseId, PhaseGroup, modelid, equipment_id, position_x, position_y, position_z, orientation, spawntimesecs, spawndist, currentwaypoint, curhealth, curmana, MovementType, npcflag, unit_flags, unit_flags2, unit_flags3, dynamicflags) VALUES (?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?)"
Unknown column 'spawnDifficulties' in 'field list'
In mysql_stmt_prepare() id: 63, sql: "INSERT INTO gameobject (guid, id, map, spawnDifficulties, PhaseId, PhaseGroup, position_x, position_y, position_z, orientation, rotation0, rotation1, rotation2, rotation3, spawntimesecs, animprogress, state) VALUES (?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?)"
Unknown column 'spawnDifficulties' in 'field list'
Could not prepare statements of the World database, see log for details.
	D:\WORKSPACE\TrinityCore\TrinityCoreBuild\bin\Debug>worldserver
TrinityCore rev. 80c3304daf8a 2018-12-18 12:50:15 +0100 (3.3.5 branch) (Win64, Debug, Static) (worldserver-daemon)
<Ctrl-C> to stop.
	 ______                       __
/\__  _\       __          __/\ \__
\/_/\ \/ _ __ /\_\    ___ /\_\ \, _\  __  __
   \ \ \/\`'__\/\ \ /' _ `\/\ \ \ \/ /\ \/\ \
    \ \ \ \ \/ \ \ \/\ \/\ \ \ \ \ \_\ \ \_\ \
     \ \_\ \_\  \ \_\ \_\ \_\ \_\ \__\\/`____ \
      \/_/\/_/   \/_/\/_/\/_/\/_/\/__/ `/___/> \
                                 C O R E  /\___/
http://TrinityCore.org                    \/__/
	Using configuration file D:/WORKSPACE/TrinityCore/TrinityCoreBuild/bin/Debug/worldserver.conf.
Using SSL version: OpenSSL 1.0.2o  27 Mar 2018 (library: OpenSSL 1.0.2o  27 Mar 2018)
Using Boost version: 1.59.0
Updating Auth database...
>> Auth database is up-to-date! Containing 11 new and 115 archived updates.
Updating Character database...
>> Character database is up-to-date! Containing 8 new and 77 archived updates.
Updating World database...
DBUpdater: Given update include directory "D:/WORKSPACE/TrinityCore/TrinityCore/sql/old/3.3.5a/world" does not exist, skipped!
>> Applying update "2018_02_19_01_world.sql" '67DC66D'...
>> Applying update "2018_03_11_00_world_2016_11_26_05_world.sql" 'FA19238'...
>> Applying update "2018_03_11_01_world_2016_12_26_07_world.sql" '94CFCF5'...
>> Renaming update "2016_11_27_00_world.sql" to "2018_03_11_02_world_2016_11_27_00_world.sql" '69B3DFA'.
>> Renaming update "2016_11_27_01_world.sql" to "2018_03_11_03_world_2016_11_27_01_world.sql" '97CFC3A'.
>> Renaming update "2016_11_27_02_world.sql" to "2018_03_11_04_world_2016_11_27_02_world.sql" 'AD2E82D'.
>> Renaming update "2016_11_27_03_world.sql" to "2018_03_11_05_world_2016_11_27_03_world.sql" '566BD2F'.
>> Applying update "2018_03_11_06_world_2016_11_27_04_world.sql" '97F9458'...
>> Applying update "2018_03_11_07_world_2016_11_29_00_world.sql" '752E872'...
>> Renaming update "2016_11_30_01_world.sql" to "2018_03_12_00_world_2016_11_30_01_world.sql" 'A0A4FA0'.
>> Renaming update "2016_12_01_02_world_335.sql" to "2018_03_12_01_world_2016_12_01_02_world.sql" 'CD633EE'.
>> Renaming update "2016_12_06_00_world.sql" to "2018_03_12_02_world_2016_12_06_00_world.sql" '55117D7'.
>> Applying update "2018_03_12_03_world_2016_12_07_00_world.sql" '00806EF'...
>> Applying update "2018_03_12_04_world_2016_12_07_01_world.sql" '09FDD7E'...
>> Renaming update "2016_12_10_00_world.sql" to "2018_03_12_05_world_2016_12_10_00_world.sql" '1968260'.
>> Renaming update "2016_12_10_01_world.sql" to "2018_03_12_06_world_2016_12_10_01_world.sql" '52CA694'.
>> Applying update "2018_03_12_07_world_2016_12_13_00_world.sql" '67D93A0'...
>> Applying update "2018_03_12_08_world_2016_12_13_01_world.sql" 'C5FE13C'...
>> Applying update "2018_03_12_09_world_2016_12_13_02_world.sql" '6453515'...
>> Renaming update "2016_12_15_00_world.sql" to "2018_03_12_10_world_2016_12_15_00_world.sql" 'B77D043'.
>> Renaming update "2016_12_18_00_world.sql" to "2018_03_12_11_world_2016_12_18_00_world.sql" 'FD90606'.
>> Renaming update "2016_12_20_00_world.sql" to "2018_03_12_12_world_2016_12_20_00_world.sql" '5AAF6FC'.
>> Applying update "2018_03_12_13_world_2016_12_22_00_world.sql" 'AB30BAB'...
>> Applying update "2018_03_14_00_world.sql" 'E50D8C8'...
>> Renaming update "2016_12_23_01_world.sql" to "2018_03_17_00_world_2016_12_23_01_world.sql" '60D4179'.
>> Renaming update "2016_12_24_00_world.sql" to "2018_03_17_01_world_2016_12_24_00_world.sql" 'FEC246E'.
>> Renaming update "2016_12_24_02_world.sql" to "2018_03_17_02_world_2016_12_24_02_world.sql" '9652F9F'.
>> Applying update "2018_03_17_03_world_2016_12_13_05_world.sql" '18009AF'...
>> Renaming update "2016_12_24_03_world.sql" to "2018_03_17_04_world_2016_12_24_03_world.sql" '708D4D3'.
>> Renaming update "2016_12_24_05_world.sql" to "2018_03_17_05_world_2016_12_24_05_world.sql" 'D3521B0'.
>> Renaming update "2016_12_24_06_world.sql" to "2018_03_17_06_world_2016_12_24_06_world.sql" 'AE9009A'.
>> Applying update "2018_03_17_07_world_2016_12_24_09_world.sql" '4D3E664'...
>> Applying update "2018_03_17_08_world_2016_12_24_10_world.sql" 'A5BBBE1'...
>> Applying update "2018_03_17_09_world_2016_12_25_00_world.sql" 'EBF92EA'...
>> Applying update "2018_03_17_10_world_2016_12_25_01_world.sql" 'EE9A606'...
>> Applying update "2018_03_17_11_world_2016_12_25_02_world.sql" '96A790D'...
>> Applying update "2018_03_17_12_world_2016_12_25_03_world.sql" 'EB8D3CD'...
>> Applying update "2018_03_17_13_world_2016_12_25_04_world.sql" '6E84FC4'...
>> Applying update "2018_03_17_14_world_2016_12_26_01_world.sql" 'F279B02'...
>> Applying update "2018_03_17_15_world_2016_12_26_03_world.sql" 'C62C0F6'...
>> Renaming update "2016_12_26_04_world.sql" to "2018_03_17_16_world_2016_12_26_04_world.sql" '09C3E07'.
>> Applying update "2018_03_17_17_world_2016_12_26_05_world.sql" 'B5B969E'...
>> Renaming update "2016_12_26_06_world.sql" to "2018_03_17_18_world_2016_12_26_06_world.sql" 'E5050CF'.
>> Renaming update "2016_12_26_07_world.sql" to "2018_03_17_19_world_2016_12_26_07_world.sql" 'CD56A2E'.
>> Renaming update "2016_12_27_00_world.sql" to "2018_03_17_20_world_2016_12_27_00_world.sql" '1DF1FA1'.
>> Applying update "2018_03_17_21_world_2016_12_27_02_world.sql" '0FB0B38'...
ERROR 1054 (42S22) at line 2: Unknown column 'PhaseId' in 'field list'
Applying of file 'D:/WORKSPACE/TrinityCore/TrinityCore/sql/updates/world/master/2018_03_17_21_world_2016_12_27_02_world.sql' to database 'world' failed! If you are a user, please pull the latest revision from the repository. Also make sure you have not applied any of the databases with your sql client. You cannot use auto-update system and import sql files from TrinityCore repository with your sql client. If you are a developer, please fix your sql query.
Could not update the World database, see log for details.

idk what you have do, but you look to have a mix of 3.3.5a and master branch.

https://i.imgur.com/DVOwiea.png

I checked out 3.3.5, ran CMAKE, re-compiled, and its still giving me another error.

Note - I’ll clone again and start from scratch I think git messed up the files somewhere along the line (maybe a bad command or something).

[CODE]
TrinityCore rev. 80c3304daf8a 2018-12-18 12:50:15 +0100 (3.3.5 branch) (Win64, Debug, Static) (worldserver-daemon)
to stop.
______ __
/__ \ __ _/\ _
/
/\ / _ __ /_\ ___ /_\ , \ __ __
\ \ /`‘__/\ \ /’ _ \/\ \ \ \/ /\ \/\ \ \ \ \ \ \/ \ \ \/\ \/\ \ \ \ \ \_\ \ \_\ \ \ \_\ \_\ \ \_\ \_\ \_\ \_\ \__\\/
___
//// ////////// `//>
C O R E /_
/
http://TrinityCore.org /
_/
Using configuration file D:/WORKSPACE/TrinityCore/TrinityCoreBuild/bin/Debug/worldserver.conf.
Using SSL version: OpenSSL 1.0.2o 27 Mar 2018 (library: OpenSSL 1.0.2o 27 Mar 2018)
Using Boost version: 1.59.0
Updating Auth database…

Auth database is up-to-date! Containing 11 new and 115 archived updates.
Updating Character database…
Character database is up-to-date! Containing 8 new and 77 archived updates.
Updating World database…
DBUpdater: Given update include directory “D:/WORKSPACE/TrinityCore/TrinityCore/sql/old/3.3.5a/world” does not exist, skipped!
Applying update “2018_02_19_01_world.sql” ‘67DC66D’…
Applying update “2018_03_11_00_world_2016_11_26_05_world.sql” ‘FA19238’…
Applying update “2018_03_11_01_world_2016_12_26_07_world.sql” ‘94CFCF5’…
Renaming update “2016_11_27_00_world.sql” to “2018_03_11_02_world_2016_11_27_00_world.sql” ‘69B3DFA’.
Renaming update “2016_11_27_01_world.sql” to “2018_03_11_03_world_2016_11_27_01_world.sql” ‘97CFC3A’.
Renaming update “2016_11_27_02_world.sql” to “2018_03_11_04_world_2016_11_27_02_world.sql” ‘AD2E82D’.
Renaming update “2016_11_27_03_world.sql” to “2018_03_11_05_world_2016_11_27_03_world.sql” ‘566BD2F’.
Applying update “2018_03_11_06_world_2016_11_27_04_world.sql” ‘97F9458’…
Applying update “2018_03_11_07_world_2016_11_29_00_world.sql” ‘752E872’…
Renaming update “2016_11_30_01_world.sql” to “2018_03_12_00_world_2016_11_30_01_world.sql” ‘A0A4FA0’.
Renaming update “2016_12_01_02_world_335.sql” to “2018_03_12_01_world_2016_12_01_02_world.sql” ‘CD633EE’.
Renaming update “2016_12_06_00_world.sql” to “2018_03_12_02_world_2016_12_06_00_world.sql” ‘55117D7’.
Applying update “2018_03_12_03_world_2016_12_07_00_world.sql” ‘00806EF’…
Applying update “2018_03_12_04_world_2016_12_07_01_world.sql” ‘09FDD7E’…
Renaming update “2016_12_10_00_world.sql” to “2018_03_12_05_world_2016_12_10_00_world.sql” ‘1968260’.
Renaming update “2016_12_10_01_world.sql” to “2018_03_12_06_world_2016_12_10_01_world.sql” ‘52CA694’.
Applying update “2018_03_12_07_world_2016_12_13_00_world.sql” ‘67D93A0’…
Applying update “2018_03_12_08_world_2016_12_13_01_world.sql” ‘C5FE13C’…
Applying update “2018_03_12_09_world_2016_12_13_02_world.sql” ‘6453515’…
Renaming update “2016_12_15_00_world.sql” to “2018_03_12_10_world_2016_12_15_00_world.sql” ‘B77D043’.
Renaming update “2016_12_18_00_world.sql” to “2018_03_12_11_world_2016_12_18_00_world.sql” ‘FD90606’.
Renaming update “2016_12_20_00_world.sql” to “2018_03_12_12_world_2016_12_20_00_world.sql” ‘5AAF6FC’.
Applying update “2018_03_12_13_world_2016_12_22_00_world.sql” ‘AB30BAB’…
Applying update “2018_03_14_00_world.sql” ‘E50D8C8’…
Renaming update “2016_12_23_01_world.sql” to “2018_03_17_00_world_2016_12_23_01_world.sql” ‘60D4179’.
Renaming update “2016_12_24_00_world.sql” to “2018_03_17_01_world_2016_12_24_00_world.sql” ‘FEC246E’.
Renaming update “2016_12_24_02_world.sql” to “2018_03_17_02_world_2016_12_24_02_world.sql” ‘9652F9F’.
Applying update “2018_03_17_03_world_2016_12_13_05_world.sql” ‘18009AF’…
Renaming update “2016_12_24_03_world.sql” to “2018_03_17_04_world_2016_12_24_03_world.sql” ‘708D4D3’.
Renaming update “2016_12_24_05_world.sql” to “2018_03_17_05_world_2016_12_24_05_world.sql” ‘D3521B0’.
Renaming update “2016_12_24_06_world.sql” to “2018_03_17_06_world_2016_12_24_06_world.sql” ‘AE9009A’.
Applying update “2018_03_17_07_world_2016_12_24_09_world.sql” ‘4D3E664’…
Applying update “2018_03_17_08_world_2016_12_24_10_world.sql” ‘A5BBBE1’…
Applying update “2018_03_17_09_world_2016_12_25_00_world.sql” ‘EBF92EA’…
Applying update “2018_03_17_10_world_2016_12_25_01_world.sql” ‘EE9A606’…
Applying update “2018_03_17_11_world_2016_12_25_02_world.sql” ‘96A790D’…
Applying update “2018_03_17_12_world_2016_12_25_03_world.sql” ‘EB8D3CD’…
Applying update “2018_03_17_13_world_2016_12_25_04_world.sql” ‘6E84FC4’…
Applying update “2018_03_17_14_world_2016_12_26_01_world.sql” ‘F279B02’…
Applying update “2018_03_17_15_world_2016_12_26_03_world.sql” ‘C62C0F6’…
Renaming update “2016_12_26_04_world.sql” to “2018_03_17_16_world_2016_12_26_04_world.sql” ‘09C3E07’.
Applying update “2018_03_17_17_world_2016_12_26_05_world.sql” ‘B5B969E’…
Renaming update “2016_12_26_06_world.sql” to “2018_03_17_18_world_2016_12_26_06_world.sql” ‘E5050CF’.
Renaming update “2016_12_26_07_world.sql” to “2018_03_17_19_world_2016_12_26_07_world.sql” ‘CD56A2E’.
Renaming update “2016_12_27_00_world.sql” to “2018_03_17_20_world_2016_12_27_00_world.sql” ‘1DF1FA1’.
Applying update “2018_03_17_21_world_2016_12_27_02_world.sql” ‘0FB0B38’…
ERROR 1054 (42S22) at line 2: Unknown column ‘PhaseId’ in ‘field list’
Applying of file ‘D:/WORKSPACE/TrinityCore/TrinityCore/sql/updates/world/master/2018_03_17_21_world_2016_12_27_02_world.sql’ to database ‘world’ failed! If you are a user, please pull the latest revision from the repository. Also make sure you have not applied any of the databases with your sql client. You cannot use auto-update system and import sql files from TrinityCore repository with your sql client. If you are a developer, please fix your sql query.
Could not update the World database, see log for details.
[/CODE]

I checked out the single branch via the command:

git clone --single-branch --branch 3.3.5 https://github.com/TrinityCore/TrinityCore.git

Re-imported SQL Files.

Re-compiled.

Works Fine Now. Thanks @Aokromes for helping me pinpoint the issue.

TrinityCore rev. d69ef2ab1d0e 2019-02-13 09:30:55 +0100 (3.3.5 branch) (Win64, RelWithDebInfo, Static) (worldserver-daemon)
to stop.


/\__  _\       __          __/\ \__
\/_/\ \/ _ __ /\_\    ___ /\_\ \, _\  __  __
   \ \ \/\`'__\/\ \ /' _ `\/\ \ \ \/ /\ \/\ \
    \ \ \ \ \/ \ \ \/\ \/\ \ \ \ \ \_\ \ \_\ \
     \ \_\ \_\  \ \_\ \_\ \_\ \_\ \__\\/`____ \
      \/_/\/_/   \/_/\/_/\/_/\/_/\/__/ `/___/> \
                                 C O R E  /\___/

http://TrinityCore.org /__/

Using configuration file F:/Trinity_Build_Lich3.3.5a/worldserver.conf.
Using SSL version: OpenSSL 1.1.1a 20 Nov 2018 (library: OpenSSL 1.1.1a 20 Nov 2018)
Using Boost version: 1.66.0
Updating Auth database…
>> Auth database is up-to-date! Containing 18 new and 115 archived updates.
Updating Character database…
>> Character database is up-to-date! Containing 8 new and 77 archived updates.
Updating World database…
>> World database is up-to-date! Containing 747 new and 3161 archived updates.
Could not prepare statements of the Character database, see log for details.

Help, I tried everything, and this happens when I run worldserver.exe. any solution please I’m new to this