Alter database properties (shrink size of databases) in GUI - by Uwe Ricken

Status : 


Sign in
to vote
ID 794983 Comments
Status Closed Workarounds
Type Bug Repros 1
Opened 7/25/2013 5:50:48 AM
Access Restriction Public


a database user who's member of the db_owner group cannot shrink database files by using the GUI.

Sign in to post a comment.
Posted by Microsoft on 8/7/2013 at 11:08 AM
Hello Uwe. While "GRANT VIEW SERVER STATE" may give more premission than you want, changing the underlying SMO operations would be out of scale for a PCU item. We must suggest that you continue to advise developers to use DBCC SHRINKFILE.

-Walter A Jokiel, Program Manager, SQL Server (
Posted by Uwe Ricken on 8/7/2013 at 1:57 AM
Dear Charles,

basically "GRANT VIEW SERVER STATE" will give more permissions as planned.
If I grant the privilege to a database owner he/she will have the ability to run dmv for server information I won't provide.

just as an example:
in a shared environment I make the developer A the owner of a database. Now he's responsible for the db and can run any modification for "his" database. I won't allow privileges to monitor server status and health checks against the server.

So - currently - I have to advice the developers that they have to use DBCC SHRINKFILE instead of the GUI.
Posted by Charles [MSFT] on 8/6/2013 at 2:09 PM
Hello Uwe,

May I ask why "GRANT VIEW SERVER STATE TO <login>" isn't a usable workaround for you?

Charles Gagnon (
Posted by Microsoft on 7/26/2013 at 12:53 PM
Hello Uwe. Thank you for bringing this to our attention. We really do appreciate the feedback. We’ll investigate and get back to you.

-Walter A Jokiel, Program Manager, SQL Server (