|
|
Posted by Erland Sommarskog on 08/22/06 22:08
(brian.j.parker@gmail.com) writes:
> I got the same error trying to do a full backup of master. With some
> reluctance, I rebooted the server, and... the problem magically cleared
> up. I could truncate the log, expand the devices and the database and
> log, and go on from there (get a backup, etc).
Great to hear that it worked out.
BACKUP, DISK INIT etc must all fail in this situation. BACKUP will
always fail, since it wants to write to the log. DISK INIT could
work for a user database, but DISK INIT needs to write to a table
in guess which database.
I would expect NO_LOG to work, but may NO_LOG writes to master.
Oh, well, 6.5, itwasn't too bad in its days, but it is dated now.
--
Erland Sommarskog, SQL Server MVP, esquel@sommarskog.se
Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/prodtechnol/sql/2005/downloads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodinfo/previousversions/books.mspx
Navigation:
[Reply to this message]
|