no job history

sql2k sp3a
One of my servers doesnt retain very much job history. I have no history for
several jobs that run once or more per day. Is there a limit to the amount
of records the SysJobHistory table can hold? Any other ideas?
TIA, ChrisRYes, you can define the limit. EM, right-click Agent, Properties. On one of the tabs, you can set
this.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"ChrisR" <noemail@.bla.com> wrote in message news:evndYNpdFHA.2736@.TK2MSFTNGP12.phx.gbl...
> sql2k sp3a
> One of my servers doesnt retain very much job history. I have no history for several jobs that run
> once or more per day. Is there a limit to the amount of records the SysJobHistory table can hold?
> Any other ideas?
> TIA, ChrisR
>|||Thanks Tibor.
"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
message news:%23EjtESpdFHA.1288@.tk2msftngp13.phx.gbl...
> Yes, you can define the limit. EM, right-click Agent, Properties. On one
> of the tabs, you can set this.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
> Blog: http://solidqualitylearning.com/blogs/tibor/
>
> "ChrisR" <noemail@.bla.com> wrote in message
> news:evndYNpdFHA.2736@.TK2MSFTNGP12.phx.gbl...
>> sql2k sp3a
>> One of my servers doesnt retain very much job history. I have no history
>> for several jobs that run once or more per day. Is there a limit to the
>> amount of records the SysJobHistory table can hold? Any other ideas?
>> TIA, ChrisR
>sql

no job history

sql2k sp3a
One of my servers doesnt retain very much job history. I have no history for
several jobs that run once or more per day. Is there a limit to the amount
of records the SysJobHistory table can hold? Any other ideas?
TIA, ChrisRYes, you can define the limit. EM, right-click Agent, Properties. On one of
the tabs, you can set
this.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"ChrisR" <noemail@.bla.com> wrote in message news:evndYNpdFHA.2736@.TK2MSFTNGP12.phx.gbl...[vb
col=seagreen]
> sql2k sp3a
> One of my servers doesnt retain very much job history. I have no history f
or several jobs that run
> once or more per day. Is there a limit to the amount of records the SysJob
History table can hold?
> Any other ideas?
> TIA, ChrisR
>[/vbcol]|||Thanks Tibor.
"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
message news:%23EjtESpdFHA.1288@.tk2msftngp13.phx.gbl...
> Yes, you can define the limit. EM, right-click Agent, Properties. On one
> of the tabs, you can set this.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
> Blog: http://solidqualitylearning.com/blogs/tibor/
>
> "ChrisR" <noemail@.bla.com> wrote in message
> news:evndYNpdFHA.2736@.TK2MSFTNGP12.phx.gbl...
>

no job history

sql2k sp3a
One of my servers doesnt retain very much job history. I have no history for
several jobs that run once or more per day. Is there a limit to the amount
of records the SysJobHistory table can hold? Any other ideas?
TIA, ChrisR
Yes, you can define the limit. EM, right-click Agent, Properties. On one of the tabs, you can set
this.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"ChrisR" <noemail@.bla.com> wrote in message news:evndYNpdFHA.2736@.TK2MSFTNGP12.phx.gbl...
> sql2k sp3a
> One of my servers doesnt retain very much job history. I have no history for several jobs that run
> once or more per day. Is there a limit to the amount of records the SysJobHistory table can hold?
> Any other ideas?
> TIA, ChrisR
>
|||Thanks Tibor.
"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
message news:%23EjtESpdFHA.1288@.tk2msftngp13.phx.gbl...
> Yes, you can define the limit. EM, right-click Agent, Properties. On one
> of the tabs, you can set this.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
> Blog: http://solidqualitylearning.com/blogs/tibor/
>
> "ChrisR" <noemail@.bla.com> wrote in message
> news:evndYNpdFHA.2736@.TK2MSFTNGP12.phx.gbl...
>

No history information for jobs

Hi All,
When I right click on some jobs in sql server and select view job history, s
ometimes I get "There is no history information for this job". I was able to
see job history few hours/days back. I have not cleared logs nor restarted
the box. But still i am not
able to see any history information. I can however see history information o
n other jobs. Can you tell me why is sql server wiping of job history inform
ation for some jobs. What can i do to prevent it?
Regards,
PROHave you tried increasing the values in SQLAgent-->Properties-->Job
System tab? Look at the Maximum job history log size(rows) and Maximum
job history rows per job values. See if that works for you.
Mark Allison, SQL Server MVP
PRashanth wrote:

> Hi All,
> When I right click on some jobs in sql server and select view job history, sometim
es I get "There is no history information for this job". I was able to see job histo
ry few hours/days back. I have not cleared logs nor restarted the box. But still i a
m n
ot able to see any history information. I can however see history information on other jobs
. Can you tell me why is sql server wiping of job history information for some jobs. What c
an i do to prevent it?
> Regards,
> PRO|||Hi Mark,
Thank you very much for your reply. The current setting of my sql server
is Max. job history log size(rows): 500000
max job history rows per job: 1000
Also, i dont understand why there is no job history for only some of the
jobs
Regards,
PRO
*** Sent via Developersdex http://www.examnotes.net ***
Don't just participate in USENET...get rewarded for it!|||--
|
| Hi Mark,
|
| Thank you very much for your reply. The current setting of my sql server
| is Max. job history log size(rows): 500000
| max job history rows per job: 1000
|
| Also, i dont understand why there is no job history for only some of the
| jobs
|
| Regards,
| PRO
--
It is possible that the job history of more frequently running jobs are
overwriting those of the less frequently running jobs. To address this,
increase your max job history log size and decrease your max job history
rows per job.
Hope this helps,
Eric Cardenas
SQL Server support

