These forums have been archived and are now read-only.

The new forums are live and can be found at https://forums.eveonline.com/

EVE Technology Lab

 
  • Topic is locked indefinitely.
 

SDEExternalsToSql Tool (Phoebe 1.0+ compatible)

First post First post
Author
Previous Topic Next Topic
Darkblad
Doomheim
#21 - 2014-05-30 11:50:16 UTC
Darkblad wrote:
Just a short note:

Rubicon 1.4 SDE just got released
http://cdn1.eveonline.com/data/Rubicon_1.4_97069_db.zip

And the tool handled the externals w/o error, which lets me assume that it worked just fine Smile
Same applies to Kronos 1.0 SDE: http://content.eveonline.com/data/Kronos_1.0_98431_db.zip

NPE – ISD – RIP
Tuborg Uitoh
#22 - 2014-06-15 17:03:00 UTC
hey traying to get this tool to work i keep getting this error

"Connection to SQL Database: Failed
Reason was: A network-related or instance-specific error occurred while establis
hing a connection to SQL Server. The server was not found or was not accessible.
Verify that the instance name is correct and that SQL Server is configured to a
llow remote connections. (provider: SQL Network Interfaces, error: 26 - Error Lo
cating Server/Instance Specified)
Press any key to exit."

im extracting the db directly from the zip downloaded from eve website and i also trayed using it on a sqllite db from fuzzworks keeps giving me the same error... i rename all files to universDataDx.db what am i duing wrong ??
Desmont McCallock
#23 - 2014-06-15 20:18:33 UTC
You must specify the data source in the connection string at the config file. How do you expect the tool to know where the SQL server is and how you named the database?
Darkblad
Doomheim
#24 - 2014-07-10 20:58:05 UTC
The tool worked fine for the http://cdn1.eveonline.com/data/Crius_1.0_beta3.zip (i.e. no errors)

Further tables got removed from the MSSQL SDE and moved another .yaml file, as stated in today's Devblog

Removed table invBlueprintTypes
Removed table ramTypeRequirements
Removed table ramAssemblyLines
Added YAML file blueprints.yaml

NPE – ISD – RIP
Azarion Sinak
678 lost souls
#25 - 2014-07-11 01:27:39 UTC  |  Edited by: Azarion Sinak
Why the move to YAML instead of MSSQL? I don't understand the attraction to flat files versus a rationalized indexed database. Perhaps its the DBA in me, but seriously?

Is it really that hard to support both? Let those of us technically inclined to handle versioning the DB's and those that want to use flat files use them?
Calvin
Tritanium Forge Industries
#26 - 2014-07-14 22:56:08 UTC  |  Edited by: Calvin
Desmont McCallock wrote:
You must specify the data source in the connection string at the config file. How do you expect the tool to know where the SQL server is and how you named the database?


Hi Desmont, I apologize for the totally n00b question here, but... well that's a good description of my skills in this area (I nearly had a panic attack when I saw the BP material list being moved to YAML).

Where exactly do I need to change the connection string so your tool hooks up with my MS SQL database? I see the connectionStrings section in the config file, but it's all greek to me at the moment.

EDIT: After careful tinkering I figured it out. Now I need to figure out how to get it to import the blueprints.yaml file...
Hel O'Ween
Men On A Mission
#27 - 2014-07-16 17:00:16 UTC
Calvin wrote:
Now I need to figure out how to get it to import the blueprints.yaml file...


When extracting the archive, it creates two folders: SQLITEFILES and YAMLFILES, with the YAMLFILES folder holding a file appropriately named "Put yaml files here" .

Now I leave it to you to guess how to import that blueprints.yaml file ... Blink

EVEWalletAware - an offline wallet manager.
Darkblad
Doomheim
#28 - 2014-07-16 17:47:05 UTC
Hel O'Ween wrote:
Calvin wrote:
Now I need to figure out how to get it to import the blueprints.yaml file...


When extracting the archive, it creates two folders: SQLITEFILES and YAMLFILES, with the YAMLFILES folder holding a file appropriately named "Put yaml files here" .

Now I leave it to you to guess how to import that blueprints.yaml file ... Blink
Problem is, that the current version of Desmont's tool doesn't respect the blueprints.yaml (new file for crius).
First thing that comes to mind would be "what if I change its name to one of the .yaml files that Desmont's tool actually uses" - but that would break things - worst case being that the wrong data gets inserted into the wrong tables of the MSSQL database.

NPE – ISD – RIP
Calvin
Tritanium Forge Industries
#29 - 2014-07-17 02:12:08 UTC
Darkblad wrote:
Hel O'Ween wrote:
Calvin wrote:
Now I need to figure out how to get it to import the blueprints.yaml file...


When extracting the archive, it creates two folders: SQLITEFILES and YAMLFILES, with the YAMLFILES folder holding a file appropriately named "Put yaml files here" .

Now I leave it to you to guess how to import that blueprints.yaml file ... Blink
Problem is, that the current version of Desmont's tool doesn't respect the blueprints.yaml (new file for crius).
First thing that comes to mind would be "what if I change its name to one of the .yaml files that Desmont's tool actually uses" - but that would break things - worst case being that the wrong data gets inserted into the wrong tables of the MSSQL database.


