|
|
Posted by Tom Moreau on 08/22/06 16:05
Well, MS keeps support for n - 1 releases. Considering that this is n - 3,
it would be a good idea. Indeed, I don't believe there is now a direct
upgrade path from 6.5 to 2005. You'll likely have to upgrade via either of
the following paths:
1) 6.5 -> 7.0; 7.0 -> 2005
2) 6.5 -> 2000; 2000 -> 2005
If you have 2000 in house, you can upgrade that part now.
If it's an "important" app, it's also important to keep the RDBMS current.
--
Tom
----------------------------------------------------
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
SQL Server MVP
Toronto, ON Canada
..
<brian.j.parker@gmail.com> wrote in message
news:1156262141.064510.218430@i42g2000cwa.googlegroups.com...
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]
|