Eralper (11/22/2010)
Thanks Jeff,I checked the BOL and I found :
The amount of logging for SELECT...INTO depends on the recovery model in effect for the database. Under the simple recovery model or bulk-logged recovery model, bulk operations are minimally logged. With minimal logging, using the SELECT… INTO statement can be more efficient than creating a table and then populating the table with an INSERT statement.
So I think populating a new table and then truncating the other might be more efficient when log size is considered.
I agree. Just to be clear for folks that may think of doing it, don't ever shift from FULL recovery to SIMPLE recovery for the sake of archiving data because it will break the log chain for backups. It's ok to shift from FULL recovery to the BULK-LOGGED recovery, though.
--Jeff Moden
Change is inevitable... Change for the better is not.