Microsoft SQL Server Spatial Reader/Writer

FME can read and write spatial and attribute data held in live Microsoft SQL Server database tables.

FME provides read and write access to live Microsoft SQL Server databases via Microsoft's ActiveX Data Objects (ADO).

Microsoft SQL Server Spatial Product and System Requirements

Dependencies  Microsoft OLE DB Driver 18.x for SQL Server (Note: Microsoft OLE DB Driver 19 is not yet supported by FME.)
Microsoft System CLR Types for SQL Server 2012 (installed with FME except in silent installs).
Microsoft .NET Framework v4.5.2.

FME connects to SQL (Azure) Servers first using Microsoft OLE DB Driver 18.x for SQL Server. If the OLE DB Driver is not found, FME tries to connect again using the 2012 Native Client.
The 2012 Native Client supports SQL Server 2005 and above, including Azure Servers.
The 2008 Native Client supports SQL Server 2005 and above, but does not support Azure Servers.
For spatial reading and writing, Microsoft System CLR Types for SQL Server 2012 and Microsoft .Net 4.5.2 are required.

Format

Platform

Operating System

Reader/Writer

FME Desktop License

FME Server

FME Cloud

Windows 64-bit

Linux

Mac

Reader

Available in FME Professional Edition and higher

Yes

No

Yes

No

No

Writer

Available in FME Database Edition and higher

Yes

No

Yes

No

No

FME Workbench Reader Overview

Click the Reader Parameters button and establish a Microsoft SQL Server Spatial database connection.

FME considers a database dataset to be a collection of relational tables. Arbitrary where clauses and joins are fully supported.

FME Workbench Writer Overview

Click the Writer Parameters button and establish a Microsoft SQL Server Spatial database connection.

The Microsoft SQL Server Spatial writer module stores attribute records into a live relational database. The Microsoft SQL Server Spatial writer provides the following capabilities:

  • Transaction Support: The writer provides transaction support that eases the data loading process. Occasionally, a data load operation terminates prematurely due to data difficulties. The transaction support provides a mechanism for reloading corrected data without data loss or duplication.
  • Table Creation: The writer uses the information within the FME mapping file to automatically create database tables as needed.