We are having an ETL process which inserts lots of data into tables. This database is set to Simple Recovery Model and the transaction log is growing a lot. I was thinking that would it help to set this database into Bulk-Logged Recovery Model? We are taking full backups on daily basis. So is there some operations which are not logged in Bulk-Logged Recovery Model compared to Simple Recove
Bulk Logged will not help you in this situation. Your transaction log is growing because you are performing large transactions. In simple mode, the log is truncated after a checkpoint. Check these site: http://www.sql.recoverytoolbox.com/ & download demo Recovery Toolbox for SQL Server. Depending on how you are loading your data, you may need to break it up into smaller chunks. Make sure you are not loading all the data in one large transaction.
Each recovery model has its unique properties which makes distinguishes between them. Simple recovery model doesn’t include the backup of log files if you with Bulk-logged recovery model it uses transaction log files to maintain and stores the whole operations which saves processing time and whole process is knows as Minimal Logging. Bulk-logged recovery model performs high-performance bulk copy operations; minimal log space is used by bulk operations.
I would like to recommend you to use Simple recovery models if some features fails to support Bulk-logged recovery mode