rebuild sql services; making an instance the default

When installing Dotnet, wound up with TWO Named SQL Server instances for use
by the sample apps. When trying to uninstall the extraneous one, I screwed
up and selected the one I wanted to keep. Canceled the uninstall. Server is
still there. Can start up manually and connect to it. However, the
service(s) got whacked before I canceled out.
Two questions.
1) Can the services be rebuilt by hand?
2) If I can get the single (named) instance working, can I turn it into the
default instance? My sole purpose was to be able to test the DotNet sample
apps, all of which are hardwired to connect to local. It's becoming quite a
nuisance to fix them all.
Any suggestions would be greatly appreciated. TIADo you have the database files still there? I.e., the mdf, ldf and possibly
ndf. If so, just use sp_attach_db to attach the database files to get each
database into your desired instance. You can not rename an instance, so you
need to install a named instance.
--
Tibor Karaszi, SQL Server MVP
Archive at:
http://groups.google.com/groups?oi=djq&as_ugroup=microsoft.public.sqlserver
"Ron Foster" <rlfoster1@.cox.net> wrote in message
news:%23nvQjkbvDHA.2316@.TK2MSFTNGP10.phx.gbl...
> When installing Dotnet, wound up with TWO Named SQL Server instances for
use
> by the sample apps. When trying to uninstall the extraneous one, I screwed
> up and selected the one I wanted to keep. Canceled the uninstall. Server
is
> still there. Can start up manually and connect to it. However, the
> service(s) got whacked before I canceled out.
>
> Two questions.
> 1) Can the services be rebuilt by hand?
> 2) If I can get the single (named) instance working, can I turn it into
the
> default instance? My sole purpose was to be able to test the DotNet sample
> apps, all of which are hardwired to connect to local. It's becoming quite
a
> nuisance to fix them all.
>
> Any suggestions would be greatly appreciated. TIA
>|||Thanks for the response.
Yes, I still have the entire named instance available, and can connect to
it.
What I lost was the services to start/stop/pause it. Currently am having to
start it manually in a cmd box.
"Tibor Karaszi" <tibor.please_reply_to_public_forum.karaszi@.cornerstone.se>
wrote in message news:OVXpctbvDHA.2000@.TK2MSFTNGP11.phx.gbl...
> Do you have the database files still there? I.e., the mdf, ldf and
possibly
> ndf. If so, just use sp_attach_db to attach the database files to get each
> database into your desired instance. You can not rename an instance, so
you
> need to install a named instance.
> --
> Tibor Karaszi, SQL Server MVP
> Archive at:
>
http://groups.google.com/groups?oi=djq&as_ugroup=microsoft.public.sqlserver
>
> "Ron Foster" <rlfoster1@.cox.net> wrote in message
> news:%23nvQjkbvDHA.2316@.TK2MSFTNGP10.phx.gbl...
> > When installing Dotnet, wound up with TWO Named SQL Server instances for
> use
> > by the sample apps. When trying to uninstall the extraneous one, I
screwed
> > up and selected the one I wanted to keep. Canceled the uninstall. Server
> is
> > still there. Can start up manually and connect to it. However, the
> > service(s) got whacked before I canceled out.
> >
> >
> >
> > Two questions.
> >
> > 1) Can the services be rebuilt by hand?
> >
> > 2) If I can get the single (named) instance working, can I turn it into
> the
> > default instance? My sole purpose was to be able to test the DotNet
sample
> > apps, all of which are hardwired to connect to local. It's becoming
quite
> a
> > nuisance to fix them all.
> >
> >
> > Any suggestions would be greatly appreciated. TIA
> >
> >
>sql

Reattaching System Databases

I had to uninstall a SQL Server 2000 installation. Before I uninstalled it
I copied the Data directory to a different drive. After I reinstalled it I
copied my user databases back to the new Data directory and re-attached
them. My problem is I can not find a way copy the system databases back to
the new Data directory to re-attach them. I tried it with the Master.mdf
after shuting down SQL Server, but it wouldn't start back up. I do not have
a backup to restore from, only the .mdf and ldf files.
Is there a way to attach the old sytem database mdf and ldf files to the new
SQL Server installation.
Thanks
MikeAs a last ditch attempt, you could attach them as another database, perform a backup of the new database and then restore the master with the backup.|||Hi,
Instead of attaching the User databases perform the below steps,
After installation perform ,
1. Stop the SQL Server / SQL Agent service
2. Move all the new MDF and LDF to a new location (System databases)
3. Copy all the old MDF and LDF files back to the old location where the
files resides previously (Includes old System databases)
4. Start SQL server back
Thanks
Hari
MCDBA
"M Smith" <msmith@.avma.org> wrote in message
news:ONhB#8xzDHA.1740@.TK2MSFTNGP12.phx.gbl...
> I had to uninstall a SQL Server 2000 installation. Before I uninstalled
it
> I copied the Data directory to a different drive. After I reinstalled it
I
> copied my user databases back to the new Data directory and re-attached
> them. My problem is I can not find a way copy the system databases back
to
> the new Data directory to re-attach them. I tried it with the Master.mdf
> after shuting down SQL Server, but it wouldn't start back up. I do not
have
> a backup to restore from, only the .mdf and ldf files.
> Is there a way to attach the old sytem database mdf and ldf files to the
new
> SQL Server installation.
> Thanks
> Mike
>