[mapguide-users] SQL Server 2005

[Lockyer James]

Hi Robert
 
Thanks for that, I read some of the documents but none stated that the FDO SQL only worked if you had Map 3D - it was something I guessed by accident when I was trying to reverse engineer the process of connection.  So effective FDO to me would mean one that didn't rely on me purchasing a third software package.  
 
What information is there about FGF binary format? I've managed to create an SQL file which sorts out the meta data on the SQL file.  I'd stopped when I established that the expected datasource was in fact binary rather than GML (which was my firt thought as to how data could be stored).
 
Jim
 
 

________________________________

From: Robert Fortin [mailto:robert.fortin at autodesk.com]
Sent: Wed 04/10/2006 15:59
To: users at mapguide.osgeo.org
Subject: RE: [mapguide-users] SQL Server 2005


Jim,
 
I guess as for the documentation, it is an oversight and should be fixed.  Some of this documentation exist from the FDO side (FDG_FDODevGuide.pdf and FET_TheEssentialFDO.pdf available on the open source side)   But I agree that even there there is not enough and could be further refine.
 
Mapguide SP1 will introduce performance enhancement for reading data.  I hope that it will cover some of your concern with your Odbc case.
 
"And is there any intention of creating an effective FDO for SQL." 
 
I'm not sure what you would consider an effective provider for SQL server.  SQL Server doesn't have native support for geometry.  Therefore, we need some mechanism to deal with it.  Like I said, you can still read data out of SQL server but that has limited use if you can't get your geometry out of it.  The geometry is currently stored in FGF binary format and the database requires FDO metadata in order to work with geometry.  
 
We look at supporting geometry stored in OGC WKT format to give some flexibility for non-FDO enable database but it is not currently implemented at this time.
 
RF

________________________________

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


Cheers,
 
Can I ask why it has taken three months to point that out or why this is not mentioned in the any of the help files/ published material on the internet or for that matter why the UK resellers are unaware of this fact.  And is there any intention of creating an effective FDO for SQL.
 
In case you have X,Y,Z coordinates stored in different columns, the ODBC provider should be used against SQL Server data. - has this been speeded up in the latest release?  As when I tried this it took over 40 minutes to map out four points.
 
Has anyone thought about using GML as a storage mechanism?
 
Jim
 
James Lockyer
GIS Specialist
IM&T
Bradford and Airedale Teaching PCT
New Mill, Victoria Road, Saltaire, Shipley, West Yorkshire, BD18 3LD
 
Tel: 01274 366031
 
This email is intended for the use of the addressee only and may contain confidential information, copyright material or views/opinions that do not necessarily reflect those of the organisation. If you receive this email by mistake please advise the sender immediately. All should be aware that this email may be subject to public disclosure under the Freedom of Information Act 2000 and that emails are monitored periodically.

________________________________

From: Robert Fortin [mailto:robert.fortin at autodesk.com]
Sent: Wed 04/10/2006 14:39
To: users at mapguide.osgeo.org
Subject: RE: [mapguide-users] SQL Server 2005


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 --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/ms-tnef
Size: 11941 bytes
Desc: not available
Url : http://lists.osgeo.org/pipermail/mapguide_users/attachments/20061004/930d24a3/attachment.bin