Using sp_dropserver

18 Aug 2006 4:49 PM

moondaddy

For a week I have been trying to resolve an issue with VS2005 where it will
not debug sql server 2k or 05. One of the many links I was given or found
to resolve this is:

http://support.microsoft.com/kb/317241/en-us

this is the only one I haven't tried yet for fear that I could make matters
much worse. It tells me to drop the server and then re-add it. upon
looking into sp_dropserver I see that I have to first remove all logins and
accounts.

1) does this mean I also have to add in all system accounts after adding
the server back in such as SA and anything used by SSRS? Things seem to be
so complicated with various depenancies and permissions that I would have a
very difficult time restoring all the correct logins, accounts, and
permissions after adding the server back in. What's the risk here and any
recommendations of how to set it backup?

2) how does dropping and re-adding as server effect all of my databases?

3) any other comments?

Thanks.

--
moondaddy@noemail.noemail

18 Aug 2006 5:05 PM

Arnie Rowland

Using sp_dropserver will not affect databases, logins, accounts, etc. It
should only affects the 'list' of servers that SSMS knows about.

SP_DropServer will remove a server from the list of servers in
master.dbo.sysservers, and then using sp_addserver or sp_addlinkedserver to
add one back -allowing you to 'clean up' naming mistakes.

--
Arnie Rowland, Ph.D.
Westwood Consulting, Inc

Most good judgment comes from experience.
Most experience comes from bad judgment.
- Anonymous

Show quote

"moondaddy" <moondaddy@noemail.noemail> wrote in message
news:OmHTgYuwGHA.3904@TK2MSFTNGP02.phx.gbl...
> For a week I have been trying to resolve an issue with VS2005 where it
> will not debug sql server 2k or 05. One of the many links I was given or
> found to resolve this is:
>
> http://support.microsoft.com/kb/317241/en-us
>
> this is the only one I haven't tried yet for fear that I could make
> matters much worse. It tells me to drop the server and then re-add it.
> upon looking into sp_dropserver I see that I have to first remove all
> logins and accounts.
>
> 1) does this mean I also have to add in all system accounts after adding
> the server back in such as SA and anything used by SSRS? Things seem to
> be so complicated with various depenancies and permissions that I would
> have a very difficult time restoring all the correct logins, accounts, and
> permissions after adding the server back in. What's the risk here and any
> recommendations of how to set it backup?
>
> 2) how does dropping and re-adding as server effect all of my databases?
>
> 3) any other comments?
>
> Thanks.
>
>
>
> --
> moondaddy@noemail.noemail
>