Hide database names from unauthroized users in SSMS

If a user is not authorized to see a database can I exclude that database from even appearing in Management Studio for that user

TIA,

Barkingdog

Hi,

you would need to revove the permission 'VIEW ANY DATABASE' from the role PUBLIC.

HTH, Jens K. Suessmeyer.

http://www.sqlserver2005.de|||

I found the server-level permission "View any database", denied it to the test user, and found exactly that. The user couldn't see (under SSMS) any databases whatsoever including the one he is the DBO of! How can I assign him permissions to see that one database but no others in the SSMS tree?

TIA,

Barkingdog

P.S. The evidence is if I removed that permission from "public" then no one -- maybe even the sa? - could see any databases in SSMS.!

|||

How are you making the user an owner? Are you making him a member of db_owner or are you using the alter authorization statement to make the user the actual owner of the database?

You can tell by looking at the owner_sid in sys.databases - the sid should point to the owning login. If the login is the owner of the database, denying that user view any database will not prevent him from viewing the database in sys.databases or Management Studio.

Jack Richins
SDE Sql Server

|||

I made him a member of the db_owner.

When I run

sp_helpuser <DBName>

it returns x01 as the SID for the username dbo.

When I run

use DBName

select * from sys.databases

it returns.......

0x010500000000000515000000AAB950D6A501....

for the owner sid of the database.

So the user is not the DBO (though he belongs to that role).

Then back to my original question. How can I deny a user from seeing any databses in the SSMS tree that he does not have permission to access?

TIA,

Barkingdog

|||

DENY VIEW ANY DATABASE to the test login. This prevents the user from seeing any databases for which the user is not the DBO. You can make the user a DBO by using ALTER AUTHORIZATION DATABASE::<database> TO <login>. Being a member of db_owner is not sufficient to see the database if "view any database" was denied.

This is not very clean and may not work for you if you can't make this user login the actual DBO of the database you want him to administer or have multiple logins you want to secure in this manner as only a single login can be the actual DBO of a database.

This is something we're investigating for future improvements. So if you could provide some details on what you would like this login to be able to do and what you don't want the login to see or do, it could help us better solve your problems as we design future versions of SQL Server. Also whether you use SQL Logins or Windows Integrated Logins - how many different logins you'd like to secure in this way, and anything else you think might be relevant.

Thanks,
Jack Richins
SDE SQL Server

|||

Dear Jack,

This whole issue took me by surprise. In our shop we have three teams of developers and all the development datbases are in a single sql instance. One of the group leaders asked me if there is any way to prevent those not in his group from even seeing the database display name under SSMS and sql tools (e.g. query editor, via OLEDB). I don't know the reason for his concern -- developers outside his group are not authorized to even view his databases but from a security perspective it seems reasonable: If a user does not have access to a databse, why should the database even "exist" for that user. This applies regardless of the form of Windows authentication used.

TIA,

Barkingdog

|||

Thanks, this isn't a scenario we'd been discussing so I'm glad you brought this up. I'm sorry we don't have a solution for you now, but hopefully in the future we can do something to enable this.

Thanks,
Jack Richins
SDE SQL Server

|||Although it blocks users from seeing other databases in the SMSS database dropdown, as the user I can still query sys.databases and see everything and I have used the deny view any database to public. In a hosting environment, this just won't be acceptable. In sql 2000, I just created a sysdatabases view that looked at your credentials and passed what you had rights to. Can't do that in 2005, but definately need this.|||

The main issue here is that determining what databases a user can see is an expensive check, as the permissions to access the database are stored in the database itself, so verifying them requires a database access. This prevents a general solution from being available through SSMS - some customers manage hundreds of databases on a single server, which would make such checks prohibitive.

You can still write a view in SQL Server 2005 that could filter rows using "has_dbaccess() = 1" as a predicate, but you should only do this if you have a limited number of databases, as it would be too expensive otherwise.

I also want to add that we're aware of this request and we're looking at ways to address it.

Thanks
Laurentiu

Hide database names from unauthroized users in SSMS

If a user is not authorized to see a database can I exclude that database from even appearing in Management Studio for that user

TIA,

Barkingdog

Hi,

you would need to revove the permission 'VIEW ANY DATABASE' from the role PUBLIC.

HTH, Jens K. Suessmeyer.

http://www.sqlserver2005.de
|||

I found the server-level permission "View any database", denied it to the test user, and found exactly that. The user couldn't see (under SSMS) any databases whatsoever including the one he is the DBO of! How can I assign him permissions to see that one database but no others in the SSMS tree?

TIA,

Barkingdog

P.S. The evidence is if I removed that permission from "public" then no one -- maybe even the sa? - could see any databases in SSMS.!

