Skip to main content

Effective Permissions on a Database

written by David Postlethwaite

Ever wondered who has what access to your database or a particular object within? With the ever increasing need to keep permissions to a minimum this is becoming more important.

If you are using Active Directory groups to assign permissions to your servers and your databases it’s not always obvious what the combined permissions might be for a particular user who may be a member of several groups.You can check the effective permissions to a database using the following command.  Thus far I’ve been unable to find out where this can be found in SQL Server Management Studio (SSMS)

use databaseName
EXECUTE AS USER = 'domain\fred';
SELECT * FROM fn_my_permissions(NULL, 'DATABASE');

This will only work for accounts that have a specific database permission. If you try it with a sysadmin  account which has permission through the server role but has no specific database permissions you will get an error like this:

Msg 916, Level 14, State 1, Line 1
The server principal "domain\serviceAccount" is not able to access the database "databaseName" under the current security context.

It has been useful in finding accounts that have managed to get full permissions by virtue of being linked to the dbo account, something which isn’t immediately obvious in SSMS

Moving down to a more granular level it’s also possible to check the explicit permissions to a specific object such as a stored procedure in a database:

use databaseName
EXECUTE AS USER = 'domain\fred';
SELECT * FROM fn_my_permissions('storedproc1, 'OBJECT')
ORDER BY subentity_name, permission_name ;

This command will not show the effective permissions, this can be seen in the permission tab of the properties of an object in SSMS.

And if you need to grant permissions to an object here is the syntax

grant execute on dbo.storedProc1 to [domain\fred]

In my next article I will show an easy way to grant explicit permissions to every stored procedure and function in a database.


Popular posts from this blog

SQL Server 2012 and Virtual Service Accounts

This post is written by David Postlethwaite
If you are using SQL Server 2012 you will probably have noticed that the default account for the SQL services has changed from that used in previous versions. With SQL 2005 and 2008 the default account for SQL service and SQL Agent service was “NT Authority\System”. This is one the built in accounts on a Windows machine, managed by the machine and selectable from a dedicated dropdown list

The Network Service account was introduced in Windows 2003 as an alternative to using the LocalSystem account, which has full local system privileges on the local machine, a major security concern.
The Network Service has limited local privileges easing these security concerns but when many services on a machine use the Network Service account it becomes harder to track which service is actually accessing resources and performing actions, because all the services are using the one Network Service account.
Also, this account, by default, has sysadmin per…

Always Encrypted

By David Postlethwaite

Always Encrypted is new features in SQL Server 2016 and it is also available in Azure SQL Database. Here you can encrypt columns in a table with a master key and a certificate so that they will appear as encrypted strings to those who don’t have the required certificate installed on their pc.
Once the certificate is installed on the computer then the unencrypted data can then be seen as normal.

The data passes from database to your application as the encrypted value, only the application with the correct certificate can unencrypt the data so it is secure across the wire. This will go some way to resolving the concern of people worried about putting their sensitive data on a shared server in the cloud such as Microsoft Azure and accessing the data across the Internet.

At the time of writing Always Encrypted is only supported with ADO.NET 4.6, JDBC 6.0 and ODBC 13.1 but expect other driver to become available.

The calling application (including SSMS) must also hav…

New in SQL Server 2017: Graph Databases

David has recorded and published a video of his presentation on SQL Server Graph Database. In his video which you can watch below, David provides an excellent introduction into SQL Server 2017 Graph Databases. In his presentation he looks at Tennis results at tournaments for  his favourite player "The Fed"  Rodger Federer.

David  shows how to set up graph database and work with them in SQL Server 2017.

Graph Database is not new. Other vendors have had graph database capabilities for some time so Microsoft are quite late to the market. In David presentation it appears that Microsoft have done a reasonable job of implementing some of the graph database features but he does point some of the limitations of the Microsoft product too and suggests that it is not ready for production yet but Microsoft seem serious about this feature.

Please watch the video and feel free to leave a comment or feedback - David is delivering a version of this talk on Graph databases in SQL Saturday Ka…