InstantForum.NET v2.9.0SQLServerCentralhttp://www.sqlservercentral.com/Forums/notifications@sqlservercentral.comSun, 26 May 2013 00:09:15 GMT20http://www.sqlservercentral.com/Forums/Topic672178-29-1.aspxIf your trim job has any significant number of rows in it, it is generally advisable to expire the rows in batches of N rows. One very easy way to implement this is to do: set rowcount @pBatchCntDelete -- Limit number of rows to selectand then run the delete in a loop until no rows are affected.Of course it will perform far better if you can base your deletions on the clustered key. If you aren't using an index and have to delete by table scan, then you would not want to batch the delete as above.Thu, 12 Mar 2009 09:43:26 GMTAdrian Hainshttp://www.sqlservercentral.com/Forums/Topic672178-29-1.aspxComments posted to this topic are about the item [B]<A HREF="/articles/Video/65297/">Removing Audit History - SQL School Video</A>[/B]Mon, 09 Mar 2009 23:56:58 GMTAndy Warren