logsize

  • For everyone else's benefit: the first 8K page of the physical log file contains header information - no log records.

    The header is just internal stuff to manage the log proper.

    Paul

  • using dbcc updateusage helps ? it shouldn't. there were some problems with counting allocations but on sql server 2000! 2005/2008 are running good. the only way it can be a problem is during migrating from 2000 -> to 2005/2008 without dbcc updateusage. but still it shouldn't affect on you log file.

  • Marcin Gol [SQL Server MVP] (9/6/2009)


    using dbcc updateusage helps ? it shouldn't. there were some problems with counting allocations but on sql server 2000! 2005/2008 are running good. the only way it can be a problem is during migrating from 2000 -> to 2005/2008 without dbcc updateusage. but still it shouldn't affect on you log file.

    DBCC UPDATEUSAGE never affect(ed) log files - with the possible exception of version 6.5 and earlier which kept the log in syslogs.

    I'm going to go right out on a limb here and assume that the version in question is later than 6.5 🙂

    Gail and I both made this point previously...?

  • yes dbcc updateusage is not workedout.

    my issue is stil not resolved.

    sql version is 8.0

    how to findout actual logspaceused.

  • charipg (9/7/2009)


    yes dbcc updateusage is not workedout.

    my issue is stil not resolved.

    sql version is 8.0

    how to findout actual logspaceused.

    The counter you are using seems to be the right one - it's just unfortunate that the % used figure can go over 100% as explained.

    You would probably want to take some corrective action before it reaches anything like 100% however.

    It might help if you tell us more about what you are doing, and why.

    (Also note that there is a whole separate area for SQL Server 2000 - this is a 2005 forum :))

Viewing 5 posts - 16 through 19 (of 19 total)

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