|
email this FAQ to a colleague
Q:
A week after my Site Sserver 3.0 site (with P&M) went live a I performed
a User import into analysis with no problems (there where only
several hundred users at this stage), but know after a month the import
fails (now there are propably several thousand users) and I get the
following:
Import Stopped - Your membership server is not configured properly to support
this export operation. Please contact the administrator of your
membership LDAP service to modify query settings appropriately. Suggested
settings would allow 'Max Result' to be unlimited and 'max Query Time'
should be 0 (unlimited).
I tried these setting with no better results. Also! Making these changes
caused a massive overhead on the server performance so I reset them
immediately. Does anyone know if there are any known issues in this area.
A:
The root cause of this problem is that SQL server is not handling the LDAP
queries quick enough. The LDAP queries are timing out. Keep in mind that UA
is really a data warehousing application. Having said that, follow these
guidelines:
- The minimum RAM for your SQL server should be 512Meg but I still
*strongly* recommend 1+ Gb RAM.
- You can get away with a dual processor SQL server, but I strongly
recommend a quad processor.
- Use NT Enterprise and SQL Enterprise.
- Don't run UA on the SQL server. UA is a single-threaded application.
It runs fastest on a 400+ Mhz *single-processor* machine. Run UA on a
separate machine.
If you think of UA as a data warehouse, these hardware requirements make
sense.UA doesn't fully utilize multiple-processors. UA runs best on fast,
single-processor machines. UA is not RAM intensive, it is CPU intensive.
SQL is RAM intensive. SQL is multithreaded, so it takes advantage of
multiple processors. Since these two programs (UA & SQL) require very
different configurations, I recommend running them on separate computers.
At this point, you are probably saying, "There is no way I will ever be able
to justify this hardware to management." Well, there is a way you increase
the LDAP query timeout. However, this increases the timeout for EVERY LDAP
query. On an underpowered SQL server, running some reports can take 3+ DAYS.
KB article Q195387 explains how to increase the LDAP query timeout. This is
not the recommended solution. It is considered a workaround.
- Alan Stuart
|
