This from the MSDN Library Help:

"Rushmore optimizes a query created with DELETE ... FOR if lExpression1 is an optimizable expression and the table is indexed on DELETED( ). For best performance, use an optimizable expression in the FOR clause. "

Make sure your Delete query is Rushmore-enabled, should help...

HTH,

-Irv.


>Hi,
>My primary is a composite key , combine by appid + grpid +itemcode.
>And the key fields i set in update criteria is appid, grpid and itemcode.
>
>The application is in the same machine with the database. Does 10secs for 2,000 records is acceptable?? SOmtime it can take until 20-30 secs... :( AGain, What happened if other client machine do the same thing across network?? Will it take longer time?? Then sure my client will complaint about it.. :(
>
>I used to try delete 2000 recrods for table, but it just take about 1 seconds.. how come the time taken by view is too different? Any workaround?
>
>Thank you