Issue with job run setup in Enterprise Manager

Hello All,
I have a job that consist of over 120 steps. I was able to setup it in Enter
prise Manager and run it. However, the job history can only show display 100
job steps 20 other job steps were missing. Is there a limit set on sysjobhi
story table or am I looking
at the wrong table? Please advice.
Thanks.
DavidThat is very interesting, and I do not know if it is related to the number
of histories per job, but maybe worth a try...
In SEM right click SQL Agent and go to the tab with Job history setup and
try both checking unlimited, and/or max histories per job to something like
300... See if that helps..
Wayne Snyder, MCDBA, SQL Server MVP
Mariner, Charlotte, NC
www.mariner-usa.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
"David" <anonymous@.discussions.microsoft.com> wrote in message
news:A58F9373-EFBA-4426-A2CB-2E14328B18B9@.microsoft.com...
> Hello All,
> I have a job that consist of over 120 steps. I was able to setup it in
Enterprise Manager and run it. However, the job history can only show
display 100 job steps 20 other job steps were missing. Is there a limit set
on sysjobhistory table or am I looking at the wrong table? Please advice.
> Thanks.
> David

Issue with job run setup in Enterprise Manager

Hello All,
I have a job that consist of over 120 steps. I was able to setup it in Enterprise Manager and run it. However, the job history can only show display 100 job steps 20 other job steps were missing. Is there a limit set on sysjobhistory table or am I looking
at the wrong table? Please advice.
Thanks.
David
That is very interesting, and I do not know if it is related to the number
of histories per job, but maybe worth a try...
In SEM right click SQL Agent and go to the tab with Job history setup and
try both checking unlimited, and/or max histories per job to something like
300... See if that helps..
Wayne Snyder, MCDBA, SQL Server MVP
Mariner, Charlotte, NC
www.mariner-usa.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
"David" <anonymous@.discussions.microsoft.com> wrote in message
news:A58F9373-EFBA-4426-A2CB-2E14328B18B9@.microsoft.com...
> Hello All,
> I have a job that consist of over 120 steps. I was able to setup it in
Enterprise Manager and run it. However, the job history can only show
display 100 job steps 20 other job steps were missing. Is there a limit set
on sysjobhistory table or am I looking at the wrong table? Please advice.
> Thanks.
> David

Issue with job run setup in Enterprise Manager

Hello All
I have a job that consist of over 120 steps. I was able to setup it in Enterprise Manager and run it. However, the job history can only show display 100 job steps 20 other job steps were missing. Is there a limit set on sysjobhistory table or am I looking at the wrong table? Please advice
Thanks
DavidThat is very interesting, and I do not know if it is related to the number
of histories per job, but maybe worth a try...
In SEM right click SQL Agent and go to the tab with Job history setup and
try both checking unlimited, and/or max histories per job to something like
300... See if that helps..
--
Wayne Snyder, MCDBA, SQL Server MVP
Mariner, Charlotte, NC
www.mariner-usa.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
"David" <anonymous@.discussions.microsoft.com> wrote in message
news:A58F9373-EFBA-4426-A2CB-2E14328B18B9@.microsoft.com...
> Hello All,
> I have a job that consist of over 120 steps. I was able to setup it in
Enterprise Manager and run it. However, the job history can only show
display 100 job steps 20 other job steps were missing. Is there a limit set
on sysjobhistory table or am I looking at the wrong table? Please advice.
> Thanks.
> David

Issue gettin a sql agent task to stop.

Russell,
do any of the steps invoke DTC or use linked servers?
Russell wrote:
> I Have a daily task that runs a stored procedure to import some orders us
ing
> a call to a third party exe, then to copy and rename a couple of logs and
> then use XPSMTP to send the logs to a couple of people. It has done all o
f
> it except the sending of the e-mail.
> I have noticed this morning that the run of the job from friday was still
> running. So I have killed the process which now says it is rolling back, s
o
> far it has been rolling back for 3 hours. and it does not do much data
> manipulation. If I use kill with status I get:
> SPID 61: transaction rollback in progress. Estimated rollback completion:
> 100%. Estimated time remaining: 0 seconds.
> But the rollback still runs, are ther any executables that SQL uses to run
> extended stored procedures that I could kill that might release this threa
d?
> Regards
> RussellThe job has 3 steps, the first runs a DTS which copies some rows from a
remote server, the second job executes an exe on remote server, the third
step runs a stored procedure which copies a file from a remote server and
renames it, also it runs an ISQL statement to put the output to a file,
lastly it e-mails the 2 files to myself and the finance director. The only
part of the whole process it has not done is to send the e-mail
"shane" wrote:

