Important Notice: Our web hosting provider recently started charging us for additional visits, which was unexpected. In response, we're seeking donations. Depending on the situation, we may explore different monetization options for our Community and Expert Contributors. It's crucial to provide more returns for their expertise and offer more Expert Validated Answers or AI Validated Answers. Learn more about our hosting issue here.

What is the impact if we use DYNSA User ID instead of the sa User ID for installs?

Id impact installs SA user
0
Posted

What is the impact if we use DYNSA User ID instead of the sa User ID for installs?

0

You can use the DYNSA User ID as an alternative to the ‘sa’ User ID. This will not impact installs and updates. Make sure the DYNSA has the same rights as the ‘sa’ did and that they also have sufficient SQL Server rights to be able to create Tables. This user must either be in the ‘sysadmin’ fixed server role or the ‘db_owner’ role for the DYNAMICS database. Also, here is the Role and Task for Omni Tools. Please make sure the DYNSA User ID is assigned to it.

0
Ben Mulu

Our company had policy not allow sa user for execute batch job .How can I created new user instead sa user for execute batch job with same authority.

I try to created new user(I created jobrun user) and changed it in my batch job but when that job executed it show in log “Executed as user NT SERVICE\SQLSEVERAGENT” .

I don’t understand why it executed by NT Authorize instead Jobrun user.I’d like toknow how can  I execute batch job by jobrun user .

Regards,

Ben

Related Questions

What is your question?

*Sadly, we had to bring back ads too. Hopefully more targeted.

Experts123