SpatialWare ®

Version 4.9.2 for Microsoft® SQL Server 2008

INSTALLATION GUIDE
Information in this document is subject to change without notice and does not represent a commitment on the part of the vendor or its representatives. No part of this document
may be reproduced or transmitted in any form or by any means, electronic or mechanical, including photocopying, without the written permission of MapInfo Corporation,
One Global View, Troy, New York 12180-8399.
© 2009 MapInfo Corporation. All rights reserved. Portions © 2004 Stopwatch Maps, Inc. All rights reserved. MapInfo, the MapInfo logo, MapInfo Professional, and
SpatialWare are trademarks of MapInfo Corporation and/or its affiliates.
MapInfo Corporate Headquarters:
Voice: (518) 285-6000
Fax: (518) 285-6070
Sales Info Hotline: (800) 327-8627
Government Sales Hotline: (800) 619-2333
Technical Support Hotline: (518) 285-7283
Technical Support Fax: (518) 285-6080
Contact information for all MapInfo offices is located at: http://www.mapinfo.com/contactus.
Adobe Acrobat® is a registered trademark of Adobe Systems Incorporated in the United States.
Products named herein may be trademarks of their respective manufacturers and are hereby recognized. Trademarked names are used editorially, to the benefit of the trademark
owner, with no intent to infringe on the trademark.
April 2009
Table of Contents

Chapter 1: Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
Key Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4
Product Inventory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4
Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4
Sample Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4
Sample Queries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4
Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4
Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5
Installation Structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5
Questions About Upgrading? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5
Chapter 2: Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
Selecting a SQL Server Instance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8
Local or Remote Installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8
Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8
Additional Steps for Installing on Windows Cluster . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9
Testing Your Installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9
Post Installation Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10
Uninstall SpatialWare . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10
Removing a Remote SpatialWare Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10
Chapter 3: Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Install Log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .12
Installation Error Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .12
Maximum Stored Procedure Nesting Level Exceeded. . . . . . . . . . . . . . . . . . . . . . . . . .12
Incorrect Reference to Older DLL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .12
Error Message: "This string is too long." . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .12
Error Message: Incompatible Version of MDAC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .12
Appendix A: Glossary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

<Book Title> 1
2 <Product Name & #>
Introduction
1
Welcome to SpatialWare for Microsoft® SQL Server 2008. This guide explains
how to install and set up SpatialWare for Microsoft SQL Server 2008. It contains
tips and information for this version of the software only. Subsequent shipments
of the software may or may not contain a similar guide.
MapInfo SpatialWare for Microsoft SQL Server 2008 will be referred to as
SpatialWare in this guide.
This chapter introduces you to SpatialWare’s components and features, and
orients you to get the most out of the product.

In this chapter:
Š Key Features. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4
Š Product Inventory. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4
Š Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5
Š Installation Structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5
Š Questions About Upgrading? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5
Key Features

Key Features
SpatialWare has the following benefits and features:

• A complete integration of spatial and attribute data.

• Data security.
• Scalability. The spatial data type enhancements are implemented entirely on the server side to
exploit the scalability offered by Microsoft SQL Server.
• A rich set of spatial functions that follow the OGC naming and parameter specifications for
spatial functions in SQL.
• Standards compliance.
• Ease of use.
• Programmatic interfaces. SpatialWare requires no middle tier to access the database, so you
can access SpatialWare functionality through standard programmatic interfaces such as JDBC
and ODBC.

Product Inventory
Your copy of SpatialWare includes software, sample data, sample queries, and documentation.

Software
SpatialWare software is provided to integrate with Microsoft SQL Server 2008.

Sample Data
SpatialWare includes sample data for experimenting with data retrieval and analysis. The following
sample data are installed with SpatialWare:

• Georgetown database – A sample database that many of the examples in the User Guide
reference.
Sample data are automatically installed into the SQL Server instance specified during SpatialWare
installation.

Sample Queries
Sample queries on the Georgetown database are provided to show the advantages and
implementations of using SQL Server and SpatialWare for spatial data management.

Sample queries are installed into SpatialWare’s demo/Query directory.

Documentation
SpatialWare documentation consists of the following:

• Installation Guide – This guide provided in PDF form.