|||

How are you making the user an owner? Are you making him a member of db_owner or are you using the alter authorization statement to make the user the actual owner of the database?

You can tell by looking at the owner_sid in sys.databases - the sid should point to the owning login. If the login is the owner of the database, denying that user view any database will not prevent him from viewing the database in sys.databases or Management Studio.

Jack Richins
SDE Sql Server

|||

I made him a member of the db_owner.

When I run

sp_helpuser <DBName>

it returns x01 as the SID for the username dbo.

When I run

use DBName

select * from sys.databases

it returns.......

0x010500000000000515000000AAB950D6A501....

for the owner sid of the database.

So the user is not the DBO (though he belongs to that role).

Then back to my original question. How can I deny a user from seeing any databses in the SSMS tree that he does not have permission to access?

TIA,

Barkingdog

|||

DENY VIEW ANY DATABASE to the test login. This prevents the user from seeing any databases for which the user is not the DBO. You can make the user a DBO by using ALTER AUTHORIZATION DATABASE::<database> TO <login>. Being a member of db_owner is not sufficient to see the database if "view any database" was denied.

This is not very clean and may not work for you if you can't make this user login the actual DBO of the database you want him to administer or have multiple logins you want to secure in this manner as only a single login can be the actual DBO of a database.

This is something we're investigating for future improvements. So if you could provide some details on what you would like this login to be able to do and what you don't want the login to see or do, it could help us better solve your problems as we design future versions of SQL Server. Also whether you use SQL Logins or Windows Integrated Logins - how many different logins you'd like to secure in this way, and anything else you think might be relevant.

Thanks,
Jack Richins
SDE SQL Server

|||

Dear Jack,

This whole issue took me by surprise. In our shop we have three teams of developers and all the development datbases are in a single sql instance. One of the group leaders asked me if there is any way to prevent those not in his group from even seeing the database display name under SSMS and sql tools (e.g. query editor, via OLEDB). I don't know the reason for his concern -- developers outside his group are not authorized to even view his databases but from a security perspective it seems reasonable: If a user does not have access to a databse, why should the database even "exist" for that user. This applies regardless of the form of Windows authentication used.

TIA,

Barkingdog

|||

Thanks, this isn't a scenario we'd been discussing so I'm glad you brought this up. I'm sorry we don't have a solution for you now, but hopefully in the future we can do something to enable this.

Thanks,
Jack Richins
SDE SQL Server

|||Although it blocks users from seeing other databases in the SMSS database dropdown, as the user I can still query sys.databases and see everything and I have used the deny view any database to public. In a hosting environment, this just won't be acceptable. In sql 2000, I just created a sysdatabases view that looked at your credentials and passed what you had rights to. Can't do that in 2005, but definately need this.|||

The main issue here is that determining what databases a user can see is an expensive check, as the permissions to access the database are stored in the database itself, so verifying them requires a database access. This prevents a general solution from being available through SSMS - some customers manage hundreds of databases on a single server, which would make such checks prohibitive.

You can still write a view in SQL Server 2005 that could filter rows using "has_dbaccess() = 1" as a predicate, but you should only do this if you have a limited number of databases, as it would be too expensive otherwise.

I also want to add that we're aware of this request and we're looking at ways to address it.

Thanks
Laurentiu

|||I have tried changing the view any database property, which works, but the user cannot see the databases that they own... is there something else that needs to be done for them to see these databases and no others?|||

This is what I ended up doing:

--SQL 2005

If @.@.version like 'Microsoft SQL Server 2005%'

Begin -- Create Login only if it doesn't exist:

IF NOT EXISTS (SELECT * FROM sys.server_principals WHERE [name] = @.Username)

Begin

