I really like the feature known as “All Permissions Grantable” in which any permission can be managed using the GRANT verb, because there are no “magic” logins or users anymore. The coolest thing is that all server roles are now defined in terms of the permissions they have; this chart is in the BOL. In it, sysadmin equates to CONTROL SERVER. <\/P>
\n
But I did notice when reading through BOL that many things are defined as “this can only be done by sysadmin”. But what if I’m not sysadmin and I do have CONTROL SERVER? Can I do those “sysadmin only“ things? Or the collolary: if I am granted CONTROL SERVER, do I become sysadmin (that is, show up in the system tables as sysadmin).<\/P>
\n
At least with the first three items I tried, I can perform the “sysadmin only” function but I’m not sysadmin. Good thing to remember when looking through an instance for high privilege users, to make sure some logins don’t slip through the cracks. Here’s example:<\/P>
\n
create login bob with password = ‘StrongPW1’
go
grant control server to bob
go
— login as bob or
execute as login=’bob’
go
create database sample
go
— this works for bob
alter database sample set trustworthy on
go
— bob is not a member of sysadmin server role
— BOL says he must be
sp_helpsrvrolemember ‘sysadmin’
go<\/P><\/p>\n","protected":false},"excerpt":{"rendered":"
I really like the feature known as “All Permissions Grantable” in which any permission can be managed using the GRANT verb, because there are no “magic” logins or users anymore. The coolest thing is that all server roles are now defined in terms of the permissions they have; this chart is in the BOL. In it, […]<\/p>\n","protected":false},"author":7,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1],"tags":[],"class_list":["post-929","post","type-post","status-publish","format-standard","hentry","category-uncategorized"],"yoast_head":"\n