February 2, 2020 at 12:51 pm
Hello.
I have been reading that SYSADMIN cannot be granted at DBLEVEL.
However, when I do a Select * from SYS.SYSLOGINS where SYSADMIN = 1 it returns a Database Name in the DBNAME, either a User DB or Master.
So what is this telling me - if anything ?
Regards
Steve O.
February 2, 2020 at 1:40 pm
Having thought about this as I pressed send I thin that it is actually just telling me what that Users Default DB is in the Login Properties.
Which seems to imply that SYSADMIN is instance wide?
I am going to have a play with the other roles in TEST but what the Admins need to be able to do from within the application is to create/modify SYSLOGINs and Users in MSDB and the Application DB and link the 3 using the same SID and that is it so maybe one of the other roles is more suitable.
Regards
Steve O.
February 2, 2020 at 2:03 pm
sysadmin is server (instance) level role as seen on
description of what each column for syslogins below
and as you will need it for sure https://docs.microsoft.com/en-us/dotnet/framework/data/adonet/sql/server-and-database-roles-in-sql-server
February 3, 2020 at 11:42 am
syslogins will tell you who can connect - if you go into each database and look at sysusers when you will see individual permissions
but a sysadmin will have ALL permissions on ALL databases - if you want admin privileges on a per database basis, then you need to take away sysadmin from the login and set them up as DBO in the database.
Server roles will pretty much always overrule database roles
MVDBA
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply