Microsoft SQL Server and SQL Azure


GeoServer does not come built-in with support for SQL Server; it must be installed through an extension. Proceed to Installing the SQL Server extension for installation details.

Microsoft’s SQL Server is a relational database with spatial functionality. SQL Azure is the database option provided in the Azure cloud solution which is in many respects similar to SQL Server 2008.

Supported versions

The extension supports SQL Server 2008 and SQL Azure.

Installing the SQL Server extension


Due to licensing requirements, not all files are included with the extension. To install SQL Server support, it is necessary to download additional files.

GeoServer files

  1. Download the SQL Server extension from the GeoServer download page.


    Make sure to match the version of the extension to the version of the GeoServer instance!

  2. Extract the contents of the archive into the WEB-INF/lib directory of the GeoServer installation.

  3. Restart the GeoServer to load the extension.

Microsoft files

  1. Navigate to Microsoft’s JDBC driver for SQL Server and SQL Azure download page.
  2. Extract the contents of the archive
  3. If you are running Java 6 or above, copy the file sqljdbc4.jar to the WEB-INF/lib directory of the GeoServer installation. If you are running Java 5 instead (supported up to GeoServer 2.1.x) copy the file sqljdbc.jar to the WEB-INF/lib directory
  4. For GeoServer installed on Windows, copy auth\x86\sqljdbc_auth.dll and xa\x86\sqljdbc_xa.dll to C:\Windows\System32

Adding a SQL Server database

Once the extension is properly installed SQL Server will show up as an option when creating a new data store.


SQL Server in the list of vector data sources

Configuring a SQL Server data store


Configuring a SQL Server data store

host The sql server instance host name or ip address, only. Note that server\instance notation is not accepted - specify the port below, instead, if you have a non-default instance.
port The port on which the SQL server instance is accepting connections. See the note below.
database The name of the database to connect to. Might be left blank if the user connecting to SQL Server has a “default database” set in the user configuration
schema The database schema to access tables from (optional).
user The name of the user to connect to the oracle database as.
password The password to use when connecting to the database. Leave blank for no password.

max connections

min connections

Connection pool configuration parameters. See the Database Connection Pooling section for details. If you are connecting to SQL Azure make sure to set the validate connections flag as SQL Azure closes inactive connections after a very short delay.

Determining the port used by the SQL Server instance

You can determine the port in use by connecting to your SQL server instance using some other software, and then using netstat to display details on network connections. In the following example on a Windows PC, the port is 2646

C:\>netstat -a | find "sql1"
TCP   DPI908194:1918   ESTABLISHED

Using the geometry metadata table

The SQL server data store can determine the geometry type and native SRID of a particular column only by data inspection, by looking at the first row in the table. Of course this is error prone, and works only if there is data in the table. The administrator can address the above issue by manually creating a geometry metadata table describing each geometry column. Its presence is indicated via the SQL Server datastore connection parameter named Geometry metadata table (which may be a simple table name or a schema-qualified one). The table has the following structure (the table name is flexible, just specify the one chosen in the data store connection parameter):


When the table is present the store first searches it for information about each geometry column to be classified, and falls back on data inspection only if the table does not contain any information.

Previous: Oracle
Next: Teradata