Re: Replacing Default Instance
From: Hari (hari_prasad_k_at_hotmail.com)
Date: 03/25/04
- Next message: Vincent Jones: "Simple Cursor"
- Previous message: Kevin: "Re: AWE SQL Performance Problem"
- In reply to: Jim: "Replacing Default Instance"
- Messages sorted by: [ date ] [ thread ]
Date: Thu, 25 Mar 2004 10:09:12 +0530
Hi ,
Add on to Tibor, Instead of moving the user databases to new named instance,
why dont you take a backup of MSDB database from the new
named instance and restore it in Default instance.
This is under the assumption only your MSDB has got issues. This case all
your Logins/Backup devices and configuration info in Master
database can be preserved.
Have a look into the below article (Just read the MSDB part only)
http://support.microsoft.com/default.aspx?scid=kb;EN-US;Q224071
If you have problems in detach/attach, try with backup and restore strategy.
Thanks
Hari
MCDBA
"Jim" <jromano@phs-us.com> wrote in message
news:e1e1a687.0403241251.1c364809@posting.google.com...
> Our default instance of SQL 2000 is corrupted. The msdb database
> tables do not have several columns required by the SQL Agent. The
> corruption apparently occurred while running the SQL Wizard to convert
> our 6.5 version to 2000. TO rectify the problem we successfully
> installed a new instance of SQL which gave us a clean set of msdb and
> master tables. We then copied our user databases over to the new
> instance. My question is this: can we now make that new instance the
> default instance? How can we do this? Thanks.
- Next message: Vincent Jones: "Simple Cursor"
- Previous message: Kevin: "Re: AWE SQL Performance Problem"
- In reply to: Jim: "Replacing Default Instance"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
