Originally, the SDE was provided solely as an MS SQL server backup file. As the SDE is commonly used in environments where MS SQL is not available or would be overkill, a number of people maintain conversion routines and copies, to make it available in a more useful format.
As more formats were introduced, containing extra data, these routines were expanded to bring the data back into a single format.
As the various methods for conversion result in differing versions, with different layouts of data, conversions will be listed by the primary maintainer.
EVE SDE Database Builder is a Windows application that lets users import the SDE yaml files into MS Access, MS SQL Server, Comma Separated Values, Semi-colon Separated Values, MySQL, PostgreSQL, and SQLite. Additionally, users can customize the import by language type and selecting specific SDE yaml files to import or ignore.
Main links for the application:
Desmont provides a tool to run on Windows, to merge the other data back into the SQL Server SDE, and to convert into a variety of formats, either at full database, or individual tables.
This tool converts to a format close to the SDE as it was before CCP changed how it was produced -splitting it sqlserver, yaml and sqlite files- with blueprint information going into ramTypeRequirements. As such it should be more compatible with some older tools.
Steve provides conversions of the SDE for download, in the following formats:
.bz2 files can be unzipped with 7zip, on Windows. Historical copies are kept available. When data is migrated into alternate formats, it’s generally copied back into the old table format, but not always. The industry data, for example, is in a number of new industryActivity tables. While allowing for greater flexibility, this can break some older tools.
Conversion is performed with https://github.com/fuzzysteve/yamlloader which can target any database which SQLAlchemy can work with.