• Seggerman-675349 - Monday, March 12, 2018 3:00 PM

    the log file for a database for a fairly small database is up to 46 Gig - and growing
    it is threatening to fill the virtual server, bringing the web application to a complete halt
    I tried to shrink - no dice
    how do I safely shrink it?
    shouldn't it truncate when a full backup  is taken?

    thanks
    a newbie DBA, not by choice

    Usually when your log blows up like that, check the log reuse value in sys.databases - you just execute:
    select name, log_reuse_wait_desc, recovery_model_desc
    from sys.databases

    If it's in full recovery model and the the log_reuse_wait_desc is log_backup, backup the log.

    Sue