System.mda performance impact
Posted on 1998-06-23
I have a database used by 4-12 people at a time. The system mda file contains all possible users - around 150. Performance is KEY in this database.
Previously I had the system.mda located on the network with the data. The icon on everyone's machine pointed to the network system.mda. This worked GREAT. Maintenance for me was a breeze because any forgotten passwords or requests for new users could be handled immediately.
However - I got the 'great' idea to offload the system.mda to the users machine to save on performance. I can tell that the login screen displays faster - but don't know how much performance gain I'm getting now. I do know that maintenance is turning into a nightmare. Users can use different PCs and now - if they change their password - the change is only reflected on the single machine. Setting up new users is no longer a simple single step process.
My question - What am I gaining besides initial load time savings by putting the system.mda (mdw) on the local machine. Specifically - how often is the system.mda accessed? Is it accessed once at log in - or for every table retrieval?
All comment are welcome - but please don't post an answer unless you KNOW how the system mda/mdw is used.