Transaction log filling up memory space

Last post 11-17-2008 5:44 PM by gw. 2 replies.
Page 1 of 1 (3 items)
Sort Posts: Previous Next
  • 10-17-2008 1:04 PM

    Transaction log filling up memory space

    Has anyone come across this scenario: 

    Store1 has HQ server.  Store2 in Dr Philips has exceeded its hard disk memory.
    The CPU that serves as the server at Store2 appears to be storing transaction logs at:
    C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Data\Store2_Log

    It has maxed out the 74 GB on the CPU.

    recently the CPU popped up this message:

    "The transaction log for database 'mydatabase' is full. To find out why space in the log cannot be reused, see the log_reuse_wait_desc column in sys.databases"


    when that happens the store is unable to enter any new customers and cannot log into the RMS Manager program.

  • 11-07-2008 1:00 PM In reply to

    Re: Transaction log filling up memory space

    BACKUP LOG [Your DataBase] WITH NO_LOGUSE [Your DataBase]

    GO

    DBCC SHRINKFILE ('Logical Log File Name', 20) --20 equals size of the log file after shrink and is in MB

    GO

    I would make sure this is done with a full backup otherwise you will not be able to roll back any transaction after you shrink the logs.  

     

  • 11-17-2008 5:44 PM In reply to

    • gw
    • Top 500 Contributor
    • Joined on 11-17-2008
    • Posts 4

    Re: Transaction log filling up memory space

     You should set up a maintenance plan on your SQL server to keep this log from getting too big.

Page 1 of 1 (3 items)