SQL Mgmt studio bug with Linked Servers?

microsoft.public.sqlserver.tools

5 Oct 2006 4:50 PM

smoss

I'm trying to allow some developers to view and/or modify linked servers,
without having to give them sysadmin rights.

Per MS it should work to give them the setupadmin role and Alter Any Linked
Server permissions. However, it works using TSQL, but not through the GUI.
It requires the Sysadmin rights to view/alter through the GUI.

Is this a known issue? I've got Microsoft SQL Server Management
Studio 9.00.1399.00.

The documentation from MS is as follows fyr:

"When you create a linked or remote server, SQL Server creates a default
login mapping to the public server role. This means that by default, all
logins can view all linked and remote servers. To restrict visibility to
these servers, remove the default login mapping by executing
sp_droplinkedsrvlogin and specifying NULL for the locallogin parameter.

If the default login mapping is deleted, only users that have been
explicitly added as a linked login or remote login can view the linked or
remote servers for which they have a login. To view all linked and remote
servers after the default login mapping is deleted requires the following
permissions:

ALTER ANY LINKED SERVER or ALTER ANY LOGIN ON SERVER

Membership in the setupadmin or sysadmin fixed server roles"