Failed scheduled job

I have a scheduled job which has been failing for a while,
and the only way I have now been able to have it concluded
successfully and with required data transfer result is
when the service-account is member of the domain-admins
group. Adding the service-account only to the local-admins
group of concerned systems gives successfull job
completion but with empty result.
Thus my question is, why must the service-account be
member of the domain-admins group, when the job itself is
to run under the domain-admin account that has full
permission on all systems.
I will appreciated any clarification.What exactly is the job trying to do ?
--
HTH
Jasper Smith (SQL Server MVP)
I support PASS - the definitive, global
community for SQL Server professionals -
http://www.sqlpass.org
"topokin" <bimosekin@.hotmail.com> wrote in message
news:b9c101c381a1$241e5030$a601280a@.phx.gbl...
I have a scheduled job which has been failing for a while,
and the only way I have now been able to have it concluded
successfully and with required data transfer result is
when the service-account is member of the domain-admins
group. Adding the service-account only to the local-admins
group of concerned systems gives successfull job
completion but with empty result.
Thus my question is, why must the service-account be
member of the domain-admins group, when the job itself is
to run under the domain-admin account that has full
permission on all systems.
I will appreciated any clarification.|||Whether or not you need a domain admin account depends on what you are
trying to do. In general, there is really no need for the service account or
the account tha runs the job to be a member of the domain admin. In most
places, you'd be told to get lost by the NT admin if you ask for the domain
admin rights.
I'd suggest you carefully log your jobs. For instance, you can specify an
output file for each step in its Advanced tab. You can then review this
output file to find more about the nature of the failure.
--
Linchi Shea
linchi_shea@.NOSPAMml.com
"topokin" <bimosekin@.hotmail.com> wrote in message
news:b9c101c381a1$241e5030$a601280a@.phx.gbl...
> I have a scheduled job which has been failing for a while,
> and the only way I have now been able to have it concluded
> successfully and with required data transfer result is
> when the service-account is member of the domain-admins
> group. Adding the service-account only to the local-admins
> group of concerned systems gives successfull job
> completion but with empty result.
> Thus my question is, why must the service-account be
> member of the domain-admins group, when the job itself is
> to run under the domain-admin account that has full
> permission on all systems.
> I will appreciated any clarification.
>

failed jobs ..to restart automatically.

hi
my job was scheduled at 11.45 pm..but server went down at 11.40..and restart
ed at 12.10 am..
i want to know
1) how can we reschedule our jobs..so that if server went down and job was s
chedule somewhere in between it should automatically start..
jobs can be anything like backup/reindex//etc
regards
sunnyHi,
Set SQL server agent to start automatically, when the server starts. And the
n schedule your job to run automatically at the startup, i.e when the agent
starts up.
You can use the following stored proc
sp_add_jobschedule
and set @.freq_type = 64
The value 64, sets the job to start automatically, when the sql server agent
starts.
Thanks
GYK

failed jobs ..to restart automatically.

h
my job was scheduled at 11.45 pm..but server went down at 11.40..and restarted at 12.10 am.
i want to kno
1) how can we reschedule our jobs..so that if server went down and job was schedule somewhere in between it should automatically start.
jobs can be anything like backup/reindex//et
regard
sunnHi,
Set SQL server agent to start automatically, when the server starts. And then schedule your job to run automatically at the startup, i.e when the agent starts up
You can use the following stored pro
sp_add_jobschedul
and set @.freq_type = 64
The value 64, sets the job to start automatically, when the sql server agent starts
Thank
GYK