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

[frosty1_4me]

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.