How can I register the same SQL Server more than once in
Enterprise Manager, using multiple logins?
"A server with this name already exists."
I'd expect this to be a FAQ, but twenty minutes of
googling it has turned up precious little by way of
remedies. This should be a pretty garden-variety
situation: I need to access multiple databases on a single
SQL Server, some of which require a different login from
others. I've added a new server group for the additional
instance/connection/registration, but every attempt to
register the server returns "A server with this name
already exists."
This is a simple thing to accomplish in Query Analyzer,
but I need some of Enterprise Manager's functionality.
Obviously, I could keep deleting and re-registering every
time I need to change context, but that's a pretty tedious
kludge, or I wouldn't be writing this post, you know?
Anyways, is there a hack?
Thanks much.
Create an alias to the SQL Server within the Client Network Utility (within
the SQL Server program group) and then register that alias within Enterprise
Manager.
Keith
"Paul Smith" <paul.smith@.zurichna.com> wrote in message
news:18f301c4a648$0f3dc8e0$a601280a@.phx.gbl...
> How can I register the same SQL Server more than once in
> Enterprise Manager, using multiple logins?
> "A server with this name already exists."
> I'd expect this to be a FAQ, but twenty minutes of
> googling it has turned up precious little by way of
> remedies. This should be a pretty garden-variety
> situation: I need to access multiple databases on a single
> SQL Server, some of which require a different login from
> others. I've added a new server group for the additional
> instance/connection/registration, but every attempt to
> register the server returns "A server with this name
> already exists."
> This is a simple thing to accomplish in Query Analyzer,
> but I need some of Enterprise Manager's functionality.
> Obviously, I could keep deleting and re-registering every
> time I need to change context, but that's a pretty tedious
> kludge, or I wouldn't be writing this post, you know?
> Anyways, is there a hack?
> Thanks much.
>
|||That hit the spot - forgot all about the Client Utility, but what a simple,
quick and straightforward solution (...which is probably why I didn't arrive
at it on my own! heh.)
Thanks.
"Keith Kratochvil" wrote:
> Create an alias to the SQL Server within the Client Network Utility (within
> the SQL Server program group) and then register that alias within Enterprise
> Manager.
> --
> Keith
>
> "Paul Smith" <paul.smith@.zurichna.com> wrote in message
> news:18f301c4a648$0f3dc8e0$a601280a@.phx.gbl...
>
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment