title: Best practice for archiving a huge table of over 1,000,000,000 rows
body: <p>I'm using SQL Server 2005. There is an audit trail table, containing over 1,000,000,000 rows. I'm planning to archive this table. When I make a simple select with <code>nolock</code>, I can still find blocking (probably IO blocking with other process?). So are there any best practice for this kind of situation?</p>