I have a weekly database maintenance job which amongst other things rebuilds all the indexes, this job takes about 8 hours & so if it is still running during 'up' time it has a major impact on the users.
I'd like to be able to quit this job if it overruns or at least be able to give users an estimate of when the system will be available so I have two questions:
1/ If I kill this job off whilst it is indexing what impact will this have on the database ( what state will the indexes be in afterwards).
2/ Is there any way of monitoring how far the job has progressed( beyond the start& end times the databases in sqlmaintplan_history)
I'd like to be able to quit this job if it overruns or at least be able to give users an estimate of when the system will be available so I have two questions:
1/ If I kill this job off whilst it is indexing what impact will this have on the database ( what state will the indexes be in afterwards).
2/ Is there any way of monitoring how far the job has progressed( beyond the start& end times the databases in sqlmaintplan_history)