A spatial engine provides access to a service that can perform spatial operations, one of the available spatial engines is for SQLServer 2008.
Namespace
urn:com.cohga.server.spatial.geotools#1.0
Tags
spatialengine
Properties
Name |
Type |
Required |
Description |
id |
string |
yes |
Unique identifier |
dbtype |
'sqlserver' |
yes |
The name of the driver to use, in this case sqlserver |
host |
string |
yes |
The hostname or ip address of the SQL Server server |
port |
number |
yes |
The port number that the SQL Server instance is running on |
database |
string |
no |
The database to be connected to |
instance |
string |
no |
The SQLServer instance to be connected to |
schema |
string |
no |
The schema used when connecting to the database |
user |
string |
yes |
The userid used when connecting to the database |
passwd |
string |
yes |
The password used when connecting to the database |
minconnections |
integer |
no |
The minimum number of connections to open to the database, default 1 |
maxconnections |
integer |
no |
The maximum number of connections to open to the database, default 10 |
validateconnections |
boolean |
no |
Should database connections be checked on each access to see if they're still valid, default false |
namespace |
string |
no |
The namespace prefix |
fetchsize |
integer |
no |
The number of records read with each iteraction with the dbms, default 1000 |
connectiontimeout |
integer |
no |
The number of seconds the connection pool will wait before timing out attempting to get a new connection, default 20 seconds |
Sub-tags
None
Content
None
Examples
<spatial:spatialengine id="sqlserver"> <dbtype>sqlserver</dbtype> <host>sqlhost</host> <port>1434</port> <user>gis</user> <passwd>hak0rz</passwd> <schema>GIS</schema> <minconnection>2</minconnections> <validateconnections>true</validateconnections> </spatial:spatialengine>