4 Spatialware 4.9.2 for SQL Server 2008

 Chapter 1:

• User Guide – Installed with your software and accessible by pointing your Internet browser to the
index.htm page in SpatialWare’s doc directory. Also provided as a PDF file on the software
media.
You can view online (HTML) documentation on a Windows, Macintosh, or UNIX computer running
version 4 or later of Internet Explorer or Netscape, or running a current version of Mozilla or Safari.

The online documentation uses JavaScript. If you encounter difficulty viewing the documentation,
ensure that JavaScript is enabled in your browser.

Requirements
SpatialWare is supported with Microsoft SQL Server 2008 on the following platforms:

• Windows XP Professional 32 and 64-bit (Service Pack 2)

• Windows Server 2003 (Service Pack 2)
• Windows Server 2003 x64 (Service Pack 1)
To view the online User Guide you need version 4 or later of Internet Explorer or Netscape, or a
current version of Mozilla or Safari.

About 70 MB of disk space is necessary to install the SpatialWare software.

Installation Structure
SpatialWare components are installed in two locations: the \Binn subdirectory of SQL Server, and
the SpatialWare subdirectory under the Program Files directory of Windows (for example,
C:\Program Files\SpatialWare 4.9). The latter contains the following subdirectories:

• bin – Scripts used by SpatialWare.

• s9_info – Message files used by SpatialWare.
• demo – Demonstrations and samples.
• dB – Sample Georgetown data.
• Query – Sample queries for Georgetown data.
• doc – Documentation. Point your Internet browser to the index.htm file in order to view the online
User Guide.
• log – SpatialWare’s log file.

Questions About Upgrading?

For those of you who are upgrading from a previous release of SpatialWare, this section addresses
some of the questions that you may have.

Do I need to re-spatialize my existing database?

No. The installation wizard upgrades all attached spatial databases.

Installation Guide 5
Questions About Upgrading?

Do I need to spatialize any new databases that I create on my SpatialWare server?

Yes. You will have to spatialize any new databases using the sp_spatialize_db procedure. Refer to
the User Guide for instructions.

6 Spatialware 4.9.2 for SQL Server 2008

Installation
2
This chapter provides important installation and pre-installation instructions, and
describes how to test the installation.

In this chapter:
Š Selecting a SQL Server Instance . . . . . . . . . . . . . . . . . . . . . . . . . . .8
Š Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8
Š Uninstall SpatialWare . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10
Selecting a SQL Server Instance

Selecting a SQL Server Instance

Local or Remote Installation

SpatialWare can be installed locally, if SQL Server is installed locally. It can also be installed
remotely on the same network machine where SQL Server is running. For a local install you will
need Local Administrator privileges. For a remote installation, you will need Operating System
Administrator privileges. If you are on a workgroup network you will need Administrator rights on the
domain.

To configure databases and install data, you will need Database Administration privileges. A new
installation of SQL Server, by default, will give you database privileges. If you are working with an
existing SQL Server installation, then it is possible that the security options have been reconfigured.
In this case, you may need to consult with your Database Administrator to ensure that you have
database administration privileges set up for your user ID before installing the server component.

The server install wizard checks for these privileges and notifies you if they are not in place.

If you plan to perform a remote installation, installing across a network to the SQL Server database
machine, you must first map a drive to that machine. You can do this by choosing Tools > Map
Network Drive from your Windows Explorer dialog.

If it is necessary for the DBA to install the server component, they should perform a local installation
on the machine running SQL Server. SpatialWare can be installed on the default or any named
instance of SQL Server.

Note that if you install SpatialWare on more than one instance on the same server, you have to
select correct installation directories for each instance of SpatialWare.

The directory naming has changed from SQL Server 2005 to SQL Server 2008. The new naming
conventions are discussed below:

The default instance ID is constructed using the following format:

MSSQL for the Database Engine, followed by the major version number and a period, followed
by the instance name. For example, a default instance name (MSSQLSERVER) will produce a
directory structure as follows:
C:\Program Files\Microsoft SQL Server\MSSQL10.MSSQLSERVER\MSSQL\Binn\

