We have a database in SQL Server 2008 for which the
Recovery model is set to
Periodically, we run a big update on a big table (15 million rows to update). To accomplish this, we run a Stored Procedure which takes 2 hours+ to run. When the Stored Procedure finishes to run, the log file grew up to 37GB which is kind of strange since the recovery model is Simple and that we don't even explicitly begin a transaction in the Stored Procedure (we make a full backup of the DB prior to update for safety)
Also, when we shrink the log file, it goes back to 1MB
Is it possible to just prevent the log file to grow up 37GB ?