Restricting Enterprise Manager access

[stressball]

Hi,

We have an offsite client who wants to access one of our databases via Enterprise Manager, I have set up a user for them with access only to their one database, however, when testing this, logging in as this user, they can only access their database, however they can view the rest of the databases, with an access denied error message if they attempt to access any of the others. Our problem is that they can still view the list of databases, which we don't want them to be able to do. Is there anyway we can only allow them to see just the one database they have access to on our server?

Thanks.

 

[stressball]

We are using SQL Server 2000

 

[mrdenny]

If you manually delete the guest account for each database it will not show up for anyone who isn't an admin on the server.

The best solution is to simply leave it as is.

Denny
MCSA (2003) / MCDBA (SQL 2000)

--Anything is possible. All it takes is a little research. (Me)

http://www.mrdenny.com

(Not quite so old any more.)

 

[stressball]

Hi,

We have no guest accounts, but yes I think you are right we are going to have to leave this as is until the next version of SQL Server, which apparently does allow you to do this.

 

[DrSql]

You can try to create a new MMC and snap on the EM tools that you deisre. Here is link for a quick start.

http://www.winsupersite.com/showcase/win2k_taskpad.asp

http://www.winsupersite.com/showcase/win2k_980823.asp

Dr. Sql
goEdeveloper@yahoo.com
Good Luck.

 

[stressball]

Hi,

Thanks for that info, but we have no access to our clients site servers, all we are giving them is a username and password so that they can gain access to the databases they require, which they want to be able to do through their version of Enterprise Manager.

Regards,
Stressball

 

[gmmastros]

As another suggestion, you could install a named instance of SQL Server, move the single database to it, and then only grant access to the particular named instance. You'll still want to setup a user account for them and certainly restrict access to the xp_cmdshell command becuase they could then effectively browse your hard drive and see the physical names of the database files.

-George

Strong and bitter words indicate a weak cause. - Fortune cookie wisdom

 

[stressball]

Hi,

Thanks, that sounds like it will solve our problem, although it will impact on our servers performance and require application code changes. But even that is preferable to them seeing our entire list of databases.

Stressball