[mapguide-users] SQL Server 2005

[Robert Fortin]

The SQL Server provider is intented to work with datastore created with
Map 3D 2007 inside SQL Server 2000 and 2005.
It has it's own geometry storage and spatial indexing mechanism.
Although it could reverse engineer existing database, this would be done
for non-spatial data only as it has no mean to identify geometry
property in the database.
 
In case you have X,Y,Z coordinates stored in different columns, the ODBC
provider should be used against SQL Server data.
 
Just wanted to make sure the provider was not being used for what it was
not design for.
 
RF

  _____  

From: Lockyer James [mailto:James.Lockyer at bradford.nhs.uk] 
Sent: Wednesday, October 04, 2006 2:59 AM
To: users at mapguide.osgeo.org
Subject: RE: [mapguide-users] SQL Server 2005


Supported yes - does it work... now that's the question.

 
  _____  

From: Gord McKenzie [mailto:gord.mckenzie at canam.com]
Sent: Tue 03/10/2006 22:04
To: users at mapguide.osgeo.org
Subject: RE: [mapguide-users] SQL Server 2005



Thanks

 

  _____  

From: Warren Medernach [mailto:warren.medernach at imaginit.ca] 
Sent: Tuesday, October 03, 2006 1:33 PM
To: users at mapguide.osgeo.org
Subject: RE: [mapguide-users] SQL Server 2005

 

Hello Gord,

 

I was informed by the ADN that the FDO provider supports: SQL Server
2000 (SP4) and SQL Server 2005.

 

Warren Medernach

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.osgeo.org/pipermail/mapguide_users/attachments/20061004/49544551/attachment.html