Skip to main content

Log File Full–Availability Group Database

I run into an interesting issue with an Availability Group database recently. I was running a data load against a database in an Always On Availability group database in SQL Server 2012.  The load was SSIS package migrating data from staging database when the package fell over with the following error
“The transaction log for database DBName is full due to 'AVAILABILITY_REPLICA'”
This was interesting error. Initially I thought my log had filled up all the space on the disk but after examining the drive on the server, looking at the free space in the log and running a

 SELECT * FROM sys.databases 

I found that this was not the case.
My query returned the following in the log_reuse_wait_desc
The SQL Server documentation gives the following explanation of this log_reuse_wait_desc
“9 = An AlwaysOn Availability Groups secondary replica is applying transaction log records of this database to a corresponding secondary database. “
For more information see
My AlwaysOn setup had involved three instances, one primary two secondary’s one setup with synchronous commit mode and automatic failover and the other  asynchronous with manual failover. The synchronous commit mode with  automatic failover had fallen out of sync and was marked as ‘Not Synchronising.’ The drive holding the log of this secondary database still had plenty space, the log itself still had plenty of space, there was no need for it to grow
This was  pain for me as the database was going to end up quite large and I didn’t want to re-initialise availability group therefore I didn’t want to remove the database from the availability to run the load  and then re-initialize after it had completed. Instead I changed the   secondary replica using synchronous commit mode to use asynchronous commit with manual failover, this meant the primary didn’t have to wait for the secondary replica to harden its log before continuing,  hopefully so the load would complete without further error. It wouldn’t have to wait for the transactions to harden against the secondary. When the load had finished and the secondary had caught up synchronizing I was able to switch back to synchronous commit and configure automatic failover.

For the latest SQL Server 2012 Training visit

USA and Canada

UK and Europe


Popular posts from this blog

SQL Server 2012 and Virtual Service Accounts

This post is written by David Postlethwaite
If you are using SQL Server 2012 you will probably have noticed that the default account for the SQL services has changed from that used in previous versions. With SQL 2005 and 2008 the default account for SQL service and SQL Agent service was “NT Authority\System”. This is one the built in accounts on a Windows machine, managed by the machine and selectable from a dedicated dropdown list

The Network Service account was introduced in Windows 2003 as an alternative to using the LocalSystem account, which has full local system privileges on the local machine, a major security concern.
The Network Service has limited local privileges easing these security concerns but when many services on a machine use the Network Service account it becomes harder to track which service is actually accessing resources and performing actions, because all the services are using the one Network Service account.
Also, this account, by default, has sysadmin per…

Always Encrypted

By David Postlethwaite

Always Encrypted is new features in SQL Server 2016 and it is also available in Azure SQL Database. Here you can encrypt columns in a table with a master key and a certificate so that they will appear as encrypted strings to those who don’t have the required certificate installed on their pc.
Once the certificate is installed on the computer then the unencrypted data can then be seen as normal.

The data passes from database to your application as the encrypted value, only the application with the correct certificate can unencrypt the data so it is secure across the wire. This will go some way to resolving the concern of people worried about putting their sensitive data on a shared server in the cloud such as Microsoft Azure and accessing the data across the Internet.

At the time of writing Always Encrypted is only supported with ADO.NET 4.6, JDBC 6.0 and ODBC 13.1 but expect other driver to become available.

The calling application (including SSMS) must also hav…

How to Setup Kerberos Correctly

David was in Copenhagen this weekend delivering his Kerberos talk Taming the Beast: Kerberos for the SQL DBA to SQL Saturday Denmark. I have had a quick chat with him via email since he got back and he said he had a great time. The event was very well attended with 280+ attendees and his talk was well attended.

I think David is planning submitting a few sessions to SQL Saturday events in Europe in the next few months so look out for him there and we'll keep you posted as to his whereabouts when schedules get finalised later in the year.

David has pre-recorded his Kerberos talk. You can watch on you tube and I have also embedded it in this post if you want to see what his kerberos talk  covers...

If we can help you with a SQL Sever problem visit our SQL Server Consulting page or contact us