Since a local system account doesn't allow backing up to another drive, I
made a new domain account so we could backup to a different drive than where
SQL Server 2005 resides. What happened then was all the jobs created under
the other account would not run. Do we have to recreate the jobs to run under
the new account or is there a way to repoint these jobs for running under the
new account. Is it as simple as I need to add this account as sysadmin on sql
server?
--
Regards,
Pat

Pat,

You should be able to simply update the owner of the jobs if you are a
sysadmin. (Or get a sysadmin to do the work for you, if you are not.) In
SSMS open the job and choose a new Owner. Or you could script a change to
the affected jobs to use.

EXEC sp_update_job @job_name = 'Job Name', @owner_login_name =
'Domain\Login'

An additional note, I always run my SQL Servers under a domain account, not
local system.

RLF

"Pat M - City of Reno" <PatMCityofReno (AT) discussions (DOT) microsoft.com> wrote in
message news:1503AEDC-23B9-422D-BA12-1B85B7B7EAA9 (AT) microsoft (DOT) com...

Pat,

You should be able to simply update the owner of the jobs if you are a
sysadmin. (Or get a sysadmin to do the work for you, if you are not.) In
SSMS open the job and choose a new Owner. Or you could script a change to
the affected jobs to use.

EXEC sp_update_job @job_name = 'Job Name', @owner_login_name =
'Domain\Login'

An additional note, I always run my SQL Servers under a domain account, not
local system.

RLF

"Pat M - City of Reno" <PatMCityofReno (AT) discussions (DOT) microsoft.com> wrote in
message news:1503AEDC-23B9-422D-BA12-1B85B7B7EAA9 (AT) microsoft (DOT) com...

Pat,

You should be able to simply update the owner of the jobs if you are a
sysadmin. (Or get a sysadmin to do the work for you, if you are not.) In
SSMS open the job and choose a new Owner. Or you could script a change to
the affected jobs to use.

EXEC sp_update_job @job_name = 'Job Name', @owner_login_name =
'Domain\Login'

An additional note, I always run my SQL Servers under a domain account, not
local system.

RLF

"Pat M - City of Reno" <PatMCityofReno (AT) discussions (DOT) microsoft.com> wrote in
message news:1503AEDC-23B9-422D-BA12-1B85B7B7EAA9 (AT) microsoft (DOT) com...

Pat,

You should be able to simply update the owner of the jobs if you are a
sysadmin. (Or get a sysadmin to do the work for you, if you are not.) In
SSMS open the job and choose a new Owner. Or you could script a change to
the affected jobs to use.

EXEC sp_update_job @job_name = 'Job Name', @owner_login_name =
'Domain\Login'

An additional note, I always run my SQL Servers under a domain account, not
local system.

RLF

"Pat M - City of Reno" <PatMCityofReno (AT) discussions (DOT) microsoft.com> wrote in
message news:1503AEDC-23B9-422D-BA12-1B85B7B7EAA9 (AT) microsoft (DOT) com...

Pat,

You should be able to simply update the owner of the jobs if you are a
sysadmin. (Or get a sysadmin to do the work for you, if you are not.) In
SSMS open the job and choose a new Owner. Or you could script a change to
the affected jobs to use.

EXEC sp_update_job @job_name = 'Job Name', @owner_login_name =
'Domain\Login'

An additional note, I always run my SQL Servers under a domain account, not
local system.

RLF

"Pat M - City of Reno" <PatMCityofReno (AT) discussions (DOT) microsoft.com> wrote in
message news:1503AEDC-23B9-422D-BA12-1B85B7B7EAA9 (AT) microsoft (DOT) com...

Pat,

You should be able to simply update the owner of the jobs if you are a
sysadmin. (Or get a sysadmin to do the work for you, if you are not.) In
SSMS open the job and choose a new Owner. Or you could script a change to
the affected jobs to use.

EXEC sp_update_job @job_name = 'Job Name', @owner_login_name =
'Domain\Login'

An additional note, I always run my SQL Servers under a domain account, not
local system.

RLF

"Pat M - City of Reno" <PatMCityofReno (AT) discussions (DOT) microsoft.com> wrote in
message news:1503AEDC-23B9-422D-BA12-1B85B7B7EAA9 (AT) microsoft (DOT) com...

Pat,

You should be able to simply update the owner of the jobs if you are a
sysadmin. (Or get a sysadmin to do the work for you, if you are not.) In
SSMS open the job and choose a new Owner. Or you could script a change to
the affected jobs to use.

EXEC sp_update_job @job_name = 'Job Name', @owner_login_name =
'Domain\Login'

An additional note, I always run my SQL Servers under a domain account, not
local system.

RLF

"Pat M - City of Reno" <PatMCityofReno (AT) discussions (DOT) microsoft.com> wrote in
message news:1503AEDC-23B9-422D-BA12-1B85B7B7EAA9 (AT) microsoft (DOT) com...

Pat,

You should be able to simply update the owner of the jobs if you are a
sysadmin. (Or get a sysadmin to do the work for you, if you are not.) In
SSMS open the job and choose a new Owner. Or you could script a change to
the affected jobs to use.

EXEC sp_update_job @job_name = 'Job Name', @owner_login_name =
'Domain\Login'

An additional note, I always run my SQL Servers under a domain account, not
local system.

RLF

"Pat M - City of Reno" <PatMCityofReno (AT) discussions (DOT) microsoft.com> wrote in
message news:1503AEDC-23B9-422D-BA12-1B85B7B7EAA9 (AT) microsoft (DOT) com...

thanks very much Russell, I am sysadmin so should be fine now.

--
Regards,
Pat


"Russell Fields" wrote: