Skip to content

Update Active Directory maximum limits documentation #8120

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
HerbertMauerer wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Update Active Directory maximum limits documentation #8120

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 8 additions & 0 deletions ...rverDocs/identity/ad-ds/plan/active-directory-domain-services-maximum-limits.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -215,9 +215,17 @@ In real-world deployments, errors begin to appear when the object approaches the

For more information about the limit, see the [AD database details article](/previous-versions/windows/it-pro/windows-server-2003/cc772829(v=ws.10)#maximum-database-record-size), [many DNS records on a single DNS name](/troubleshoot/windows-server/identity/problems-with-dc-ad-integrated-dns-zones), and [Active Directory replication error 8304: The maximum size on an object has been exceeded](/troubleshoot/windows-server/identity/active-directory-replication-error-8304).

Note this also applies to schema objects, for example how many attributes you can add to a class with "maycontain" attribute values. In this case you can add additional attribtues through auxiliary classes.
Copy link

Copilot AI Feb 6, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This note introduces schema-specific terms but doesn't follow the document's existing formatting conventions. Consider converting it to a NOTE admonition (the doc already uses >[!NOTE] blocks) and formatting schema keywords as code (e.g., mayContain) rather than quoted strings; also use the canonical casing for the schema attribute name.

Suggested change
Note this also applies to schema objects, for example how many attributes you can add to a class with "maycontain" attribute values. In this case you can add additional attribtues through auxiliary classes.
> [!NOTE]
> This limit also applies to schema objects, for example how many attributes you can add to a class with `mayContain` attribute values. In this case, you can add additional attributes through auxiliary classes.

Copilot uses AI. Check for mistakes.
Copy link

Copilot AI Feb 6, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Typo: "attribtues" should be "attributes".

Suggested change
Note this also applies to schema objects, for example how many attributes you can add to a class with "maycontain" attribute values. In this case you can add additional attribtues through auxiliary classes.
Note this also applies to schema objects, for example how many attributes you can add to a class with "maycontain" attribute values. In this case you can add additional attributes through auxiliary classes.

Copilot uses AI. Check for mistakes.

## Maximum size of Active Directory objects

When you want to add object data beyond the database limit, you get an error like:
The server side error is: 0x2024 The administrative limit for this request was exceeded.
The extended server error is:
00002024: SvcErr: DSID-0205089D, problem 5008 (ADMIN_LIMIT_EXCEEDED), data -1026
Comment on lines +222 to +225
Copy link

Copilot AI Feb 6, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The error output example should be formatted as a fenced text code block for readability and consistency with earlier sections (for example, the LDAP bind error output is in a ```text block). Also consider using a consistent hex format (e.g., 0x00002024 to match `00002024`) and hyphenating "server-side".

Copilot uses AI. Check for mistakes.

To change an attribute with a lot of data, you must store the new and old values in the database transaction. Storing the values lets you roll back the transaction if the database shuts down in the middle of the transaction. The maximum size of a transaction limits the total blob size of attribute value data to 5 MB.

The maximum size of the Active Directory transactions that you can perform also affects the limit of how many group members you can have before link-value replication and how many transactions in group membership changes exist.

Another related limit is the number of attributes that can be populated on an AD object. In testing we find 830-950 non-linked attributes can be populated with 8KB database page size. With 32KB database pages, you can get to about 2500 attributes. If you have the need to store this many attributes, you should consider having additional child objects for your purpose.
Copy link

Copilot AI Feb 6, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This paragraph introduces new numeric limits but is inconsistent with terminology/number formatting used elsewhere in the doc (for example, earlier sections use "nonlinked" and thousands separators like "1,200"). Consider aligning to "nonlinked", using "8 KB"/"32 KB" spacing, and formatting "2,500" with a comma. Also, since these are testing-derived figures, add a citation or clearly scope the statement (for example, specify the test environment/Windows Server version) so readers understand how broadly it applies.

Suggested change
Another related limit is the number of attributes that can be populated on an AD object. In testing we find 830-950 non-linked attributes can be populated with 8KB database page size. With 32KB database pages, you can get to about 2500 attributes. If you have the need to store this many attributes, you should consider having additional child objects for your purpose.
Another related limit is the number of attributes that can be populated on an AD object. In internal Microsoft lab testing, we find that approximately 830-950 nonlinked attributes can be populated with an 8 KB database page size. With 32 KB database pages, you can get to about 2,500 attributes. If you have the need to store this many attributes, you should consider having additional child objects for your purpose.

Copilot uses AI. Check for mistakes.