|
|
Posted by brian.j.parker on 08/22/06 15:55
Thank you very much for your help and advice, Tom.
Tom Moreau wrote:
> Hmm. If possible, do a full backup of master. Also stop and start SQL
> Server.
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).
Sorry to raise a ruckus about what turned out to be an easy problem,
but I'd wished not to reboot since it's an important (what isn't?)
application and I'd felt a little paranoid I wouldn't get the server
started again.
Of course it's now a renewed priority to see if we can move the
application on SQL Server 2000! That should be much easier to manage.
Cheers,
Brian
Navigation:
[Reply to this message]
|