Results 1 to 5 of 5
  1. #1
    Join Date
    May 2003
    Posts
    1

    Unanswered: Unable to truncate log file 11GB

    OS - NT server 4.00., MSSQL 6.5 with SP5a

    Even after I stop the MSSQL server 6.5 service and restart the server many time, I still can't truncate the log. "dump transaction db_name with no_log" has no effect and the log file is increasing at very fast rate during the production run time.

    I have stopped all the schedule task, but the the log file remain 11GB.
    DBCC Opentran does not show any open transcation at all.

    Suspect caused by replication as the susbscription db full few days ago
    Have done uninstall publishing, removed the distribution database manually.

    Any suggestion are welcome
    appreciate your help

    Thank you

  2. #2
    Join Date
    May 2002
    Posts
    4

    Re: Unable to truncate log file 11GB

    Originally posted by francisSg
    OS - NT server 4.00., MSSQL 6.5 with SP5a

    Even after I stop the MSSQL server 6.5 service and restart the server many time, I still can't truncate the log. "dump transaction db_name with no_log" has no effect and the log file is increasing at very fast rate during the production run time.

    I have stopped all the schedule task, but the the log file remain 11GB.
    DBCC Opentran does not show any open transcation at all.

    Suspect caused by replication as the susbscription db full few days ago
    Have done uninstall publishing, removed the distribution database manually.

    Any suggestion are welcome
    appreciate your help

    Thank you

  3. #3
    Join Date
    May 2002
    Posts
    4

    Re: Unable to truncate log file 11GB

    take a full back and isse truncate command

    use dbcc updateusage(), hope this will help. to clear the log.

  4. #4
    Join Date
    Jan 2003
    Location
    Massachusetts
    Posts
    5,799
    Provided Answers: 11
    I used to have the answer, but it appears I have since cleaned out my files. I think this was the article that helped me:

    http://support.microsoft.com/default...b;en-us;170481

  5. #5
    Join Date
    Feb 2003
    Posts
    109

    wrong syntax

    yeah, i dont think that you are using the right syntax-- i know that the NO_LOG clause will specifcally not do anything to the log file--

    so why dont you try the TRUNCATE_ONLY clause instead?

    BACKUP LOG databasename WITH TRUNCATE_ONLY
    Access 2002 ADP Rocks my World

    Long live SQL Server and 64bit Windows!!!

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •