If you can avoid using SQL Server I would advice to not use it. It is really very slow (also note to not use the Native Client driver as this is not working -> tables are not showed). Connection with Access is faster but I encountered some unstabilities with it. I did not investigate it further but I guess it is a problem with too many connections towards the Access database. I have finally transported all the data into an SDF which is working much much faster.
Jon Rizzo wrote: > > > I was told specifically the oposite - that ODBC performance of SQL Server > is slower than all other ODBC providers, including Access. I have not > verified this claim, but I can tell you that selection is particularly > slow with points coming from SQL Server. I have also had a performance > problem selecting polygons if they are joined with data coming from SQL > Server. I don't know enough about the problem to know if this is a > MapGuide or a Microsoft issue but selection on my site is terribly slow > because of this. > > > Jon > > > > None None-9 wrote: >> >> Is anyone using ODBC to Access to display point layers on a production >> server? Are there known issues with selecting and overall speed? I am >> assuming yes, and if so has anyone used MS SQL for the same thing and >> notices an improvment with the Enterprise FDO? >> >> The Rock >> >> _______________________________________________ >> mapguide-users mailing list >> [email protected] >> http://lists.osgeo.org/mailman/listinfo/mapguide-users >> >> > > -- View this message in context: http://www.nabble.com/ODBC-Points-Performance-tf4201424s16610.html#a12012749 Sent from the MapGuide Users mailing list archive at Nabble.com. _______________________________________________ mapguide-users mailing list [email protected] http://lists.osgeo.org/mailman/listinfo/mapguide-users
