Geek asks and answers

Is there a reason why the SQL job should belong to someone other than sa?

In another way, should I always set the owner of the sa job for the SQL job, even if it is the default for the user who created it?

+5
source share
2 answers

Any tasks owned by the user stop running if this user is disconnected or deleted. Jobs may also fail if there is a problem with Active Directory at run time. Brent Ozar has an article about this on his website: http://www.brentozar.com/blitz/jobs-owned-by-user-accounts/

+3
source

You will have to carry with me. Because I'm walking from memory.

Having looked at some old scripts, I have this code.

@jobOwnerNameVeryImportantToSetCorrectly = 'someSqlAuthenticatonUser'

. "" . , , .

, , - " ". "sa", .

, non 'sa' , , --?

.

  • . .
  • temp sql-authentication.
  • .
  • , .

, " ". , Sql Server 2005. , 2005 , 2008 2008R2.

, . , , :

@jobOwnerNameVeryImportantToSetCorrectly = 'someSqlAuthenticatonUser'

0

More articles:


All Articles