Author: Desktop Central
I read this interesting blog by Eric in Technet blogs. It is about the Active Directory Data base size. Eric has done a test on the practical limits of Active Directory data base size. It seems he has tried with 2^31 (2147483648) objects, which made the AD data base size to grow as big as 2TB, on a ADAM (a standalone AD) version.
What i mean the practical limits here is that AD has started throwing errors while Eric tried to add objects beyond this limit.
| Quote: |
| Along the way, we did a few other perf tests (looking at increased checkpoint depths and the like) so it added a bit of time to the import. However, after about a month, I had nearly filled my 2TB partition:
06/08/2006 10:41 AM 2,196,927,299,584 adamntds.dit I created just shy of 2^31 objects. When I went to create that next object (done here by hand in LDP to illustrate the error)? ***Calling Add… ldap_add_s(ld, “cn=sample1,OU=ObjData”, [1] attrs) Error: Add: Operations Error. <1> Server error: 000020EF: SvcErr: DSID-0208044C, problem 5012 (DIR_ERROR), data -1076 If you look up -1076, you?ll find it is JET_errOutOfAutoincrementValues (from esent98.h). Woo hoo! I ran out of DNTs. |
The complete story is available in Technet also from Joeware.
