10-17-2010 03:46 PM
11-10-2010 11:14 AM
Although my workaround works for most needs, I don't believe it works for cutting remotes since I believe one can only cut a remote with data that one has access too. I found this out a while back (perhaps prior to 7.2.2) because I had 2 IDs with different team access and when accidentally using the wrong ID, no data was in the newly cut remote!
And I suspect there will also be an issue with assigning default Groups for similar reasons, at least that's what I'm seeing with this new ID.
P.S. Sorry for the original lack of formatting - I had forgot to switch to Rich Text. I was also frustrated trying to post a quick reply. It gave me some kind of error.
12-03-2010 06:45 AM
12-14-2010 08:26 AM
Did you try running SLX Profiler in order to see the differences of the SQL statements between the different users when opening the Administrator and which statement takes too long to execute?
If you find out which statement(s) takes the extra 15 seconds to execute you can optimize the query perhaps using the SLX Profiler.
12-14-2010 08:48 PM
I did try running SLX Profiler but even when I knew the answer, or so I thought, (number of Groups), I could not discern it from the Profiler logs.