Why is My SQL Server Transaction Log Growing or Running out of Space?
The transaction log in one of my client's databases is 16GB, when the database itself is only 2MB. I have begun backups of the transaction log and they occur every half an hour.
I have attempted to run DBCC SHRINKFILE (Log,size) but it says all virtual pages are in use.
Does this mean there is an uncommited transaction or something? The file has been this big for a while now. Am I able to somehow truncate the log?