Mark Forums Read

Job Agent

Go Back

microsoft.public.sqlserver.tools microsoft.public.sqlserver.tools

Reply

Page 2 of 2

2

#11

Old

Ola Hallengren

Posts: n/a

RE: Job Agent - 05-15-2008 , 11:21 AM

You could create a monitoring SQL Server Agent job that checks for jobs that
has been running longer than a defined time.

Another thing that you could do is to use the SET LOCK_TIMEOUT statement in
your rebuild / reorganize jobs. This means that if for example an index
rebuild command has been waiting for locks for more than a defined time, then
the command is aborted. It could then continue to the next index. I have made
an index optimization stored procedure that is using this design.
http://blog.ola.hallengren.com/blog/...1/3440068.html

Ola Hallengren
http://ola.hallengren.com

"Jay Bukstein" wrote:

Quote:

I have maintenance job the runs a Reorganize/rebuild indexes. It normallly
takes 90minutes to do all DB's but on occassion it gets hung up. The job
starts at 10pm, is there a way to check if it's still running at 12:00pm and
if it is notify on of the DBA's?

Reply With Quote

#12

Old

Ola Hallengren

Posts: n/a

RE: Job Agent - 05-15-2008 , 11:21 AM

You could create a monitoring SQL Server Agent job that checks for jobs that
has been running longer than a defined time.

Another thing that you could do is to use the SET LOCK_TIMEOUT statement in
your rebuild / reorganize jobs. This means that if for example an index
rebuild command has been waiting for locks for more than a defined time, then
the command is aborted. It could then continue to the next index. I have made
an index optimization stored procedure that is using this design.
http://blog.ola.hallengren.com/blog/...1/3440068.html

Ola Hallengren
http://ola.hallengren.com

"Jay Bukstein" wrote:

Quote:

I have maintenance job the runs a Reorganize/rebuild indexes. It normallly
takes 90minutes to do all DB's but on occassion it gets hung up. The job
starts at 10pm, is there a way to check if it's still running at 12:00pm and
if it is notify on of the DBA's?

Reply With Quote

#13

Old

Ola Hallengren

Posts: n/a

RE: Job Agent - 05-15-2008 , 11:21 AM

You could create a monitoring SQL Server Agent job that checks for jobs that
has been running longer than a defined time.

Another thing that you could do is to use the SET LOCK_TIMEOUT statement in
your rebuild / reorganize jobs. This means that if for example an index
rebuild command has been waiting for locks for more than a defined time, then
the command is aborted. It could then continue to the next index. I have made
an index optimization stored procedure that is using this design.
http://blog.ola.hallengren.com/blog/...1/3440068.html

Ola Hallengren
http://ola.hallengren.com

"Jay Bukstein" wrote:

Quote:

I have maintenance job the runs a Reorganize/rebuild indexes. It normallly
takes 90minutes to do all DB's but on occassion it gets hung up. The job
starts at 10pm, is there a way to check if it's still running at 12:00pm and
if it is notify on of the DBA's?

Reply With Quote

#14

Old

Ola Hallengren

Posts: n/a

RE: Job Agent - 05-15-2008 , 11:21 AM

You could create a monitoring SQL Server Agent job that checks for jobs that
has been running longer than a defined time.

Another thing that you could do is to use the SET LOCK_TIMEOUT statement in
your rebuild / reorganize jobs. This means that if for example an index
rebuild command has been waiting for locks for more than a defined time, then
the command is aborted. It could then continue to the next index. I have made
an index optimization stored procedure that is using this design.
http://blog.ola.hallengren.com/blog/...1/3440068.html

Ola Hallengren
http://ola.hallengren.com

"Jay Bukstein" wrote:

Quote:

I have maintenance job the runs a Reorganize/rebuild indexes. It normallly
takes 90minutes to do all DB's but on occassion it gets hung up. The job
starts at 10pm, is there a way to check if it's still running at 12:00pm and
if it is notify on of the DBA's?

Reply With Quote

#15

Old

Ola Hallengren

Posts: n/a

RE: Job Agent - 05-15-2008 , 11:21 AM

You could create a monitoring SQL Server Agent job that checks for jobs that
has been running longer than a defined time.

Another thing that you could do is to use the SET LOCK_TIMEOUT statement in
your rebuild / reorganize jobs. This means that if for example an index
rebuild command has been waiting for locks for more than a defined time, then
the command is aborted. It could then continue to the next index. I have made
an index optimization stored procedure that is using this design.
http://blog.ola.hallengren.com/blog/...1/3440068.html

Ola Hallengren
http://ola.hallengren.com

