I have a database that suddenly had a huge transaction log , too big for the free space on disk drive. I know there was a good amount of free space in the database itself. I found that AutoShrink is set to "true" for some reason, and I suspect it ran and created the huge t-log ?
I can see that the last t-log backup ran yesterday at 4:00 pm, then it failed every 15 minutes afterwards due to low disk space until I made room for it , when it created a 7 Gig backup file.
I have the default trace, and my own server side trace, but don't see what caused such a big transaction log backup file shortly after 4:00 pm.
I don't know why autoshrink is on .... I am pretty new at this particular position.