Autoshrink disabled but still running?

Hi!
I've disabled auto shrink but it still seems to be in
effect. I try to expand my .log file in a database to 300
MB and it works great but a few hours later the log is
40MB again.
Auto Shrink is _not_ enabled and there is no job
automatically shrinking the db.
Any ideas?
I use sql 7 on nt 4.Perhaps there's some old shrink instruction lurking in there which SQL
Server tries to handle asynchronously?
--
Tibor Karaszi, SQL Server MVP
Archive at:
http://groups.google.com/groups?oi=djq&as_ugroup=microsoft.public.sqlserver
"Henry Fischer" <anonymous@.discussions.microsoft.com> wrote in message
news:f23101c3bd9a$033a6e00$a601280a@.phx.gbl...
> Hi!
> I've disabled auto shrink but it still seems to be in
> effect. I try to expand my .log file in a database to 300
> MB and it works great but a few hours later the log is
> 40MB again.
> Auto Shrink is _not_ enabled and there is no job
> automatically shrinking the db.
> Any ideas?
> I use sql 7 on nt 4.|||Yes, I suspect there is. The database was marked for
autoshrink when it was restored a few weeks ago. I
disabled the autoshrink but it still shrinks, but only the
logfile though...
Any ideas on how to get rid of this "feature"?
>--Original Message--
>Perhaps there's some old shrink instruction lurking in
there which SQL
>Server tries to handle asynchronously?
>--
>Tibor Karaszi, SQL Server MVP
>Archive at:
>http://groups.google.com/groups?
oi=djq&as_ugroup=microsoft.public.sqlserver
>
>"Henry Fischer" <anonymous@.discussions.microsoft.com>
wrote in message
>news:f23101c3bd9a$033a6e00$a601280a@.phx.gbl...
>> Hi!
>> I've disabled auto shrink but it still seems to be in
>> effect. I try to expand my .log file in a database to
300
>> MB and it works great but a few hours later the log is
>> 40MB again.
>> Auto Shrink is _not_ enabled and there is no job
>> automatically shrinking the db.
>> Any ideas?
>> I use sql 7 on nt 4.
>
>.
>|||> Any ideas on how to get rid of this "feature"?
Perhaps let it shrink once to the level it is aiming for (the autoshrink is
the same as specifying 25% in the DBCC SHRINKDATABASE command)?
Also, I'm pretty certain that there's a KB on this particular situation, it
might be worth spending some time to find that article.
--
Tibor Karaszi, SQL Server MVP
Archive at:
http://groups.google.com/groups?oi=djq&as_ugroup=microsoft.public.sqlserver
"Hentry Fischer" <anonymous@.discussions.microsoft.com> wrote in message
news:0a1301c3be23$855db6b0$a101280a@.phx.gbl...
> Yes, I suspect there is. The database was marked for
> autoshrink when it was restored a few weeks ago. I
> disabled the autoshrink but it still shrinks, but only the
> logfile though...
> Any ideas on how to get rid of this "feature"?
> >--Original Message--
> >Perhaps there's some old shrink instruction lurking in
> there which SQL
> >Server tries to handle asynchronously?
> >
> >--
> >Tibor Karaszi, SQL Server MVP
> >Archive at:
> >http://groups.google.com/groups?
> oi=djq&as_ugroup=microsoft.public.sqlserver
> >
> >
> >"Henry Fischer" <anonymous@.discussions.microsoft.com>
> wrote in message
> >news:f23101c3bd9a$033a6e00$a601280a@.phx.gbl...
> >> Hi!
> >>
> >> I've disabled auto shrink but it still seems to be in
> >> effect. I try to expand my .log file in a database to
> 300
> >> MB and it works great but a few hours later the log is
> >> 40MB again.
> >> Auto Shrink is _not_ enabled and there is no job
> >> automatically shrinking the db.
> >> Any ideas?
> >> I use sql 7 on nt 4.
> >
> >
> >.
> >|||Thanks Tibor,
I don't know if this really works but atleast it has so
far, which is goot.
I let it shrink down and then expanded the log to 500 MB.
Immidiately afterwards I shrunk it with DBCC SHRINKFILE
down to 300.
Now the log is actually 320 MB, but I can live with
that. :)
>--Original Message--
>> Any ideas on how to get rid of this "feature"?
>Perhaps let it shrink once to the level it is aiming for
(the autoshrink is
>the same as specifying 25% in the DBCC SHRINKDATABASE
command)?
>Also, I'm pretty certain that there's a KB on this
particular situation, it
>might be worth spending some time to find that article.
>--
>Tibor Karaszi, SQL Server MVP
>Archive at:
>http://groups.google.com/groups?
oi=djq&as_ugroup=microsoft.public.sqlserver
>
>"Hentry Fischer" <anonymous@.discussions.microsoft.com>
wrote in message
>news:0a1301c3be23$855db6b0$a101280a@.phx.gbl...
>> Yes, I suspect there is. The database was marked for
>> autoshrink when it was restored a few weeks ago. I
>> disabled the autoshrink but it still shrinks, but only
the
>> logfile though...
>> Any ideas on how to get rid of this "feature"?
>> >--Original Message--
>> >Perhaps there's some old shrink instruction lurking in
>> there which SQL
>> >Server tries to handle asynchronously?
>> >
>> >--
>> >Tibor Karaszi, SQL Server MVP
>> >Archive at:
>> >http://groups.google.com/groups?
>> oi=djq&as_ugroup=microsoft.public.sqlserver
>> >
>> >
>> >"Henry Fischer" <anonymous@.discussions.microsoft.com>
>> wrote in message
>> >news:f23101c3bd9a$033a6e00$a601280a@.phx.gbl...
>> >> Hi!
>> >>
>> >> I've disabled auto shrink but it still seems to be in
>> >> effect. I try to expand my .log file in a database to
>> 300
>> >> MB and it works great but a few hours later the log
is
>> >> 40MB again.
>> >> Auto Shrink is _not_ enabled and there is no job
>> >> automatically shrinking the db.
>> >> Any ideas?
>> >> I use sql 7 on nt 4.
>> >
>> >
>> >.
>> >
>
>.
>