The 25K is in one table <g>.

I have experienced firsthand the problem with transaction logs while working on an ecommerce project in SQL 6. Fortunately, I wasn't the DBA; it was pretty ugly. But I thought one of the "Features" of later versions is that the database could adjust dynamically. It seems rather odd that with terrabytes of empty disk space something like this could derail an entire applcation.