Microsoft SQL Server Azure (JDBC) Reader/Writer

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

FME provides read and write access via Microsoft's JDBC driver, which is bundled with FME.

Note  For FME 2025.0, we have improved the user experience by combining spatial and non-spatial formats. Previous format identifiers:
  • Microsoft SQL Server Non-Spatial (JDBC) Reader/Writer: MSSQL_JDBC_AZURE_NONSPATIAL
  • Microsoft SQL Server Spatial (JDBC) Reader/Writer: MSSQL_JDBC_AZURE_SPATIAL

Product and System Requirements

Format

FME Platform

Operating System

Reader/Writer

FME Form

FME Flow

FME Flow Hosted

Windows 64-bit

Linux

Mac

Reader

Yes

Yes

Yes

Yes

Yes

Yes

Writer

Yes

Yes

Yes

Yes

Yes

Yes

Usage Notes

The performance of this format is dependent on the amount of memory allocated to the Java Virtual Machine (JVM). The following environment variables allow you to specify memory available to Java Plugins:

Initial heap size for initializing the JVM. If unset, the default value is 1024K.

This variable must be set in multiples of 1024 and greater than 1 MB. To indicate kilobytes, megabytes, or gigabytes, append k or K, m or M, or g or G, respectively. For example, any of these values is acceptable:

6291456

6144k

6m

Maximum heap size for initializing the JVM. If unset, the default value is 16384K.

This variable must be set in multiples of 1024 and greater than 2 MB. To indicate kilobytes, megabytes, or gigabytes, append k or K, m or M, or g or G, respectively. For example, any of these values is acceptable:

83886080

81920k

80m

Tip  To pass additional parameters used by FME to the Java Virtual Machine, use the JAVA_TOOL_OPTIONS environment variable.
Memory Usage (applicable to writers only): Changing the value in the writer parameter Features Per Transaction can control the number of features that FME places in each transaction before a transaction is committed to the database.