Background:
SQL 2005
Database is Full recovery model
Problem:
There is no disk space in order to do any sort of backup and the transaction log for a particular database is huge and needs to be shrunk. I do understand that regular transaction log backups should be happening in order to truncate the logs however I just assumed ownership of this server and discovered this scenario. Bottom line is that I need to manually shrink the log file but am unable to do a backup and since I thought that since the log is truncated following a full db backup, that a DBCC SHRINKFILE will not help me.
Thanks in advance.
Glenn
SQL 2005
Database is Full recovery model
Problem:
There is no disk space in order to do any sort of backup and the transaction log for a particular database is huge and needs to be shrunk. I do understand that regular transaction log backups should be happening in order to truncate the logs however I just assumed ownership of this server and discovered this scenario. Bottom line is that I need to manually shrink the log file but am unable to do a backup and since I thought that since the log is truncated following a full db backup, that a DBCC SHRINKFILE will not help me.
Thanks in advance.
Glenn