Grant Fritchey (2/20/2014)
No way in the world, at all, to avoid the log, so best practice is to find ways to deal with it. No other choice there. If you don't need recover to a point in time, you might try bulk-logged. It can reduce log size for some operations, but, it will require log backups, unlike Simple.
Like Grant said, there is no way to avoid a hit to your log. By reducing the number of records per batch you could lessen that impact and improve overall performance.
Jason...AKA CirqueDeSQLeil
_______________________________________________
I have given a name to my pain...MCM SQL Server, MVP
SQL RNNR
Posting Performance Based Questions - Gail Shaw[/url]
Learn Extended Events