Management Studio lists all databases

A member of db_owner will inherit the VIEW ANY DATABASE permission from the role (see "permissions of fixed database roles" in BOL), which allows him to see all rows in sys.databases. This is done for backward compatibility.

You can deny VIEW ANY DATABASE permission to your user if you don't want him to see all databases.

Thanks
Laurentiu

LaurentiuCristofor at 2007-9-9 >

There isn't any catalog that exposes the databases to which you have access. But I believe you could write a stored procedure to iterate through all sys.databases entries and attempt to use each database, then print the database name if the operation succeeds. You can sign the procedure so that it has the VIEW ANY DATABASE permission, and then you can grant execute on it to public. This way users can execute the procedure even if they don't have direct access to sys.databases.

What default settings are you interested in setting for the login?

Thanks
Laurentiu

LaurentiuCristofor at 2007-9-9 >

Selecting from catalogs will not give you errors if you can't access some rows, you'll just not see them. This is different from actually trying to use an object that you don't have access, when you will get the "either doesn't exist or you don't have access" message.

For questions and suggestions on additional settings offered in the dialog for creating a login, you should again post to SQL Server Tools General.

Thanks
Laurentiu

LaurentiuCristofor at 2007-9-9 >