Post reply

Problem with Log File!

  • November 23, 2005 at 10:10 am

    #166068

    I've SQL Server 2000 with a database in Full Recovery mode. Since a view days the system is truncating automatically the log file. I can switch to simple and back to full mode, but nothing changed. What is the reason for this? What can I do?

    Thanks

  • November 23, 2005 at 1:27 pm

    #605552

    the automatic truncation only happens if is either in simple recovery or you have a job that is doing it for you

     


    * Noel

  • November 24, 2005 at 4:30 am

    #605664

    That's correct in 99.9%

    But I've had this in 2 situations in the last years, in which happens that the log file was truncte in full recovery mode!!! That is very surprising!!!

  • November 24, 2005 at 9:56 am

    #605722

    In full recovery mode, the log file is also truncated when you do a log backup - was this the case in those two instances?

    Paul Randal
    CEO, SQLskills.com: Check out SQLskills online training!
    Blog:www.SQLskills.com/blogs/paul Twitter: @PaulRandal
    SQL MVP, Microsoft RD, Contributing Editor of TechNet Magazine
    Author of DBCC CHECKDB/repair (and other Storage Engine) code of SQL Server 2005

  • November 24, 2005 at 12:28 pm

    #605755

    Why switch between Simple and Full? If you have no need for point-in-time recovery, then you should maintain your database in Simple mode. If you do have recovery needs, then it keep it in Full mode and back up your transaction logs on a regular basis.

Viewing 5 posts - 1 through 4 (of 4 total)

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