I'm experiencing huge amounts of lag in SQL Spatial layers .... compared to SDF layers, I've jsut added some code to populate a spatial index, does mapguide make use of such beasts ... can I speed the process up anymore .... select queries on these tables are completed in under a second, they are by no means large datasets
I've put the following code in place to start producing spatial indexs on my tables. CREATE SPATIAL INDEX geomIndex ON " & schema & ftable & "(geomcol1) USING GEOMETRY_GRID WITH (BOUNDING_BOX =(473358, 6945073, 553852, 7050461),GRIDS =(LEVEL_1 = MEDIUM,LEVEL_2 = MEDIUM,LEVEL_3 = MEDIUM,LEVEL_4 = MEDIUM),CELLS_PER_OBJECT = 16, PAD_INDEX = OFF, SORT_IN_TEMPDB = OFF,DROP_EXISTING = OFF, ALLOW_ROW_LOCKS = ON, ALLOW_PAGE_LOCKS = ON) Is there any other way of improving the speed of the sql spatial server datastore ... (over a minute on rendering the layer isn't going to cut it) -- View this message in context: http://osgeo-org.1803224.n2.nabble.com/sql-spatial-too-slow-still-tp5742430p5742430.html 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
