[mapguide-users] Store point geom: ODBC or Native

[Martin Morrison]

What you should be asking is really three different things.

1) ODBC
2) Native
3) MSSQL Spatial

I think there would be a general consensus that ODBC would be the slowest performing of the three.  Native is quick, it would be acceptable.  In my opinion you should be looking at MSSQL Spatial, in addition to the indexing that Zac mentioned, you also gain the benefit of spreading the workload out among other processes.  You should run benchmarks to determine your best fit.

Martin

-----Original Message-----
From: mapguide-users-bounces at lists.osgeo.org [mailto:mapguide-users-bounces at lists.osgeo.org] On Behalf Of zolinko
Sent: Friday, April 24, 2009 4:12 AM
To: mapguide-users at lists.osgeo.org
Subject: [mapguide-users] Store point geom: ODBC or Native


Hi there,

Can you tell me, how I should store point type geometry in an MSSQL server
2008 context?
Which method is preferred:
ODBC or MapGuide point type geometry?
I use Mapguide 2010 Enterprise, so it has "native" support for MSSQL
Spatial.

Has anyone some experience in the theme?

Thanks,
Zoli...
-- 
View this message in context: http://n2.nabble.com/Store-point-geom%3A-ODBC-or-Native-tp2691070p2691070.html
Sent from the MapGuide Users mailing list archive at Nabble.com.

_______________________________________________
mapguide-users mailing list
mapguide-users at lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/mapguide-users