Hello experts!
Our databases are in SIMPLE recovery mode and most of our transaction are set to perform BULK load using SSIS, even then we are hitting abnormal transaction log sizes on few databases. I see this is happening when there is overlap of our DB backup job with ETL jobs - I guess SQL server tries to record the transactions of ETL jobs while DB backup is being done.. to help recovery etc? I think the Bulk action is not working during the DB backup, hence the trn log is bulging. Any tips to minimize log growth and minimize the impact of overlap of workloads on each other? We have tight schedules /time window between DB Maint & ETL jobs.
Platform:SQ 2008 R2 Enterprise
Let me know if you need more information for an answer.
Thanks in Advance!
Mahesh
Mahesh
Our databases are in SIMPLE recovery mode and most of our transaction are set to perform BULK load using SSIS, even then we are hitting abnormal transaction log sizes on few databases. I see this is happening when there is overlap of our DB backup job with ETL jobs - I guess SQL server tries to record the transactions of ETL jobs while DB backup is being done.. to help recovery etc? I think the Bulk action is not working during the DB backup, hence the trn log is bulging. Any tips to minimize log growth and minimize the impact of overlap of workloads on each other? We have tight schedules /time window between DB Maint & ETL jobs.
Platform:SQ 2008 R2 Enterprise
Let me know if you need more information for an answer.
Thanks in Advance!
Mahesh
Mahesh