• Jeff Moden (2/11/2013)


    As a sidebar, I'm thinking there's something seriously wrong with the database. You're talking about a very small database using almost a quarter of a Terabyte! When you finally get this bugger loaded, look at the recovery model. I'd bet credits to Navy beans that it's in the FULL or Bulk Logged recovery model and that no one has taken a transactional log backup for MONTHS.

    I had a similar problem recently - the culprit was an autogrow setting that been set to 1,000... percent. :w00t: