Post reply

Huge msdb - not backup logs

  • August 30, 2006 at 10:47 pm

    #657724

    OK ... now we're getting somewhere 🙂  I used sp_spaceused to check every single table individually and finally found the REAL culprits (it was always going to be one of the last ones :-|) ...sysdtspackagelog (612mb) and sysdtssteplog (3.2gb).  So I did a bit more reading (don't want you guys to do all the work :-&gt and found that this is turned on through the dts designer and there is a handy "delete logs" button.  I'm a bit nervous clicking it though - are these logs just used for debugging, or could deleting them have wider implications?

    Thanks again

    Tom.

  • August 31, 2006 at 1:06 am

    #657734

    Glad to hear that your problem is solved. Glad that I learned a new command (DBCC UPDATEUSAGE ('msdb') WITH COUNT_ROWS) Funny to hear that the problem table is another than we stucked

    Cheers

    Zubeyir

  • August 31, 2006 at 1:26 am

    #657737

    Yeah thanks very much for your help ... I've learnt plenty too.  I've gone ahead and deleted the logs so I hope the next post here is not "whatever you do, don't delete those logs" ... It took about 3 hours to complete.  I have just shrunk the database which is now 150mb

    Thanks again for your help ... if you're ever in Brisbane, Australia I'll buy you a beer or three

    Tom

Viewing 3 posts - 16 through 17 (of 17 total)

You must be logged in to reply to this topic. Login to reply