Set @.dsql ='create login ' + @.Username + ' with password = N'''+ REPLACE(@.password, '''', '''''') + ''', DEFAULT_DATABASE=' + QUOTENAME(@.DBName) + ', CHECK_EXPIRATION=OFF, CHECK_POLICY=OFF'

execute (@.dsql)

set @.dsql = 'use master; GRANT CONNECT SQL TO ' + QUOTENAME(@.DBName)

execute( @.dsql )

End

--Deny ability to see anything other than master, tempdb and user database.

Set @.dsql = 'use master; deny VIEW any DATABASE to ' + @.Username

--Print @.dsql

execute (@.dsql)

End

--Add user as dbo to database.

Set @.dsql = @.DBName + '.dbo.sp_changedbowner ' + @.Username

--Print @.dsql

execute (@.dsql)

But, I don't think you can grant multiple user's to DBO, so you will only have one user that can see master, temp, and their database.

-Chuck Lathrope

Hide database names from unauthroized users in SSMS

If a user is not authorized to see a database can I exclude that database from even appearing in Management Studio for that user

TIA,

Barkingdog

Hi,

you would need to revove the permission 'VIEW ANY DATABASE' from the role PUBLIC.

HTH, Jens K. Suessmeyer.

http://www.sqlserver2005.de|||

I found the server-level permission "View any database", denied it to the test user, and found exactly that. The user couldn't see (under SSMS) any databases whatsoever including the one he is the DBO of! How can I assign him permissions to see that one database but no others in the SSMS tree?

TIA,

Barkingdog

P.S. The evidence is if I removed that permission from "public" then no one -- maybe even the sa? - could see any databases in SSMS.!

|||

How are you making the user an owner? Are you making him a member of db_owner or are you using the alter authorization statement to make the user the actual owner of the database?

You can tell by looking at the owner_sid in sys.databases - the sid should point to the owning login. If the login is the owner of the database, denying that user view any database will not prevent him from viewing the database in sys.databases or Management Studio.

Jack Richins
SDE Sql Server

|||

I made him a member of the db_owner.

When I run

sp_helpuser <DBName>

it returns x01 as the SID for the username dbo.

When I run

use DBName

select * from sys.databases

it returns.......

0x010500000000000515000000AAB950D6A501....

for the owner sid of the database.

So the user is not the DBO (though he belongs to that role).

Then back to my original question. How can I deny a user from seeing any databses in the SSMS tree that he does not have permission to access?

TIA,

Barkingdog

|||

DENY VIEW ANY DATABASE to the test login. This prevents the user from seeing any databases for which the user is not the DBO. You can make the user a DBO by using ALTER AUTHORIZATION DATABASE::<database> TO <login>. Being a member of db_owner is not sufficient to see the database if "view any database" was denied.

This is not very clean and may not work for you if you can't make this user login the actual DBO of the database you want him to administer or have multiple logins you want to secure in this manner as only a single login can be the actual DBO of a database.

This is something we're investigating for future improvements. So if you could provide some details on what you would like this login to be able to do and what you don't want the login to see or do, it could help us better solve your problems as we design future versions of SQL Server. Also whether you use SQL Logins or Windows Integrated Logins - how many different logins you'd like to secure in this way, and anything else you think might be relevant.

Thanks,
Jack Richins
SDE SQL Server

|||

Dear Jack,

This whole issue took me by surprise. In our shop we have three teams of developers and all the development datbases are in a single sql instance. One of the group leaders asked me if there is any way to prevent those not in his group from even seeing the database display name under SSMS and sql tools (e.g. query editor, via OLEDB). I don't know the reason for his concern -- developers outside his group are not authorized to even view his databases but from a security perspective it seems reasonable: If a user does not have access to a databse, why should the database even "exist" for that user. This applies regardless of the form of Windows authentication used.

TIA,

Barkingdog

|||

Thanks, this isn't a scenario we'd been discussing so I'm glad you brought this up. I'm sorry we don't have a solution for you now, but hopefully in the future we can do something to enable this.

Thanks,
Jack Richins
SDE SQL Server

|||Although it blocks users from seeing other databases in the SMSS database dropdown, as the user I can still query sys.databases and see everything and I have used the deny view any database to public. In a hosting environment, this just won't be acceptable. In sql 2000, I just created a sysdatabases view that looked at your credentials and passed what you had rights to. Can't do that in 2005, but definately need this.|||

The main issue here is that determining what databases a user can see is an expensive check, as the permissions to access the database are stored in the database itself, so verifying them requires a database access. This prevents a general solution from being available through SSMS - some customers manage hundreds of databases on a single server, which would make such checks prohibitive.

You can still write a view in SQL Server 2005 that could filter rows using "has_dbaccess() = 1" as a predicate, but you should only do this if you have a limited number of databases, as it would be too expensive otherwise.

I also want to add that we're aware of this request and we're looking at ways to address it.

Thanks
Laurentiu

Hidden max number of columns in Management Studio?

Hi,
The following is observed in the SQLServer 2005 Management Studio Visual
Editor:
Open table (Right Click option on a table) fails when I try it on a table
with lots of columns in it > 820 columns! Currently the table has no rows
(empty table). The same table opens fine with sql 2000 enterprise manager.
This table has been migrated/imported from sql 2000 without any errors! Other
imported tables with less number of columns can be opened in the visual
editor!
Wondering is there a hidden limit in terms of number of columns with
SQLserver 2005 Management Studio (Grid) Visual Editor?
I get SQL Executaion error
Error Source: Microsoft.VisualStudio.DataTools
Exception has been thrown by the target of an invocation
Is this a known behavior/limitation/bug? Is there a workaround?
Thanks
Kan,
See
http://www.sql-server-performance.co...ID=9016鵬
You may wish to report this as a bug at the suggested URL
http://lab.msdn.microsoft.com/produc...k/default.aspx
(also in the thread).
Steve Kass
Drew University
Kan wrote:

>Hi,
>The following is observed in the SQLServer 2005 Management Studio Visual
>Editor:
>Open table (Right Click option on a table) fails when I try it on a table
>with lots of columns in it > 820 columns! Currently the table has no rows
>(empty table). The same table opens fine with sql 2000 enterprise manager.
>This table has been migrated/imported from sql 2000 without any errors! Other
>imported tables with less number of columns can be opened in the visual
>editor!
>Wondering is there a hidden limit in terms of number of columns with
>SQLserver 2005 Management Studio (Grid) Visual Editor?
>I get SQL Executaion error
>Error Source: Microsoft.VisualStudio.DataTools
>Exception has been thrown by the target of an invocation
>Is this a known behavior/limitation/bug? Is there a workaround?
>Thanks
>
>

Hi Here Nasir

IN MY SYSTEM MICROSOFT SQL SERVER 2005 IS INSTALL ... WHEN I START MICROSOFT SQL SERVER 2005
ONE OPTION IS COME package Microsoft SQL Management Studio package' failed to load ..

SO I CANT ACESS MICROSOFT SQL SERVER 2005 ..
SO CAN U TELL ME WHATS A BROBLEM FROM THIS
--

Quote:

Originally Posted by nasir ghani

IN MY SYSTEM MICROSOFT SQL SERVER 2005 IS INSTALL ... WHEN I START MICROSOFT SQL SERVER 2005
ONE OPTION IS COME package Microsoft SQL Management Studio package' failed to load ..



SO I CANT ACESS MICROSOFT SQL SERVER 2005 ..
SO CAN U TELL ME WHATS A BROBLEM FROM THIS
--

Moved to SQL server forum.|||Does this link give you any hints?

Hi

Can any one let me know why named pipes protocol in disabled by default in SQL 2005 on SQL server management >> protocols?

Thanks

Named pipes connections will allow remote conenctions why is disabled by default. This is one of the new directives of the new Server systems, secure by default. Many features are disabled by default but can be explicitly enabled by using a command or the appropiate GUIs shipped with SQL Server.

Jens K. Suessmeyer

http://www.sqlserver2005.de

|||There is no specific reason but the developer edition and the Express users just need to spend time with the surface area configuration tool and configuration manager because most services comes disabled by default.

Help: I can open my database in Management Studio, but can't connect it in Integration Services

Received error tip:

An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: SQL Network Interfaces, error: 26 - Error Locating Server/Instance Specified)

