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.
:confused: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|||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".|||What syntax did you use to increase it?|||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.

:confused:|||What syntax did you use to increase the transaction log?|||I'm using Enterprise Manager.|||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')|||I know that you can't duplicate my experience, that's why is a problem. but thats happen sometimes in SQL 7.0.