Microsoft KB Archive/262047

= Data Is Always Stored on the Same Partition in Membership Database =

Article ID: 262047

Article Last Modified on 5/10/2000

-

APPLIES TO


 * Microsoft Site Server 3.0 Standard Edition

-



This article was previously published under Q262047



SYMPTOMS
When the Membership database is partitioned across multiple databases, data may always get stored on the same partition. For example, the following unique CN values are placed on the same partition because the first 16 characters are the same:

cn=aasd000a0a180005

cn=aasd000a0a180006



CAUSE
The hash algorithm used to determine the partition value only uses the first 16 characters. In the previous example, the same partition value is generated because the first 16 bytes are the same for each.



WORKAROUND
To work around this issue, do one of the following:
 * Add a &quot;must have&quot; attribute of GUID to the custom class and change the naming attribute to GUID rather than CN?.
 * Use a namespace-partition scheme rather than value partitions (separate containers and/or partitions for a specific series set of Macintosh addresses).
 * Reverse the entries so that the unique characters are at the beginning of the RDN.
 * Truncate or abbreviate the first set of characters for a known series of Macintosh addresses so that the objects are correctly partitioned when you use value partitions.



STATUS
Microsoft has confirmed that this is a problem in Microsoft Site Server 3.0.

Keywords: kbprb KB262047

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.