Hi,
oh my god what have i started here. Please don't try to convince me that standards are important and slapd pricecly implents RFC 2696, i was already convinced of that before i started the discussion. Anyway i like to resond to Howard Chu because he mentioned something dangerous and wrong regarding Active Directory (somewhat of topic here) but i like to avaoid people following his suggestion:
Howard Chu hyc@symas.com wrote:
Here is why i believe others might run into the same issue. If you
need
to create a ldap client dealing with big search results for various
LDAP
directories you had to use 1.2.840.113556.1.4.319 even if you are
only
interested in collecting the entire result otherwise you would fail
with
Active Directory.
Nonsense. You simply ask your AD administrator to raise the default
sizelimit,
the same way you would ask an OpenLDAP administrator to do the same
thing.
Well about 6 years ago when i first noticed this problem, i asked Microsoft about that limit and yes you can use ntdsutil.exe to set MaxPageSize to a higher limit:
http://support.microsoft.com/kb/315071/en-us
But it is strongly recommend to not change it!!!! Over the years i have seen quite some Active Directories customers and many of them are very afraid when you ask them you change some configuration or extending the schema. In 2001 SAP's IT set MaxPageSize=10000 for a few weeks as a temporary workaround until i was able to provide a real solution. That was a long time ago and today SAP's and probably most other companies Active Directories are running with default values. 1.2.840.113556.1.4.319 and MaxPageSize had not been invented to make our life more difficult. A good article about it is e.g. http://searchwinit.techtarget.com/tip/0,289483,sid1_gci1265206,00.html. I like to close with Gary Olsen's conclusion "The best practice for setting MaxPageSize is to leave it alone."
Best regards Randolf