Supported Destination Data Sources

Two types of destination data source types are supported TAB file and SQL Server.

When uploading data, the user’s named connection choice determines which destination data source gets created. A user can choose either a file connection (which will generate a TAB file) or a SQL Server connection. Other connection types are not available to users.

  • When choosing a file connection, the uploaded table is a TAB file on the file system at a path relative to the file connections root (which the user can choose in Spectrum Spatial Analyst). If the source table is a TAB file, the same file is re-used. Otherwise, the data is converted to and saved as a new extended TAB (Native X) table. Non-spatial tables cannot save to TAB.

    When replacing an existing TAB file, it is deleted and a new TAB file created with the same name and column definitions. Any non-spatial indexes in the table are lost. When a user uploads replacement TAB files, they can choose to upload the index files if needed.

  • When choosing a SQL Server connection, the uploaded table will be a table in SQL server. Both spatial and non-spatial tables can be created. When the table includes geometry, or the user has selected an XY column, a Spatial table is created. The name connection used must let the user perform create table operations in the database.

    When replacing an existing SQL server table, it is truncated and the records from the uploaded file added to it. Any non-spatial indexes in the table are retained.

Note: When creating a new SQL server table, a MapInfo Map Catalog record is not created for the table. If a record is needed, you must manually create it. An existing record (when replacing a SQL server table, for example) is not modified or deleted. When the table that is being replaced has a different geometry type and a map catalog entry exists, you may need to manually change it to reflect the new geometry type and bounds.