Results 1 to 9 of 9
  1. #1
    Join Date
    Jul 2002
    Location
    Lima - Perú
    Posts
    30

    Unhappy Unanswered: Autoshrink Log ???

    Hello: I have a Database with a file log of 75 Mb which I have increased to 150 MB, but when i execute a "backup log with no_log" the size is returned to the initial size, I must mention that autoshrink is disabled.


  2. #2
    Join Date
    Oct 2001
    Location
    Naples, FL
    Posts
    273
    with no_log or truncate_only they will only remove the checkpointed transactions in the log, it will not reduce the footprint (file size). If you need to shrink the file use dbcc shrinkfile. But be careful in this as if your log regularly has to grow, you are hurting your performance by constantly shrinking it.

    HTH
    ---------------
    Ray Higdon MCSE, MCDBA, CCNA

  3. #3
    Join Date
    Jul 2002
    Location
    Lima - Perú
    Posts
    30
    Hi :

    I know that, but my problem is that i dont want to "shrink" the file but when i execute "Backup log" the file log is "shrinked".

  4. #4
    Join Date
    Oct 2001
    Location
    Naples, FL
    Posts
    273
    What syntax did you use to increase it?
    ---------------
    Ray Higdon MCSE, MCDBA, CCNA

  5. #5
    Join Date
    Jul 2002
    Location
    Lima - Perú
    Posts
    30
    I'm executing "Backup Log NAME with no_log".

    Results : Truncate the log and my file log that i increased to 150 Mb is decresed to the initial size of 75 Mb.


  6. #6
    Join Date
    Oct 2001
    Location
    Naples, FL
    Posts
    273
    What syntax did you use to increase the transaction log?
    ---------------
    Ray Higdon MCSE, MCDBA, CCNA

  7. #7
    Join Date
    Jul 2002
    Location
    Lima - Perú
    Posts
    30
    I'm using Enterprise Manager.

  8. #8
    Join Date
    Oct 2001
    Location
    Naples, FL
    Posts
    273
    I ran this multiple times and with simple and full recovery mode and can not duplicate what you are experiencing. If you can do what you are trying to do in SQL, plese post it, if you do not, run profiler while you make your changes in EM. See if this helps at all:

    create database testing
    use testing
    dbcc sqlperf('logspace')

    alter database testing
    modify file
    (NAME = testing_log,
    SIZE = 20MB)


    dbcc sqlperf ('logspace')

    backup log testing with no_log

    dbcc sqlperf ('logspace')
    ---------------
    Ray Higdon MCSE, MCDBA, CCNA

  9. #9
    Join Date
    Jul 2002
    Location
    Lima - Perú
    Posts
    30
    I know that you can't duplicate my experience, that's why is a problem. but thats happen sometimes in SQL 7.0.

Posting Permissions

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