[mapguide-users] Limiting database access does it improve performance in MGE?

[Trevor Wekel]

Hi Kent,

Typically, MapGuide will perform a describe schema when the FDO connection is first opened.  As far as I know, using a smaller subset of tables will reduce what describe schema "sees" and improve the initial connect time for the FDO connection.  In other words, describe schema doesn't have to walk the entire schema for your database.  As long as the FDO connection remains "pooled" then the schema should not be queried again.

I don't think it will affect the speed of processing the join since the connection is already established at that point.  However, if you have connection pooling disabled, then it will affect the join speed since a connection is made for every select statement.

The default FeatureService properties in serverconfig.ini will remove stale FDO connections after 8 hours and purge schema every 24 hours.

[FeatureServiceProperties]
DataConnectionTimeout = 28800
DataConnectionPoolExcludedProviders = OSGeo.SHP,OSGeo.SDF
DataConnectionPoolEnabled = 1
CacheTimeLimit = 86400

Regards,
Trevor

-----Original Message-----
From: mapguide-users-bounces at lists.osgeo.org [mailto:mapguide-users-bounces at lists.osgeo.org] On Behalf Of frosty1_4me
Sent: August 19, 2011 3:58 PM
To: mapguide-users at lists.osgeo.org
Subject: [mapguide-users] Limiting database access does it improve performance in MGE?

Hi,

There was a suggested made some time ago in a previous post I had where the
suggestion was to create a db user that only had access to the required
tables and views in the database that MGE was actually using instead of
having a user that had read access to the entire db.

I've been playing around with that concept a little and in MG Studio.  I
created a data connetion to a SQL db datasource using a limited access user
then I created another connection to the same SQL db with a user that has
read access to the entire db.  I then joined an two seperate sdfs to each of
those connections to see how quickly the tables were loaded within the
secondary class table.  The speed of establishing the join was considerable.

Now, my question is does that also translate to how fast the join is
processed in MGE when the user accesses layers that have that join
established, or is the speed really only for the sanity of the MGE author
that gets to take advantage of the quicker load time in the authoring
window?

It's a lot of work to define a user to use only the views, tables, and sp's
for each database so I need to know if all that work will translate to a
faster loading map.

thanks.

--
View this message in context: http://osgeo-org.1803224.n2.nabble.com/Limiting-database-access-does-it-improve-performance-in-MGE-tp6705093p6705093.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