Just read about another cause of SQL Server 2005 Transaction Log bloating to add to my previous list.
Suspending a DB Mirroring session will prevent the primary DB from truncating its log file after a checkpoint as the log entries will be queued to be sent to the mirror DB. When the mirroring session is resumed [...]
A SQL Server 2005 High Safety DB Mirroring session synchronously transfers transactions from the primary DB to the mirroring DB and then with the help of a witness server supports automatic fail over from the primary to the mirror is the primary becomes unavailable. All the primary, mirror and witness nodes all keep an eye [...]
A little while ago one of my work colleges asked me why a transaction log could suddenly grow in size on SQL Server 2005 . I went with the stock standard “long running transaction” answer; then a few days latter read about another reason. And have just read about another one.
So here is my in [...]
I decided to take a look at setting up a SQL Server 2005 Database Mirroring session and once again got carried away with security and ownership. In the past other than maintaining ownership chains I’ve purposely ignored these areas, but in SQL 2005 it seems a lot easier to do the right thing.
The mirroring session [...]