Has anyone experienced this before? I don’t think (but I’m not sure) that any heavy transactions were happening. Do you know why the log file might still be in use?
If any transactions were happening, the log file is in use. Any at all, doesn’t have to be heavy. The only way that I know to get the log file to stop is to take the database offline.
Thanks, Denster. I wonder why SQL Server allows that?
I guess I don’t know what you mean… The transaction log is the single most important mechanism in SQL Server to manage data integrity, and it is supposed to be in use at all times. When are you expecting SQL Server to NOT use it?