You could use the following query to provide some quick details about the domain admin:
FROM sys.dm_exec_sessions des
INNER JOIN sys.dm_exec_connections dec ON des.session_id = dec.session_id
CROSS APPLY sys....
There is good information in the two existing answers, and you should follow-up on what they suggest.
But be aware that in some cases the account might not be actively connecting, we have seen cases where a user who has SSMS open and has a servers listed in their Central Management Servers (CMS), show as connected when if fact they are not actively doing ...
SQL Server will allow you to create a database user for a domain account, even if the corresponding login does not exist. No error will be returned as long as the user creating the database user has CREATE USER permissions and the domain account is valid.
However, the new user will not be able to authenticate to the instance until a login for that account (...
It might sound a silly question,
I think you have a security requirement written by someone who doesn't know what he is doing, and then implemented by someone else who doesn't know what he is doing. "Silly" is far too benign a word to describe this. I hope this is a toy system completely firewalled off from the internet.
sudo su - abc -c "psql"
You said ...
It's not good idea to have built-in accounts or default security groups i.e. Domain Users, Domain Admins etc.. to have access on SQL Server. Instead, create separate windows account/domain security groups to have access on SQL Server.
Also, some of best practices as follows, for more details have a look at security benchmark
Always disable sa ...
This will allow a specific user (user1) to run any Sql Agent job.
Members of SQLAgentUserRole and SQLAgentReaderRole can only start jobs that they own. Members of SQLAgentOperatorRole can start all local jobs including those that are owned by other users
CREATE USER [user1] FOR LOGIN [user1]
ALTER ROLE [SQLAgentOperatorRole] ...