KB10493 - What is the easiest way to convert a standard SHP (or other vector) format map file into a SQL database layer? Which SQL database products are supported?

The easiest option is to use the TatukGIS Editor product to export the vector map file from any TatukGIS supported vector map format, e.g., SHP, EOO, MID/MIF, TAB, DXF, DGN, TIGER, GML, VPF, DLG, SDTS, GPX, GDF, KML, etc. into a SQL database layer. The Editor can export to a number of SQL database map layer formats: i) TatukGIS SQL binary, ii) OpenGIS (OGC) SQL Simple Features Implementation, iii) Geomedia Acess Warehouse, iv) Geomedia SQL Server, v) ESRI Personal Geodatabse, vi) Oracle Spatial/Locator, vii) PostGIS, viii) Microsoft SQL Spatial Server, ix) MapInfo SpatialWare.

Alternatively, refer to the DK Any2SQL source code sample, which is located in DK-VCL and DK.NET sample set #5. The source code in this sample can be compiled into a Any2SQL test application which can be used to convert SHP (and several other vector format) files to SQL database layers of two formats: i) the TatukGIS SQL layers or ii) the OpenGIS SQL layers. The TatukGIS format is somewhat faster of the two formats. The OpenGIS format has the advantage of being openly documented (at www.opengis.org) and accepted by the OpenGIS consortium. The DK product, of course, supports other SQL database formats (either inherently or via the DK Spatial Database Extensions), but the DK Any2SQL sample does not support these other formats.

As of the DK 8.x, the DK Any2SQL sample is provided as a DK-VCL sample in Delphi and C++Builder code and as a DK.NET sample in C# and VB.NET code. If you are using the DK-ActiveX edition, refer to the Delphi, C++Builder, C#, or VB.NET code versions of this sample to learn how this functionality works and in order to create the same functionality with the DK-ActiveX edition.

The TatukGIS SQL layer format is compatible with any of the TatukGIS supported SQL database products, e.g., SQL products such as MSJET (MDB), MSSQL, MySQL, Oracle, Interbase, DB2, Advantage, sapDB, and PostgreSQL. The OpenGIS SQL database layer format is compatible with most, but not all, of these database products. For example, the OpenGIS SQL format is not compatible with PostgresSQL. Some other formats are compatible with only one or two database products. For example, the Geomedia SQL Server format works only with MSSQL Server.

For guidance on how to set up the connection between the TatukGIS product and the SQL database layer, refer to Knowledge Base item KB10765.