I understand the difference between link/unlink vs. enable/disable at the .rep/.unv level…but I don’t understand the difference at the domain level. I’ve tested and read all the docs I can find and searched thru archives and knowledge exchanges but haven’t found anything on this topic. Can someone please enlighten me?
Thanks.
baked (BOB member since 2002-09-05)
It works the same way. If you are disabling everything at the top level, then re-enabling things (docs, unvs, domains, it doesn’t matter) at a lower level, then you are slowing down your login process and requiring BusObj to do additional work.
Think of it this way. If you have a resource enabled at the top level, it is inherited all the way down the chain. Now, suppose that you have a resource linked at the top level but disabled. That’s two things to check. Now you re-enable that resource at a lower level. That’s three things to check. Multiply 3 by the number of users and the number of resources, and that’s a lot of data to process. 
Now, unlink the item at the top level, and relink it down lower where it’s needed. Now there’s only one thing to check.
Any time you can eliminate 2/3 of your data it’s a good thing. 
Even if you have a very small group of users, using the strategy of linking / unlinking can show dramatic improvements for repository access.
Dave
Dave Rathbun 
(BOB member since 2002-06-06)