We have a 7 TB DW environment that we're using High Availability on. Almost all of the data is bulk loaded nightly/ weekly. We've been running this in Sync-commit mode, but lately the Transaction Log in our Primary DB has grown to > 1/2 TB waiting on the bulk loads to be committed on the Secondary server.
Would this scenario be mitigated if we were using ASync-commit mode? Would the TLog, no longer waiting for the Secondary to synchronize, be able to shrink as it normally would (of course considering TLog backups, etc.)?
TIA, ChrisRDBA