Don't know how this happened, the database just fell into my lap, and I've found that the allocated file for the transaction log has recently grown to about 13 gigs - and it was about 8 last week. Actual size after truncation (of a copy) shows one meg is quite enough to hold what it should.

Now whatever I try with the original database, it won't let me shrink it - yes, it behaves like it's shrunk, but when I come back to look at it, it's 13G again.

I've found an option to delete the log - would adding a second log and then deleting the old one do any damage or should I just go ahead and do it? Or is it that I don't have the rights? If so, it should have given me any sort of error, instead of pretending to have done what I told it to...

Or, are there other options? This has just gone way out of proportion.