We noticed that typical WMS response times using the OGR layer type for MS SQL server are 5 times slower compared to the MapServer MS SQL plugin. Maybe the OGR driver does not properly use the spatial index and always let's MapServer filter the relevant geometries? Do other users have a similar experience? At least that would make the OGR layer type unusable for us in this case. We understand that OGR layers have an extra level of abstraction but that should not create such a big performance penalty. Any hints to make the OGR layer faster?
The reason that we switched from Plugin to OGR was that the Plugin does not properly support the "gml_types" "auto" clause and always reports the column types as string. Tx Martin -- View this message in context: http://osgeo-org.1560.x6.nabble.com/MS-SQL-server-OGR-5-times-slower-compared-to-Mapserver-plugin-tp5259922.html Sent from the Mapserver - User mailing list archive at Nabble.com. _______________________________________________ mapserver-users mailing list [email protected] http://lists.osgeo.org/mailman/listinfo/mapserver-users
