Post reply

My Log is Full and dbcc shrinkfile failed......

  • August 17, 2005 at 3:48 pm

    #87308

    Friend i have the next problem

    My Log is full and i attempted to shrink with a dbcc

    dbcc shrinkfile(vanilla_log,100)

    Cannot shrink log file 2 (Vanilla_Log) because all logical log files are in use

    well , when i saw this message i stopped the sql service and started it again but when i run the dbcc the message appears again why??

    thankss for read me.......

    mm another question how can i do an update but it will not go to the log file??

    Thankss

  • August 17, 2005 at 4:57 pm

    #582894

    Is your log full because you are out of disk space, or because your log file is not set to autogrow?

    If it is not set to autogrow, then just increase the size of the log by a meg or 2, then issue your shrink stuff.

    If the disk is full, your going to have to figure some way to free up some space first.

    Move a not/little used db off temporarily, Delete unused backups etc.

    Then Do your shrink.

     

  • August 18, 2005 at 3:10 am

    #582940

    Is you database in full recovery mode? If so, backup the log. That will truncate the log and allow you to shrink it.

    If the database is in simple recovery mode, issue a checkpoint and SQL will automatically truncate the log files

    Note that truncating the log just affects the virtual log files and doesn't change the size of file on disk.

    Read the entries in Books Online about backup and log architecture

    There is no way to do an update that isn't logged.

    Gail Shaw
    Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
    SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

    We walk in the dark places no others will enter
    We stand on the bridge and no one may pass

Viewing 3 posts - 1 through 2 (of 2 total)

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