Decrease in Performance after implementing Security
- Thread starter ions
- Start date
- Local time
- Today, 14:50
- Joined
- Feb 28, 2001
- Messages
- 30,562
If you implemented workgroup security correctly, the database IS encrypted.
While in theory you could affect performance badly by implementing security, it is most likely that you implemented security badly... please don't be offended by that.
The "right" way to implement security is to define a very few groups and derive all permissions from the groups. THEN create your user list and make them members of one or more of the groups. No user should ever obtain permissions from his/her individual account. Always, always, ALWAYS use the MS paradigm of a user obtaining permissions through group membership.
If you have a lot of individual users and each one has explicit rights granted, you are running into the "access control list" issue of having too many access lists to process per item. The fix for this is as stated above.
While in theory you could affect performance badly by implementing security, it is most likely that you implemented security badly... please don't be offended by that.
The "right" way to implement security is to define a very few groups and derive all permissions from the groups. THEN create your user list and make them members of one or more of the groups. No user should ever obtain permissions from his/her individual account. Always, always, ALWAYS use the MS paradigm of a user obtaining permissions through group membership.
If you have a lot of individual users and each one has explicit rights granted, you are running into the "access control list" issue of having too many access lists to process per item. The fix for this is as stated above.
All my permissions are based on 3 groups not users. I don't want to implement encryption due to 15% slow down as stated in F Scott Barker's Access Power Programming Book. The security is working very well just runnig way more slowly. It might be just something to do with the network.
Just wanted to know if this is common I guess not and the problem lies outside of security. Have to keep digging for the answer.
Just wanted to know if this is common I guess not and the problem lies outside of security. Have to keep digging for the answer.
I got rid of security and the database is running effeciently again. When I say more effeciently I mean 4x faster. The forms that take 5 seconds to load took 20 seconds with security.
Could the reason be that my client uses Windows NT 4.0? Maybe Access 2002 doesn't work well with NT 4.0?
Could the reason be that my client uses Windows NT 4.0? Maybe Access 2002 doesn't work well with NT 4.0?
Last edited:
Geoff Convery
Registered User.
- Local time
- Today, 12:50
- Joined
- Jul 21, 2006
- Messages
- 33
5 seconds sounds like an awfully long time for a form to open. Are your clients working over a Wide Area Network? If they are then a) any degredation in preformance for whatever reason will be magnified and b) I think, personally, that they're in danger of the data becoming corrupted as Access isn't too stable over WANs.
- Local time
- Today, 14:50
- Joined
- Feb 28, 2001
- Messages
- 30,562
I tend to doubt that you could see a difference of 5 seconds between opening secured vs. unsecured DB due to encryption unless you are running on a CPU that still measures its speed in 2-digit MHz.
However, if your Workgroup file is incorrectly set up, merely opening the WKG and reading the LDB might slow you down a little.
I repeat, ALL Access databases are encrypted. When you "remove" security, what you really do is change the basis of encryption from the private WKG file to the default WKG file. If you see a speed difference, it is NOT repeat NOT an encryption issue on any computer with 0.5 GHz or faster CPU.
Look to your file sharing and the speed of your network. Something IS wrong but encryption ain't it. On the other hand, if you remove the special WKG setup and replace it with the Office default WKG (which is what you REALLY do when you "remove" security), you allow folks to use their local copies of the default WKG file. Which means the problem is related to sharing that file.
However, if your Workgroup file is incorrectly set up, merely opening the WKG and reading the LDB might slow you down a little.
I repeat, ALL Access databases are encrypted. When you "remove" security, what you really do is change the basis of encryption from the private WKG file to the default WKG file. If you see a speed difference, it is NOT repeat NOT an encryption issue on any computer with 0.5 GHz or faster CPU.
Look to your file sharing and the speed of your network. Something IS wrong but encryption ain't it. On the other hand, if you remove the special WKG setup and replace it with the Office default WKG (which is what you REALLY do when you "remove" security), you allow folks to use their local copies of the default WKG file. Which means the problem is related to sharing that file.
Similar threads
