"Tom Roth" <TomRoth@discussions.microsoft.com> wrote in message
news:5AA9277E-1B22-4AA1-B1F0-BD099956EAE3@microsoft.com...
>I have 28.6GB of space available on the log drive. I found a Q Article
> (909369). I wonder if this is my problem. I'm running SQL Server 2000
> Standard SP3a.
> --
> Tom
>
>
> "Arnie Rowland" wrote:
>
>> How much free space is available on the disk?
>>
>> --
>> Arnie Rowland, Ph.D.
>> Westwood Consulting, Inc
>>
>> Most good judgment comes from experience.
>> Most experience comes from bad judgment.
>> - Anonymous
>>
>>
>> "Tom Roth" <TomRoth@discussions.microsoft.com> wrote in message
>> news:58EE27BE-DA0A-4867-91C8-1E26EA1F7CE0@microsoft.com...
>> >I also wwanted to mention that the transaction log is set to
>> >automatically
>> > grow. The file growth is "10%". The maximum file size is
>> > "Unrestricted
>> > file
>> > growth".
>> > --
>> > Tom
>> >
>> >
>> > "Tom Roth" wrote:
>> >
>> >> I'm running SQLServer 2000 Standard. I have a database that is set
>> >> for
>> >> Recovery Mode = Simple. The dboption "trunc. log on ckpt." is set to
>> >> TRUE.
>> >> I have also issued the truncate log command "BACKUP LOG DB_Name WITH
>> >> TRUNCATE_ONLY". I have penty of available disk space.
>> >>
>> >> I still get the following error messages:
>> >> DESCRIPTION: Error: 9002, Severity: 17, State: 6
>> >> The log file for database 'DB_Name' is full. Back up the transaction
>> >> log
>> >> for
>> >> the database to free up some log space.
>> >>
>> >> Why do I keep getting this error message? Does the dboption "trunc.
>> >> log
>> >> on
>> >> ckpt" not work?
>> >> --
>> >> Tom
>>
>>
>>