Thanks Dark, that about sums up the problem. I'm starting to hit panic mode as I'm about to loose my BP material list table, which means about 85% of all my database functionality goes out the window... I love Desmont's tool, but arg, stops short of solving my problem at the moment!
Desmont McCallock
#30 - 2014-07-18 18:58:54 UTC
Guys don't panic. I will work on a new version that supports the Crius patch this weekend. Stay tuned.
Calvin
Tritanium Forge Industries
#31 - 2014-07-18 22:12:09 UTC
Desmont McCallock wrote:
Guys don't panic. I will work on a new version that supports the Crius patch this weekend. Stay tuned.


u r my hero (-:

Thanks Desmont! Anything you can do to have this ready for Crius I really appreciate!
Desmont McCallock
#32 - 2014-07-19 18:18:53 UTC  |  Edited by: Desmont McCallock
While I was working on a new version of the tool I stumbled upon a serious inconsistency in the blueprints.yaml data.
The following blueprintTypeIDs
Quote:
935,943,948,953,2864,3533,27657,27659,27661,27663,27665,27667,27938,27940,27942,27958,27960,27962,27964,27966,27968,27970,27972,27974,27976,27978,27980,27982,27984,27986,27988,27990,27992,27994,27996,27998,28000,28002,28004,28006,28008,28010,28012,28014,28016,28018,28020,28022,28024,28026,28028,28030,28032,28034,28036,28038,28040,28042,28044,28046,28048,28050,28052,28054,28056,28058,28060,28062,28064,30187,30558,30562,30582,30586,30588,30599,30600,30605,30614,30615,30618,30628,30632,30633,30752,30753,30754,33080,33082,33084
don't have a manufacturing activity thus no product type id. Each blueprint should produce one product and that makes me pretty sure that "Hiouston, we have a problem".

Calling CCPFoxFour and CCP Nullarbor to the rescue.

Until this is fixed it's not safe to release the tool.
Steve Ronuken
Fuzzwork Enterprises
Vote Steve Ronuken for CSM
#33 - 2014-07-19 18:30:15 UTC
Having a poke at those numbers, 70 of them aren't published blueprints (so they shouldn't matter).

Then there's the Primae, and the echelon blueprints, which I don't think actually exist in game.

The other 18 are for reverse engineering, and can't be manufactured from.

Woo! CSM XI!

Fuzzwork Enterprises

Twitter: @fuzzysteve on Twitter
Desmont McCallock
#34 - 2014-07-19 18:37:17 UTC  |  Edited by: Desmont McCallock
Doing a query on the Rubicon 1.2 SDE
Quote:
select * from [Rubicon 1.2].[dbo].[invBlueprintTypes] where blueprintTypeID in (935,943,948,953,2864,3533,27657,27659,27661,27663,27665,27667,27938,27940,27942,27958,27960,27962,27964,27966,27968,27970,27972,27974,27976,27978,27980,27982,27984,27986,27988,27990,27992,27994,27996,27998,28000,28002,28004,28006,28008,28010,28012,28014,28016,28018,28020,28022,28024,28026,28028,28030,28032,28034,28036,28038,28040,28042,28044,28046,28048,28050,28052,28054,28056,28058,28060,28062,28064,30187,30558,30562,30582,30586,30588,30599,30600,30605,30614,30615,30618,30628,30632,30633,30752,30753,30754,33080,33082,33084)
all have productTypeID. So I believe this is still a problem, Steve.

Edit: OK, they may not have a bill of materials but there should be a product type id in the data never the less.
Calvin
Tritanium Forge Industries
#35 - 2014-07-19 18:40:56 UTC
Desmont McCallock wrote:
Doing a query on the Rubicon 1.2 SDE all have productTypeID. So I believe this is still a problem, Steve.


Totally understand Desmont, would rather see a properly-debugged tool than a half-assed one (-: Thanks for working on this!
Desmont McCallock
#36 - 2014-07-19 18:44:21 UTC
And for those that need examples:
typeID "935" is the Reaper blueprint. You can't manufacture a Reaper (there is no bill of materials for it) but the data should mention that this blueprint produces the Reaper (588).
CCP Nullarbor
C C P
C C P Alliance
#37 - 2014-07-19 18:55:24 UTC
I will double check this week, but the blueprints.yaml does contain a lot of blueprints that never actually exist on TQ. It is currently a snapshot of everything in development whether it is published or not.

We might strip them out for the next release though.

CCP Nullarbor // Senior Engineer // Team Game of Drones
Desmont McCallock
#38 - 2014-07-26 14:39:51 UTC
The officially released SDE for Crius 1.0 still has the issue with missing productTypeID.
Desmont McCallock
#39 - 2014-07-27 15:23:36 UTC
Just released a beta version for the Crius patch. You'll find the dl link in the first post of the thread. Please report any inconsistencies you may find.
Calvin
Tritanium Forge Industries
#40 - 2014-07-27 16:21:28 UTC
Desmont McCallock wrote:
Just released a beta version for the Crius patch. You'll find the dl link in the first post of the thread. Please report any inconsistencies you may find.


Hi Desmont,

Thanks for your work on this. The blueprints stuff imported successfully, however I'm not sure I completely understand what data is going where. It looks like you re-made the old tables? Could you give some indication on what data from the blueprints.yaml file goes where exactly?

Thanks much!