Unanswered: log blowing up on huge insert operation
We are doing a one - time insert into a database and the log is growing to 15GB using ALL of the free space on the drive and blowing up.
The insert is being done with a third party ETL tool - reading our datamart (15 million rows) and then doing inserts on one column in select rows our sql server DB. For each insert into the sql server DB, there is a trigger that writes to another table.
Will simple recovery mode help me here?? Bulk-logged??