Next run date!

Hi,
Yesterday I changed a motherboard on my SQL server 7.0.
Today I noticed that jobs has not been started last night,
and I noticed that date is wrong on this machine,so I did
set the date and time and rebooted the machine, however
still can not see the next run date on scheduled job, even
if I create a new job, I can not see that. Does anyone
know how to fix this?
Thanks in advance-Rob
Hi Rob,
I learned the Job of SQL Server 7.0 did not start after changing the
motherboard and you cannot see the value of "Next run date" property of the
job. As far as I know, after changing the motherboard of the machine,
generally, the old operation system will crash. Do you mean your old
operation system is still available and there is not any problem?
According to your description, it seems all the jobs on your problematic
machine have this problem. If I have misunderstood, please feel free to let
me know. Have you started the SQL Server agent? If the problem still
occurred after starting SQL Server agent, what's the message in the Next
Run Date field of the problematic job?
I am looking forward to hearing from you soon.
Regards,
Michael Shao
Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security
This posting is provided "as is" with no warranties and confers no rights.
|||Hi Rob,
How is the issue going on your side? Do you mean that the "Next Run Date"
column shows "(Date and Time are not available)" value? Even for a newly
created job although it has a valid schedule?
1. Please check again to see if the SQL Server Agent Service is started and
the jobs are enabled.
Right click on one of the jobs -> properties -> schedules tab -> make sure
there is a schedule set up for this job.
If so -> choose the schedule -> edit -> make sure the schedule is enabled
(checkbox is checked)
If not, check it and click ok and apply.
Now, right click on "Jobs" under SQL Server Agent and choose refresh. Check
if the next run date column shows any values. If so, please check each and
every single job to check if the schedule has been enabled.
2. If it still does not help, check in the MSDB database to see if you can
see the date but not in the GUI? Try the following SQL statement.
Select schedule_id, name, next_run_date, next_run_time from sysjobschedules
3. If it also does not show up in MSDB database, please try to run DBCC
CHECKDB against the MSDB database. Also, please enable and provide the SQL
Server Agent log.
For more information regarding SQL Server Agent log, please see the
following article on SQL Server Books Online.
Topic: "SQL Server Agent Properties (General Tab)"
4. If the date shows correctly in the MSDB database, check if an end date
has been specified for the job schedule and if it is already past the end
date?
5. Please run sp_help_job against the jobs to see if the next_run_date and
next_run_time shows correctly?
sp_help_job @.job_name = '<job_name>'
I am looking forward to hearing from you soon.
Regards,
Michael Shao
Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security
This posting is provided "as is" with no warranties and confers no rights.

Next run date!

Hi,
Yesterday I changed a motherboard on my SQL server 7.0.
Today I noticed that jobs has not been started last night,
and I noticed that date is wrong on this machine,so I did
set the date and time and rebooted the machine, however
still can not see the next run date on scheduled job, even
if I create a new job, I can not see that. Does anyone
know how to fix this?
Thanks in advance-RobHi Rob,
I learned the Job of SQL Server 7.0 did not start after changing the
motherboard and you cannot see the value of "Next run date" property of the
job. As far as I know, after changing the motherboard of the machine,
generally, the old operation system will crash. Do you mean your old
operation system is still available and there is not any problem?
According to your description, it seems all the jobs on your problematic
machine have this problem. If I have misunderstood, please feel free to let
me know. Have you started the SQL Server agent? If the problem still
occurred after starting SQL Server agent, what's the message in the Next
Run Date field of the problematic job?
I am looking forward to hearing from you soon.
Regards,
Michael Shao
Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security
This posting is provided "as is" with no warranties and confers no rights.|||Hi Rob,
How is the issue going on your side? Do you mean that the "Next Run Date"
column shows "(Date and Time are not available)" value? Even for a newly
created job although it has a valid schedule?
1. Please check again to see if the SQL Server Agent Service is started and
the jobs are enabled.
Right click on one of the jobs -> properties -> schedules tab -> make sure
there is a schedule set up for this job.
If so -> choose the schedule -> edit -> make sure the schedule is enabled
(checkbox is checked)
If not, check it and click ok and apply.
Now, right click on "Jobs" under SQL Server Agent and choose refresh. Check
if the next run date column shows any values. If so, please check each and
every single job to check if the schedule has been enabled.
2. If it still does not help, check in the MSDB database to see if you can
see the date but not in the GUI? Try the following SQL statement.
Select schedule_id, name, next_run_date, next_run_time from sysjobschedules
3. If it also does not show up in MSDB database, please try to run DBCC
CHECKDB against the MSDB database. Also, please enable and provide the SQL
Server Agent log.
For more information regarding SQL Server Agent log, please see the
following article on SQL Server Books Online.
Topic: "SQL Server Agent Properties (General Tab)"
4. If the date shows correctly in the MSDB database, check if an end date
has been specified for the job schedule and if it is already past the end
date?
5. Please run sp_help_job against the jobs to see if the next_run_date and
next_run_time shows correctly?
sp_help_job @.job_name = '<job_name>'
I am looking forward to hearing from you soon.
Regards,
Michael Shao
Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security
This posting is provided "as is" with no warranties and confers no rights.