Search

SQL Server Job Owner reverts to user who saved the maintenance plan by dhechle

Active

2
0
Sign in
to vote
Type: Bug
ID: 776776
Opened: 1/17/2013 4:17:20 AM
Access Restriction: Public
0
Workaround(s)
0
User(s) can reproduce this bug
This has been raised since SQL Server 2005 and appears it is still a bug in SQL Server 2008 R2. Other reports are 295846 and 454073.
When changing the owner of a SQL job to "sa" for example and then later save the maintenance plan that the job is part of the owner of the SQL job reverts back to the user that saved the maintenance plan, in my case my domain account.
This is not ideal in that when users leave the company the jobs fail. I have seen there are some work arounds to this but why is this not being fixed in any service packs and or upgrades?
Details (expand)

Product Language

English

Version

SQL Server 2008 R2 SP1

Category

SQL Engine

Operating System

Windows Server 2008 R2 Standard (SP1)

Operating System Language

English

Steps to Reproduce

1) Create a SQL maintenance plan to backup a database and save.
2) Check the owner of the SQL job is the user that created the maintenance plan
3) Change the owner of the SQL job to "sa"
4) Edit and save the maintenance plan again
5) Check the owner of the SQL job.

Actual Results

The owner of the SQL job will have reverted back to the user that saved the maintenance plan

Expected Results

Would have thought the owner of the job stays to the "sa" account

Platform

X64

Virtualization

 
File Attachments
0 attachments
Sign in to post a comment.
Posted by Microsoft on 1/29/2013 at 4:18 PM
I can see that this issue was already fixed in SQL Server 2012, but we didn't port the fix back to SQL Server 2008R2. I will keep this issue to port the change from SQL Server 2012 to SQL Server 20008R2 SP3, so keep tuned till we release this SP.

Thank you
Alex Grach [MSFT]
Posted by Microsoft on 1/29/2013 at 2:04 PM
Thank you for reporting this issue - we are investigating and will update you when we have more information.

Thanks,

Alex Grach [MSFT SQL SERVER]
Sign in to post a workaround.