Our templog.ldf file in the MSSQL$WSUS folder is getting to 10GB. It has
grown about 6GB in the last week. I have tried reading up on shrinking the
file with DBCC SHRINKFILE, but I haven't gotten that to work. I backed up
the templog file last week, then tried the SHRINKFILE this week and it wasn't
recognized as a command.

In another forum someone said I needed to change from Full to Simple
Recovery and I think I have done that from the Command Line.

I have moved all of the downloaded updates to another drive and now the
clients can't find them. I thought I did it as I was supposed to. But
that's a secondary problem until I get the templog reduced. We have less
than 2GB of free space on that drive.

Would really appreciate some help. Thanks.

Jim Allen

Re: WSUS temlog.ldf getting too large by Steve

Steve
Tue May 06 05:01:01 PDT 2008

jallenaz wrote:

>Our templog.ldf file in the MSSQL$WSUS folder is getting to 10GB. It has
>grown about 6GB in the last week. I have tried reading up on shrinking the
>file with DBCC SHRINKFILE, but I haven't gotten that to work. I backed up
>the templog file last week, then tried the SHRINKFILE this week and it
>wasn't
>recognized as a command.
>
>In another forum someone said I needed to change from Full to Simple
>Recovery and I think I have done that from the Command Line.
>
>I have moved all of the downloaded updates to another drive and now the
>clients can't find them. I thought I did it as I was supposed to. But
>that's a secondary problem until I get the templog reduced. We have less
>than 2GB of free space on that drive.

Stop the WSUS services, stop the WSUS SQL instance, delete the tempdb
files and restart.

--
Steve Foster [SBS MVP]
---------------------------------------
MVPs do not work for Microsoft. Please reply only to the newsgroups.