Yes, the problem is not using the restrictions too much (that is exactly why
Exchange caches restrictions), but applying *different* restrictions.

Dmitry Streblechenko (MVP)
http://www.dimastr.com/
OutlookSpy - Outlook, CDO
and MAPI Developer Tool

"Ken Slovak - [MVP - Outlook]" wrote in message
...
Dmitry can correct me if I'm wrong but I've never run into a problem with
either Items.Restrict or Items.Find with cached restrictions on the
server. Where I have run into problems is when I've used a Restrict on a
MAPITable and the filter uses something like a date value that changes,
for example testing for something related to today's date. That changes
every day and the restriction would be cached for a default of 8 days
(changeable on the EX server).

I tested for that and ended up with over 10,000 restrictions cached on my
server and even with only 2 active mailboxes it was taking over 10 minutes
to even switch from one item to another in Outlook until I ran code on the
server to kill the cached restrictions.

Also see http://support.microsoft.com/kb/216076

--
Ken Slovak
[MVP - Outlook]
http://www.slovaktech.com
Author: Professional Programming Outlook 2007
Reminder Manager, Extended Reminders, Attachment Options
http://www.slovaktech.com/products.htm


"David Tongeman" wrote in
message ...
I read on Dmitri's Redemption site that Exchange cache's items.restrict
calls, and that using this method too frequently can slow an exchange
server
significantly.

I can't find any reference to this anywhere else... or any advice on when
to
use restrict and when to use filter/find/find next.

I suspect that some code on a customers site (that I didn't write) is
using
items.restrict as part of a search process which is used regularly on a
large
(15000+ ) public contact folder - which in turn maybe slowing the system.

Does anyone have any comments on rules of thumb for using items.restrict
so
as not to 'bring a server to its knees' (in Dmitri's words)
--
Business Solutions using Microsoft Outlook
www.davton.com