Default Server Name

I have MSSQLServer version 8 installed. I'm using it to code with .NET. I
somehow ended up with MSSQLServer using an incorrevt server name when it
starts up. It gives me a dropdown box to select the correct servername, but
that's annoying.
My question is how can I get it to use the correct servername as the default
when it loads?
Any help is really appreciated!!
Bob
"Bob" <whoopiea@.whoopie.com> wrote in message
news:%230uT7NxjEHA.2948@.TK2MSFTNGP11.phx.gbl...
> I have MSSQLServer version 8 installed. I'm using it to code with .NET.
I
> somehow ended up with MSSQLServer using an incorrevt server name when it
> starts up. It gives me a dropdown box to select the correct servername,
but
> that's annoying.
Did you change the server name after SQL Server was installed?

> My question is how can I get it to use the correct servername as the
default
> when it loads?
If yes to the above question, use the following (from BOL):
-- substitute the previous name and new name of your servers as appropriate
sp_dropserver old_name
GO
sp_addserver new_name, local
GO
Steve
|||"Steve Thompson" <stevethompson@.nomail.please> wrote in message
news:uP4Nfd4jEHA.3844@.TK2MSFTNGP12.phx.gbl...
> "Bob" <whoopiea@.whoopie.com> wrote in message
> news:%230uT7NxjEHA.2948@.TK2MSFTNGP11.phx.gbl...
> I
> but
> Did you change the server name after SQL Server was installed?
> default
> If yes to the above question, use the following (from BOL):
> -- substitute the previous name and new name of your servers as
appropriate
> sp_dropserver old_name
> GO
> sp_addserver new_name, local
> GO
>
> Steve
>
Steve:
Thanks.
I inadvertantantly installed the sample databases to the wrong place, and
could not access them (ie: Northwind, PUBS, etc...) After alot of
troubleshooting, I got them installed from "\\computername" to
"\\computername\NetSDK". Then I deleted the databases from the data file in
"\\computername". The NetSDK folder is where they are and when I select
"\\computername\NetSDK" from SQL Server Service Manager's screen's dropdown
menu, all is fine. However, "\\computername" always comes up in the
dropdown as the default.
I'm kindof new with programming with SQL Server and not sure how to execute
the commands you suggested (sp_dropserver old_name ... GO
sp_addserver new_name, local ... GO)
All I know is how to code to the database.. creating databases, connection
strings within VS.NET and SQL queries, etc. from the programming environment
(I'm used to DB2, Access and some others).
Any additional insight is appreciated.
Thanks again,
Bob
|||Bob,
Sorry, I misunderstood your original question, it sounded as though you had
renamed your server after the SQL Server install. Since that is not the
case -- disregard my advice.
The dropdown default is something likely stored in your computers
registry...
Steve
"Bob" <whoopiea@.whoopie.com> wrote in message
news:eMn0Pa$jEHA.2680@.TK2MSFTNGP15.phx.gbl...[vbcol=seagreen]
> "Steve Thompson" <stevethompson@.nomail.please> wrote in message
> news:uP4Nfd4jEHA.3844@.TK2MSFTNGP12.phx.gbl...
..NET.[vbcol=seagreen]
it[vbcol=seagreen]
servername,
> appropriate
> Steve:
> Thanks.
> I inadvertantantly installed the sample databases to the wrong place, and
> could not access them (ie: Northwind, PUBS, etc...) After alot of
> troubleshooting, I got them installed from "\\computername" to
> "\\computername\NetSDK". Then I deleted the databases from the data file
in
> "\\computername". The NetSDK folder is where they are and when I select
> "\\computername\NetSDK" from SQL Server Service Manager's screen's
dropdown
> menu, all is fine. However, "\\computername" always comes up in the
> dropdown as the default.
> I'm kindof new with programming with SQL Server and not sure how to
execute
> the commands you suggested (sp_dropserver old_name ... GO
> sp_addserver new_name, local ... GO)
> All I know is how to code to the database.. creating databases, connection
> strings within VS.NET and SQL queries, etc. from the programming
environment
> (I'm used to DB2, Access and some others).
> Any additional insight is appreciated.
> Thanks again,
> Bob
>