Tips on reducing the size of AD (DIT) database
Hi all, Domain function Is 2008. We have 12 DCs in one domain, I notice some large differences between some of the sizes of the DIT database file. I know about the offline defrag, I guess what I'm looking for is some general advice, such as, why is one DC, DIT, 31 GB in size and others only 20 - what could cause that? Any guidance on reducing down the size, I was thinking perhaps decrease the tombstone life cycle, that would clear down the size wouldn't it?
Any help appreciated.
Any help appreciated.
Cliff Galiher
Size discrepancies is a normal byproduct of the multi-master nature of replication. As for the size, unless you *really* have a compelling reason to mess with it, it is best to leave things alone. Like any database, white space is built in and removed records leave white-space behind. The system self-tunes and messing with tombstone life, etc, can negatively impact performance, and probably won't give you the space gains you think it will.
ASKER
Hi Cliff, thanks for the response. So it's offline defrag or nothing then? I'm just wondering, if there Is no other way to reduce the size, other than delete objects and wait for tomb stone to kick in, isn't the long Gevity of AD DS in question, because the database is only ever going to get bigger and bigger all the time increasing replication and making adding additional DCs problematic as well. Just wondered what your views were?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
First of all, it is exactly these 'accurate, to the point' type responses that keep me coming back to EE. Brilliant response from you, Cliff, thank you very much for the analogy. Also thank you to Adam also. I hope points split seems fair to all. Thank you again.