• State Not Answered
  • Locked Locked
  • Replies 3 replies
  • Subscribers 96 subscribers
  • Views 3300 views
  • Users 0 members are here
Options
Related
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Is there a way to completely turn off the nightly maintenance jobs (shrinking, indexing jobs etc.) in v6.1.4?

xd
over 7 years ago

A customer upgrading 6.1.4 to 7.1.2, and asked the question "Is there a way to completely turn off the nightly maintenance job in v6.1.4?"

Thank you for your suggestions!

Parents
  • 0 over 7 years ago

    Hello,

    We suggest to never turn off the maintenance jobs as they are there for a reason.

    What we often see is that these "tasks" become a nuisance when the overall configuration is incomplete or incorrect with regards to archival.  For example, if the "history" tables grow too large then the "shrinking" jobs may run longer than desired.  Thus it's very, very important to configure the archival procedure from day one and avoid this problem later on.

    Please refer to the Configuration Guide for more information on Archiving Procedure Setup.

    Specifically, are the retention periods too long?  Is there a History Database in place to store archived data?  How large are the history tables, e.g. jobhistory?

    Instead of addressing the symptoms, it may be worthwhile to investigate the underlying cause.

    The same is true for indexing jobs.  If the tables are large, or there is fragmentation, if the SQL server is performing poorly, then these tasks will run long.

    Trevor

Reply
  • 0 over 7 years ago

    Hello,

    We suggest to never turn off the maintenance jobs as they are there for a reason.

    What we often see is that these "tasks" become a nuisance when the overall configuration is incomplete or incorrect with regards to archival.  For example, if the "history" tables grow too large then the "shrinking" jobs may run longer than desired.  Thus it's very, very important to configure the archival procedure from day one and avoid this problem later on.

    Please refer to the Configuration Guide for more information on Archiving Procedure Setup.

    Specifically, are the retention periods too long?  Is there a History Database in place to store archived data?  How large are the history tables, e.g. jobhistory?

    Instead of addressing the symptoms, it may be worthwhile to investigate the underlying cause.

    The same is true for indexing jobs.  If the tables are large, or there is fragmentation, if the SQL server is performing poorly, then these tasks will run long.

    Trevor

Children
No Data