"Jay Bukstein" wrote:

Quote:

I have maintenance job the runs a Reorganize/rebuild indexes. It normallly
takes 90minutes to do all DB's but on occassion it gets hung up. The job
starts at 10pm, is there a way to check if it's still running at 12:00pm and
if it is notify on of the DBA's?

Reply With Quote

#16

Old

Ola Hallengren

Posts: n/a

RE: Job Agent - 05-15-2008 , 11:21 AM

You could create a monitoring SQL Server Agent job that checks for jobs that
has been running longer than a defined time.

Another thing that you could do is to use the SET LOCK_TIMEOUT statement in
your rebuild / reorganize jobs. This means that if for example an index
rebuild command has been waiting for locks for more than a defined time, then
the command is aborted. It could then continue to the next index. I have made
an index optimization stored procedure that is using this design.
http://blog.ola.hallengren.com/blog/...1/3440068.html

Ola Hallengren
http://ola.hallengren.com

"Jay Bukstein" wrote:

Quote:

I have maintenance job the runs a Reorganize/rebuild indexes. It normallly
takes 90minutes to do all DB's but on occassion it gets hung up. The job
starts at 10pm, is there a way to check if it's still running at 12:00pm and
if it is notify on of the DBA's?

Reply With Quote

#17

Old

Ola Hallengren

Posts: n/a

RE: Job Agent - 05-15-2008 , 11:21 AM

You could create a monitoring SQL Server Agent job that checks for jobs that
has been running longer than a defined time.

Another thing that you could do is to use the SET LOCK_TIMEOUT statement in
your rebuild / reorganize jobs. This means that if for example an index
rebuild command has been waiting for locks for more than a defined time, then
the command is aborted. It could then continue to the next index. I have made
an index optimization stored procedure that is using this design.
http://blog.ola.hallengren.com/blog/...1/3440068.html

Ola Hallengren
http://ola.hallengren.com

"Jay Bukstein" wrote:

Quote:

I have maintenance job the runs a Reorganize/rebuild indexes. It normallly
takes 90minutes to do all DB's but on occassion it gets hung up. The job
starts at 10pm, is there a way to check if it's still running at 12:00pm and
if it is notify on of the DBA's?

Reply With Quote

#18

Old

Ola Hallengren

Posts: n/a

RE: Job Agent - 05-15-2008 , 11:21 AM

You could create a monitoring SQL Server Agent job that checks for jobs that
has been running longer than a defined time.

Another thing that you could do is to use the SET LOCK_TIMEOUT statement in
your rebuild / reorganize jobs. This means that if for example an index
rebuild command has been waiting for locks for more than a defined time, then
the command is aborted. It could then continue to the next index. I have made
an index optimization stored procedure that is using this design.
http://blog.ola.hallengren.com/blog/...1/3440068.html

Ola Hallengren
http://ola.hallengren.com

"Jay Bukstein" wrote:

Quote:

I have maintenance job the runs a Reorganize/rebuild indexes. It normallly
takes 90minutes to do all DB's but on occassion it gets hung up. The job
starts at 10pm, is there a way to check if it's still running at 12:00pm and
if it is notify on of the DBA's?

Reply With Quote

#19

Old

Ola Hallengren

Posts: n/a

RE: Job Agent - 05-15-2008 , 11:21 AM

You could create a monitoring SQL Server Agent job that checks for jobs that
has been running longer than a defined time.

Another thing that you could do is to use the SET LOCK_TIMEOUT statement in
your rebuild / reorganize jobs. This means that if for example an index
rebuild command has been waiting for locks for more than a defined time, then
the command is aborted. It could then continue to the next index. I have made
an index optimization stored procedure that is using this design.
http://blog.ola.hallengren.com/blog/...1/3440068.html

Ola Hallengren
http://ola.hallengren.com

"Jay Bukstein" wrote:

Quote:

I have maintenance job the runs a Reorganize/rebuild indexes. It normallly
takes 90minutes to do all DB's but on occassion it gets hung up. The job
starts at 10pm, is there a way to check if it's still running at 12:00pm and
if it is notify on of the DBA's?

Reply With Quote

Reply

Page 2 of 2

2

« Previous Thread | Next Thread »

Thread Tools
Show Printable Version Email this Page
Display Modes
Linear Mode Switch to Hybrid Mode Switch to Threaded Mode

Posting Rules
You may not post new threads You may not post replies You may not post attachments You may not edit your posts vB code is On Smilies are On [IMG] code is On HTML code is Off

Powered by vBulletin Version 3.5.3
Copyright ©2000 - 2012, Jelsoft Enterprises Ltd.