If using a named instance of SQL Server, this name will replace the default instance name:
C:\Program Files\Microsoft SQL Server\MSSQL10.MyInstance\MSSQL\Binn\

Installation
SpatialWare can be installed locally or remotely to SQL Server. If choosing a remote installation:

• The client machine must have SQL Server 2008 client installed.
• If the remote machine is running Windows XP or above, you must log in with system
administrative privileges.

8 Spatialware 4.9.2 for SQL Server 2008

 Chapter 2:

To install SpatialWare, run the program setup.exe on the SpatialWare CD-ROM to install
SpatialWare files. Follow the instructions provided in the dialogs. During the installation you are
prompted to:

1. Specify if this is a local or a remote installation to SQL Server. You also have the option of
installing documentation only.
2. Choose the SQL Server instance.
For a remote installation, if you choose "(another)" from the list of instances, you are asked to
provide the instance name.
3. If a previous installation of SpatialWare is detected, then you are asked if you want to upgrade it
to the current version.
4. Reboot the installation machine.
It is suggested that you reboot your installation machine to have all registry settings take effect.
Note If an error occurred during installation and you did not obtain a hostname and hostid, refer to
Troubleshooting on page 11. For a remote installation, you will have to run the
lmhostid.exe utility to obtain the hostname and hostid. This utility can be run from the bin
subdirectory where SpatialWare is installed.

You should now test your installation.

Additional Steps for Installing on Windows Cluster

To install SpatialWare 4.9.2 on SQL Server 2008 deployed in a Windows Cluster, you have to install
SpatialWare on each node.

In addition, you need to store your databases on the shared disk. Therefore, if you would like to use
the Georgetown database on Windows Cluster, you have to follow these additional steps:

1. After deploying SpatialWare on each node, login to the active node and copy the Georgetown
database files (georgetown_Data.MDF and georgetown_Log.LDF) to the shared disk (for
example, to Q:\Microsoft SQL Server\MSSQL10.MSSQLSERVER\MSSQL\Data).
2. Using SQL Server Management Studio, detach the Georgetown database that was installed by
SpatialWare and attach the version of the same database you copied to the shared disk.

Testing Your Installation

Sample queries are provided to test the installation with the Georgetown database. This database
installs by default with SpatialWare into the Data subdirectory where SQL Server is installed. It is
made available so that you have a spatial data set to explore and experiment with. It is also referred
to by the examples in the SpatialWare User Guide.

To test the installation, choose georgetown from the Query Analyzer’s database list, and run the
georgetown_demo.sql script located under SpatialWare’s demo/Query subdirectory. This script
contains sample queries.

If an error occurs, please do the following:

1. Reboot your installation machine if you have not already done so after installing.
2. Choose the georgetown database from the DB list before running the georgetown_demo.sql
script.

Installation Guide 9
Uninstall SpatialWare

3. Send your query and error messages to swsupport@mapinfo.com for assistance. Refer to
Install Log on page 12 for the location of SpatialWare error messages.

After a successful installation, you are ready to use SpatialWare.

Post Installation Setup

Refer to the SpatialWare User Guide for information on how to get started with your SpatialWare
software and for setting up your data.

Uninstall SpatialWare
To remove SpatialWare from your system, stop SQL Server, and then choose Start > Settings >
Control Panel > Add/Remove Programs. Select the SpatialWare instance you want to remove.

If you want to clean your database first, remove spatial data from your tables using SQL Server
tools, remove indices, despatialize the table columns, and then uninstall SpatialWare.

Removing a Remote SpatialWare Installation

If you installed SpatialWare 4.9.2 on a remote machine, to remove it do the following manually:

1. Stop SQL Server.

2. Remove the SpatialWare DLLs in the \Binn subdirectory of the SQL Server install.
3. Delete the MapInfo\SpatialWare 4.9 registry key with all its subkeys.

Detach and delete the SpatialWare databases, or move them to another location.

10 Spatialware 4.9.2 for SQL Server 2008

Troubleshooting
3
This chapter contains troubleshooting notes.

In this chapter:
Š Install Log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .12
Š Installation Error Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .12
Install Log

Install Log
A log of the install procedure is named spwmssql.is and is located in the user's temporary directory
(for example, C:\Documents and Settings\UserName\Local Settings\Temp). You can review this log
if you require detailed information about the installation.

