Skip to main content

Permission to Manage SQL Server Agent only

Last month i have been faced with a great question that was, how to give permission to any user for manage SQL Server Agent, create,edit and monitor jobs only?

This permission or role is relevant to server and service level, So we have to give permission at System Database Level and for SQL Server Agent only one Database is relating that is msdb.  

So i follow the steps to give permission…

  1.) Create a new user sql or domain :  "SqlAgentUser"
  2.) Now map the msdb database.

  3.) Then give below permission form same box and finally click on ok
a.      Db_owner
b.      Db_ssisadmin
c.      Db_ssisltduser
d.      Db_ssisoperator
e.      Dc_proxy
f.      Dc_Operator
g.      Dc_Admin
h.      SQLAgentOperatorRole
i.      SQLAgentReaderRole
j.      SQLAgentUserRole

   Now Connect to the Instance with the New User SqlAgentUser and credential. We will we have access to manage agent only non-other than db.



Popular posts from this blog

mongoDB error : aborting after fassert() failure

What to do when facing errors on mongoDB “aborting after fassert() failure” I like errors, in mongoDB this is the first error I faced and luckily many times. This error i faced during restoring name-space on local and restarting db system. I am still searching the exact root cause of this issue but i am able to resolve the current problem through below steps. Remove all relevant namespace files from data-file route path.. Now repair mongo instance using mongod process. mongod --repair ////////// execute command from bin folder path  Then start server using mongd process, if started server successfully then .. mongod  ////////// execute command from bin folder path Restore last backups as normal process. Now check database by connecting mongo shell. Thanks for reading,  Please comment your experience if you faced and also share knowledge if you have better steps to resolve...  

SQL71562: external references are not supported when creating a package from this platform

Last week I got this error from one of developer who was trying to deploy his project from Testing server to SQL Azure QA server. He was using “Deploy Database to SQL Azure” option from SSMS Tool-Task option. After connecting to SQL Azure portal when operation started to deployment below errors occurs. Validation of the schema model for data package failed. Error SQL71562: Error validating element has an unresolved refrence to object xx.dbo.xxxx external refrences are not supported when creating a package from this platform . Reason: The reason of the this error was; some functions of project was dependent on master database and only single database was being deploy to SQL Azure. DACFx must block Export when object definitions (views, procedures, etc.) contain external references, as Azure SQL Database does not allow cross-database external references So, this error was coming. Solution : I suggested him to create those function to locally

How to add an article in Transactional Replication

If we have a set-up of Transactional Replication for Data Distribution running and wanting to add new object to replication on other server we can follow below process. To add an article In Transaction replication with PUSH Subscription