FME can read and write attribute data held in live Microsoft SQL Server database tables. This data may not necessarily have a spatial component to it.
FME provides read and write access to live Microsoft SQL Server databases via Microsoft's ActiveX Data Objects (ADO).
Microsoft SQL Server Non-Spatial Product and System Requirements
|
FME connects to SQL (Azure) Servers first using the Microsoft OLE DB Client. This client ships with the FME installer. |
|
If the OLE DB Client is not found, FME will try to connect with the Microsoft SQL Server 2012 Native Client. If the 2012 Native Client is not found, FME tries to connect again using the 2008 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. |
|
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 Professional Edition and higher |
Yes |
No |
Yes |
No |
No |
FME Workbench Reader Overview
Click the Reader Parameters button and establish a Microsoft SQL Server Non-Spatial database connection.
FME considers a database data set to be a collection of relational tables. The tables must be defined in the workspace before they can be read. Arbitrary where clauses and joins are fully supported.
FME Workbench Writer Overview
Click the Writer Parameters button and establish a Microsoft SQL Server Non-Spatial database connection.
The Microsoft SQL Server writer module stores attribute records into a live relational database. The Microsoft SQL Server writer provides the following capabilities:
- Transaction Support: The Microsoft SQL Server 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 Microsoft SQL Server writer uses the information within the workspace to automatically create database tables as needed.