> Russell,
> do any of the steps invoke DTC or use linked servers?
>
> Russell wrote:
>|||I Have a daily task that runs a stored procedure to import some orders usin
g
a call to a third party exe, then to copy and rename a couple of logs and
then use XPSMTP to send the logs to a couple of people. It has done all of
it except the sending of the e-mail.
I have noticed this morning that the run of the job from friday was still
running. So I have killed the process which now says it is rolling back, so
far it has been rolling back for 3 hours. and it does not do much data
manipulation. If I use kill with status I get:
SPID 61: transaction rollback in progress. Estimated rollback completion:
100%. Estimated time remaining: 0 seconds.
But the rollback still runs, are ther any executables that SQL uses to run
extended stored procedures that I could kill that might release this thread?
Regards
Russell|||Russell,
do any of the steps invoke DTC or use linked servers?
Russell wrote:
> I Have a daily task that runs a stored procedure to import some orders us
ing
> a call to a third party exe, then to copy and rename a couple of logs and
> then use XPSMTP to send the logs to a couple of people. It has done all o
f
> it except the sending of the e-mail.
> I have noticed this morning that the run of the job from friday was still
> running. So I have killed the process which now says it is rolling back, s
o
> far it has been rolling back for 3 hours. and it does not do much data
> manipulation. If I use kill with status I get:
> SPID 61: transaction rollback in progress. Estimated rollback completion:
> 100%. Estimated time remaining: 0 seconds.
> But the rollback still runs, are ther any executables that SQL uses to run
> extended stored procedures that I could kill that might release this threa
d?
> Regards
> Russell|||The job has 3 steps, the first runs a DTS which copies some rows from a
remote server, the second job executes an exe on remote server, the third
step runs a stored procedure which copies a file from a remote server and
renames it, also it runs an ISQL statement to put the output to a file,
lastly it e-mails the 2 files to myself and the finance director. The only
part of the whole process it has not done is to send the e-mail
"shane" wrote:

> Russell,
> do any of the steps invoke DTC or use linked servers?
>
> Russell wrote:
>|||Ive usually come across this problem when there is a distributed
transaction involved.
stop and restart MS DTC, and see if this helps
also try running a dbcc opentran on the database in question, to see if
there are any other transacations which may be interfering..
worst case scenario youll have to stop and restart the sql services
Russell wrote:[vbcol=seagreen]
> The job has 3 steps, the first runs a DTS which copies some rows from a
> remote server, the second job executes an exe on remote server, the third
> step runs a stored procedure which copies a file from a remote server and
> renames it, also it runs an ISQL statement to put the output to a file,
> lastly it e-mails the 2 files to myself and the finance director. The only
> part of the whole process it has not done is to send the e-mail
> "shane" wrote:
>|||Hi Shane,
There are no open transactions and I have restarted the DTC service. So it
looks like I will have to try stopping and starting SQL on the server.
"shane" wrote:

> Ive usually come across this problem when there is a distributed
> transaction involved.
> stop and restart MS DTC, and see if this helps
> also try running a dbcc opentran on the database in question, to see if
> there are any other transacations which may be interfering..
> worst case scenario youll have to stop and restart the sql services
>
> Russell wrote:
>|||Ive usually come across this problem when there is a distributed
transaction involved.
stop and restart MS DTC, and see if this helps
also try running a dbcc opentran on the database in question, to see if
there are any other transacations which may be interfering..
worst case scenario youll have to stop and restart the sql services
Russell wrote:[vbcol=seagreen]
> The job has 3 steps, the first runs a DTS which copies some rows from a
> remote server, the second job executes an exe on remote server, the third
> step runs a stored procedure which copies a file from a remote server and
> renames it, also it runs an ISQL statement to put the output to a file,
> lastly it e-mails the 2 files to myself and the finance director. The only
> part of the whole process it has not done is to send the e-mail
> "shane" wrote:
>|||Hi Shane,
There are no open transactions and I have restarted the DTC service. So it
looks like I will have to try stopping and starting SQL on the server.
"shane" wrote:

> Ive usually come across this problem when there is a distributed
> transaction involved.
> stop and restart MS DTC, and see if this helps
> also try running a dbcc opentran on the database in question, to see if
> there are any other transacations which may be interfering..
> worst case scenario youll have to stop and restart the sql services
>
> Russell wrote:
>