Installation Error Messages

Maximum Stored Procedure Nesting Level Exceeded

Every spatial database must have its "Recursive triggers" setting turned OFF.

This can be managed through Enterprise Manager, by selecting a database and following Properties
> Options > Settings. If this setting is on, you can expect some insert and update operations to fail
with the message:

"A cursor with the name ... already exists."

Or

"Maximum stored procedure nesting level exceeded..."

Incorrect Reference to Older DLL

In case of an upgrade, if SpatialWare keeps reporting an older version number when executing exec
sp_spatial_query 'select hg_version() from hg_onerow', make sure that no directory listed in the
PATH environment variable contains an older version of libspatialware.dll. If this happens to be the
case, either rename or remove the older version of the DLL and then restart the system.

Error Message: "This string is too long."

The message, "This string is too long", may appear during installation instead of a failure message if
your PATH environment variable is longer than 255 characters. To remedy the problem, you will
have to reduce the length of your PATH.

Error Message: Incompatible Version of MDAC

When you are installing SpatialWare on some versions of Windows XP you may receive the
following error message: "MDAC 2.8 RTM is incompatible with this version of Windows." If this
occurs, click Cancel, and the installation will continue without problem.

12 Spatialware 4.9.2 for SQL Server 2008

Glossary
A
Client Machine
The machine where client application programs reside. Client applications
access a SpatialWare database on a server machine to read or modify
data. Typically, client machines are for individual users and their
applications. Client machines may access common server machines. The
more powerful server machines handle intensive processing and large
volume data storage.
Coordinates
Coordinates are a set of numbers used to define the location of any place
on the surface of the earth. SpatialWare supports many different coordinate
systems.
MapInfo Map Catalog
MapInfo clients store coordinate system information and symbology on a
per-table basis in the MAPINFO_MAPCATALOG table. To determine the
coordinate system that a SpatialWare table is stored in, a MapInfo client
accesses the MAPINFO_MAPCATALOG table.
RDBMS
Relational Database Management System
Server Machine
The machine where server application programs reside. The SpatialWare
database resides on a server machine, which can be accessed by
applications from a client machine.
Spatial Object
Synonym for a geometry defined by the ST_Spatial string. A spatial object
could be empty, or comprised of a single geometry, or a geometry
collection.

Spatial Table
A table is considered “spatializable” if it has a column of type ST_Spatial,
and “spatial” if it has been spatially enabled using the
sp_sw_spatialize_column procedure.

Spatialize
To spatially enable a table using the Spatialize Column procedure. This is
necessary to save spatial data to a table. Note that the table must first
contain a column of type ST_Spatial.
 Spatially Enable
A database must be spatially enabled in order for SpatialWare to use it. This involves running scripts
on the database to install SpatialWare components, and create the spatial type necessary to work
with SpatialWare.
Spatial Database
A database that is set up to hold spatial data.
Spatial Data
Data with information on location, position, size, and shape.
SQL
Structured Query Language

14 Spatialware 4.9.2 for SQL Server 2008

 Appendix A:

Installation Guide 15
Index

C O
Client machine, defined 13 Online docs 4–5
Coordinate systems, defined 13 Options, installation 8
Overview 3
D
P
DB list 9
Definitions 13–14 Prerequisites, installation 5
Documentation 4–5 Product specifications 4–5

E Q
Error messages Query Analyzer 9
installation 12
log file 12 R
G RDBMS definition 13
Remote removal 10
georgetown_demo 9
Glossary 13–14 S
H Scripts, georgetown_demo 9
Server machine 13
HTML docs 4–5 setup.exe 9
Spatial data, definition 14
I Spatial database definition 14
Installation 7 Spatializing tables, definition 13
error messages 12 Spatially enabling databases, definition 14
prerequisites 5 SQL definition 14
remote 8 Standard installation procedure 8–9
testing 9 T
Installation, options 8
Testing, installation 9
K Troubleshooting 11
Key Features 4 U
M Uninstall
MAPINFO_MAPCATALOG, defined 13 procedure 10
remote installation 10

Installation Guide 16