To resolve this problem i need to purge the transaction logs first before performing the operation. This can be done using:
- Perform a Full Backup of the Server which in effect will purge the logs. This can be performed by using Windows Server Backup or another product.
- Enable Circular Logging, dismount/remount the database, then Re-enable Circular Logging.
After the transaction logs have been flushed, this error will no longer occur.
