I am trying to create a new dynamic group. The filter is not complicated but has 9 different criterias. When i press the "View members" button it takes around 7-8 seconds to show all 3600 members. But when I try to submit the group, I get an error. In the eventlog I can see the request timed out. My guess is, that when submitting, the service tries to calculate the membership executing the sql job. So is there anywhere that I can "tune" the job?

I had the same issue (well for a set): http://social.technet.microsoft.com/Forums/en-US/ilm2/thread/0b41e178-5f2b-4edc-9267-0439b19bf6d8 It's on my todo list to post an update/blog entry about it. What solved it for me: * creating the set gradually: set one criteria, click submit, add another one click submit, .... What was probably related to the issue: * fragmented indices on the FIMService SQL DB (the fim.objectValueReference) table. By browsing the folders below the table you can see the indices and ask the properties + view the fragmentation for each of them. Or click rebuild all on the indices and see what the current fragmention is (it won't do anyting untill you click ok) (credits to Jeroen, a colleague of mine with more SQL knowledge than I :) ) P.S. I did a rebuild of the indicies two days ago. But when doing a lot of changes it's advised to do it more regulary I guess http://setspn.blogspot.com

Søren, what part of my answer was the answer? build the query bit by bit or the rebuild of the indexes? For future reference, I got a blogpost about how to find out where SQL is killing you: http://setspn.blogspot.com/2010/10/case-of-attributes-that-didnt-wanted-to.html http://setspn.blogspot.com