Spatial Data Server IIS

= Deployment =

Before you even get started with SDS you need to have spatial data (points, lines, polygons) loaded into a database within a supported RDBMS either in the native spatial data format supported by the database (such as Oracle Spatial) or an Enterprise Geodatabase (referred to as an ArcSDE Repository). SDS for IIS only supports SQL Server (Enterprise/Standard/Express), for any other RDBMS you'll need to use SDS for Java.

Preparing SQL Server for SDS
If you just got SDS and you want to take it for a spin, you need to first prepare your RDBMS, in this case SQL Server to work with SDS. More specifically, you need to create the logins, databases, and permissions necessary to make SDS work with SQL Server.

Step 1 - Install & Configure SQL Server
Since SDS is only supported on 64-bit platforms you should use a 64-bit version of SQL Server. You may be able to get away with using a 32-bit version of SQL Server (you're welcome to try) but if you run into any problems, move to 64-bit.

SQL Server Requirements
The following requirements should be met with any SQL Server deployment:


 * SQL Server Management Studio
 * SQL Server Database Engine

SQL Server Network Configuration
The following configuration works with Spatial Data Server (and is fairly typical of most SQL Server deployments). These settings can be managed from:

Start > SQL Server 2008 R2 > Management Tools > SQL Server Configuration Manager > SQL Server Network Configuration > Protocols for MSSQLSERVER


 * Shared Memory Properties:
 * Enabled = Yes


 * Named Pipes Properties:
 * Enabled = Yes
 * Pipe Name = \\.\pipe\sql\query


 * TCP/IP Properties:
 * Protocol Tab
 * Enabled = Yes
 * Keep Alive = 30000
 * Listen All = Yes
 * IP Addresses Tab
 * IPAll:
 * TCP Dynamic Ports = 
 * TCP Port = 1433

Firewall Configuration on SQL Server Box
Allow Inbound Port 1433

Test SQL Server is Working
Open SQL Server Management Studio and attempt to connect to the SQL Server system. If you can't:
 * One of the above settings is wrong on your SQL Server box
 * Network firewall may need to allow port 1433 to connect from your system to the SQL Server box
 * You may not have proper login credentials to your SQL Server

Any of the above are possible, all of them require IT department intervention and/or help from Microsoft Support.

Enable Database Authenication
Though Database Authentication is not technically required, it is recommended for the initial deployment, and can be turned off later:

Within SQL Server Management Studio:
 * Right-click properties of your server (top level item in the left list)
 * Click the Security Page
 * Set Server Authentication to: SQL Server and Windows Authentication mode
 * Click OK.

Step 2 - Create a Database

 * Create a new SQL Database, leave all settings default.
 * Specify a database name such as "SDS"
 * Click OK.

Step 3 - Specify Database User

 * Expand Security > Right-click Logins > New Login
 * Click "General" Tab
 * Login Name: sdsuser
 * SQL Server Authentication
 * Password: abc123!
 * User must Chagne password at next login: Uncheck
 * Click "User Mapping" Tab
 * Check Map for Database sds
 * Click OK