none
Bulk-Logging woes

    Question

  • I'm currently moving some large tables (>10GB, >10Mio rows) from one database to another database. Both databases are running in the same SQL Server (9.0.3068) instance. The destination databases logging is set to bulk-logging. Copying the first three tables - INSERT INTO DestDB.Schema.Table ( Columns ) SELECT Columns FROM SourceDB.Schema.Table worked like charme. Copied ~50GB with the log grown to a maximum size of ~50GB. Now I'm trying the same, but the log is exploding. Thus growing to maximum fixed size of 132GB, initial log size when starting the transaction was 2GB. And, yeah, automatic rollback.

    I have no clue what's going on. Any hint is welcome..

    Friday, April 27, 2012 1:04 PM

Answers

All replies