SQL Server Spatial FDO Provider - Installation Notes

Installing SQL Server 2008

For the install, make sure that you select the option to allow for both Windows and SQL Server Authentication.

Once SQL Server 2008 is installed, run SQL Server Configuration Manager (Start->Programs->SQL 2008->Config tools). Select 'Protocols for MSSQLSERVER' on the left (under SQL Server Network Configuration) and then enable the 'TCP/IP' protocol. You will have to restart the server after this, which you can do with this tool as well. Choose SQL Server Services on the left and restart SQL Server.

Setting up the provider.

At this time, until we build an actual install tool, what we’re doing to set this up for MapGuide Open Source 2.0 and other clients is to edit the current FDO providers.xml file and add a <FeatureProvider> entry for SQL Server Spatial. The first step is to take the new SQL Server Spatial Provider dlls and drop them into the fdo bin directory of your client application (e.g. C:\Program Files\Autodesk\!MapGuideEnterprise2009\Server\Bin\Fdo). Once that is done, update the providers.xml file in those directories by adding the entry for the SQL Server Spatial provider.

Here is the <FeatureProvider> section to add for the SQL Server Spatial provider:

<FeatureProvider>
  <Name>OSGeo.SQLServerSpatial.3.3</Name> 
  <DisplayName>OSGeo FDO Provider for SQL Server Spatial</DisplayName> 
  <Description>Read/Write access to feature data in a MS SQL Server spatially enabled data store. Supports geospatial and non-geospatial data and schema.</Description> 
  <IsManaged>False</IsManaged> 
  <Version>3.3.0.0</Version> 
  <FeatureDataObjectsVersion>3.3.0.0</FeatureDataObjectsVersion> 
  <LibraryPath>SQLServerSpatialProvider.dll</LibraryPath> 
</FeatureProvider>

Now, after installing the new dll's as described above, you can run MG 2009 or other clients based on FDO 3.3. Connect to 'localhost' and use the sa user and pwd that you defined when installing SQL 2008 or other SQL Server user account that you created.