SQL server (or Oracle) would be the option I would pick. Updates on the fly and a true RDBMS. Speed should not be an issue with it.
Martin Morrison Infrastructure Application Engineer/Systems Analyst Engineering Design Systems, Inc. 540.345.1410 martin.morri...@edsi.com www.edsi.com -----Original Message----- From: mapguide-users [mailto:mapguide-users-boun...@lists.osgeo.org] On Behalf Of Reservoirdog Sent: Wednesday, May 10, 2017 7:08 AM To: mapguide-users@lists.osgeo.org Subject: Re: [mapguide-users] Updating Feature Sources without restarting MG thx guys for your inputs. @Jackie, I have to stick to SQLite because of its performance-benefits. Up to 200MB size, there's quite nothing as fast as (Spatial) SQLites. Where can I check if SQLite is excluded from Connection Pooling? Also what I see often, is if I replace a SQLite-File, I cannot see any Schema-Changes e.g. when modifying a layer. So it seems, also schema-definition of the SQLites are somehow cached. Also here, restart of Mapguide or renaming the file to a new filename fixes this. @Kajar, thx for your hints. Unfortunately SHP is not a format, which can hold much attributive information, you also need one shapefile for each featureclass which gets unhandy when dealing with LARGE databases. My SQLites contain 100-200 feature classes. Something needs to have changed in the SQLite-Provider, as with the old MG-Versions re-saving the Feature Source was sufficient. -- View this message in context: http://osgeo-org.1560.x6.nabble.com/Updating-Feature-Sources-without-restarting-MG-tp5319874p5320030.html Sent from the MapGuide Users mailing list archive at Nabble.com. _______________________________________________ mapguide-users mailing list mapguide-users@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/mapguide-users _______________________________________________ mapguide-users mailing list mapguide-users@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/mapguide-users
