URGENT : What happens if MAX Rows per job reaches

Question

URGENT : What happens if MAX Rows per job reaches

mybid2003

SSCertifiable

Points: 6620
More actions
August 22, 2003 at 7:54 am

#159581

Hi All,
What happens if MAX Rows per job reaches in SQL Server Agent properties or SQL Server Database Maintenance Plan Properties? Are both these same?!
Thanks in Advance.
.

Viewing 10 posts - 1 through 9 (of 9 total)

You must be logged in to reply to this topic. Login to reply

Allen Cui-55137 SSC Guru Points: 51650 More actions · Answer 1

The old history recods will be deleted. SQL Server Agent uses 'sysjobhistory' to log history information but the maintenance plan keeps the history in 'sysdbmaintplan_history' table for that plan. The job generated by maintenance plan will record history information in 'sysjobhistory' once the job was executed.

mybid2003 SSCertifiable Points: 6620 More actions · Answer 2

Thanks Allen. But.... here is my problem.

I am having one strange problem, my jobs are not executing in fixed intervals.

Couple of days back we had a situation that the jobs were hung with a status "performing completion actions". We had an emergency reboot of the server, then everything seems working fine for 1.5 days.

But since yesterday early morning, the transaction log backup jobs (hourly - 24 hrs) are not running except for 2 databases (which are very new databases). I started these jobs manually. Then from the next hour onwards, they went fine, until this morning. Again they stopped couple of hrs back (not at the same time). I am manually starting these jobs.

I am going crazy...since this is very critical server for us.

PLEASE HELP.

.

Allen Cui-55137 SSC Guru Points: 51650 More actions · Answer 3

quote:
Couple of days back we had a situation that the jobs were hung with a status "performing completion actions". We had an emergency reboot of the server, then everything seems working fine for 1.5 days.

What kind of jobs? Are they created by maintenance plans?

mybid2003 SSCertifiable Points: 6620 More actions · Answer 4

Yes. Most of them. The jobs which are running while other jobs are not running also created by mentenance jobs.

Apart from that I have non-maintenance plan jobs whihc are running fine now.

NOTE: I am NOT delating old records from MSDB now. Do I need to get rid off these old records?!

.

Allen Cui-55137 SSC Guru Points: 51650 More actions · Answer 5

I would go to server Task Manager to see any SQL Server Maintenance processes (sqlmaint.exe) that could be hung. Kill them and try your jobs.

Which version of SQL Server and Service Pack?

mybid2003 SSCertifiable Points: 6620 More actions · Answer 6

SQL Server 2000 SP3 running on Windows 2000 Server SP2.

.

Allen Cui-55137 SSC Guru Points: 51650 More actions · Answer 7

You can also have detailed Maintenance Plan information written to a file. To have detailed Maintenance Plan information written to a file, use these steps: In SQL Server Enterprise Manager, navigate to the Database Maintenance Plans. Select and then double-click the plan you want. Click the Reporting tab. In the Reporting dialog box, you can choose to write a report to a text file in a specified directory. The report contains details of the steps executed by the maintenance plan, and includes any error information.

Edited by - allen_cui on 08/22/2003 1:36:32 PM

mybid2003 SSCertifiable Points: 6620 More actions · Answer 8

Allen,

Since the begining we have implemented this way. But since the Agent never ran to show the error in the report. Thats the reason I could not see anything.

Any thoughts!!!

.

mybid2003 SSCertifiable Points: 6620 More actions · Answer 9

I got this solved.

I have reduced the MAX rows, in the database Maintenance plan, then manually ran the job to get it cleared by the system itself.

After this job started running by itself. Let see if it still keeps running.

.