I'm using the Evaluation Edition of SQL Server 2005, Windows XP SP2 Home Edition.

I have disabled the firewall.

You need to enable remote connections:

http://www.sqlserver2005.de/Sharedfiles/remoteconnection.jpg

HTH, Jens Suessmeyer.

http://www.sqlserver2005.de

|||

Yes, I have enable remote connections, but still wrong.

Can the Home Edition of Windows XP support SQL Server?

|||

Hi, only the developer edition and the express edition are supposed to work on Windows XP Home (as of the offical system requirements, didn′t tested that out yet). Let me hear some feedback if that worked for you.

HTH, Jens Suessmeyer.

http://www.sqlserver2005.de

|||I have installed SQL Server Evaluation Edition on Windows XP Home Edition. It can work. In the Management Studio, the database can be opened and executed. The only one problem is that in the reporting services, the database can't be connetcted.

Help: error when trying to connect to server using sql server 2005 express

Dear all,

I have installed sql server 2005 Express with SQLADV.exe. But when I open Management Studio Express it has error:

Can not connect to server

An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: SQL Network Interfaces, error: 26 - Error locating Server/Instance Specified).

I searched on google but did not find any solution. Anyone know about that, please help me.

check this link http://blogs.msdn.com/sql_protocols/archive/2006/09/30/SQL-Server-2005-Remote-Connectivity-Issue-TroubleShooting.aspx

there are few things to be done to access database engine

(a) Remote connection to be enabled

(b) Create exception if firewall is enabled on this srever

(c) start SQL Browser service

(d) check the protocols

Madhu

|||

Dear Madhu K Nair,

I just use my local computer to test, how can I check for protocol and should I do it. Now I just use my computer to create a website and database in my computer too.

|||

check this http://support.microsoft.com/kb/914277

Madhu

|||

Please check my blog for this:

http://blogs.msdn.com/sql_protocols/archive/2007/05/13/sql-network-interfaces-error-26-error-locating-server-instance-specified.aspx