Prev: HELP: A severe error occurred on the current command.
Next: How to handle @@error=1785
From: Iain Sharp on 24 Mar 2010 13:01
However, many 'disk cleanup' programs (including microsoft's own I
think) will delete or zero out *.log files as these are generally
temporary.

As such, some other program may have 'corrupted' your log file due to
the naming convention.


On Tue, 23 Mar 2010 18:44:46 -0700, "Jeffrey Williams"
<jeff.williams3188(a)verizon.net> wrote:

>SQL Server does not care what the extension on the files are - you can even
>have files with no extensions and SQL Server will be happy.
>
>Jeff
>
>
>"A" <A(a)discussions.microsoft.com> wrote in message
>news:44F73A97-698A-45DF-897A-42588A652E21(a)microsoft.com...
>> Never mind..........It looks like the log file is corrupted. I don't know
>> if
>> the reason is having the .LOG as log file extension but it is corrupted.
>>
>> Running "DBCC CHECKDB" returns
>>
>> "Msg 9001, Level 21, State 1, Line 1
>> The log for database 'MYDB P&T' is not available. Check the event log for
>> related error messages. Resolve any errors and restart the database.
>>
>> Thanks anyway...............
>>
>>
>> "A" wrote:
>>
>>> SQL Server 2008 SP1 2734.
>>>
>>> We have a database that has the data and log file extensions are
>>> different.
>>> Data file has the .DAT extension and log file has the .LOG extension
>>> (Don't
>>> even ask who named them like that).
>>>
>>> Also, the database is in simple mode and set to AUTO CLOSE.
>>>
>>> The backup failed for this database last night thorowing the error "The
>>> log
>>> for database 'MYDB P&T' is not available. Check the event log for related
>>> error messages. Resolve any errors and restart the database.
>>>
>>> (Yes the & in the database name and again don't ask why. You will open
>>> the
>>> can of vorms).
>>>
>>> My question is what would mostly cause the backup failure.
>>>
>>> Having the database in AUTO CLOSE mode (It is backed up at 12:15 AM and
>>> it
>>> is 8:00 AM - 5:00 PM Production)
>>>
>>> or having the different file extension names or neither.
>>>
>>> Thanks for any input.
>>>
>>>
First  |  Prev  | 
Pages: 1 2
Prev: HELP: A severe error occurred on the current command.
Next: How to handle @@error=1785