Best practice tips for maintaining an Innovator installation!

Hi Community,

I want to use this thread to collect maintenance tips regarding Innovator. What is your experience? What do you think is worth to do on a regular basis to ensure long life stability and performance? See it as preventive health check for our Innovator platform, so we can identify upcoming problems before they occur.

Here are some examples. A lot of these task can already be automated:

  • Check if the latest service packs are worth an update
  • Check for active/inactive users
  • Check if file vault has still enough space
  • Check for failed conversion tasks

Questions:

  • What would would you recommend to check on a regular basis?
  • How do you monitor Innovator, e.g. to find performance consuming events?

Looking forward to hear your ideas! My shown list only shows a small part of my current list. I will share my experience if you share yours (that´s the deal  )

Best regards
Angela

Parents
  • Hi Angela,

    Interesting topic. Here is my list excluding things that you have already covered

    Regular Checks:

    1. Weekly or bi weekly a DBA runs profiler on ARAS database to identify possible ways to improve performance. DBA does data base tuning, re indexing if required.

    2. As user base increases so is the data and database size. So to improve performance few data heavy reports can be converted from AML to SQL to take advantage of SQL views as a mean of improving performance.

    For performance improvement:

    1. Normally as functionality is built with multiple sprints there is scope for optimization since many times on same event we create multiple methods during different sprints. So we take up short performance improvement project after delivery of particular module, where idea is

      1.1 Aggregate functions on same events

      1.2 Push code to server side method from client side method as much as possible

      1.3 Follow ARAS tips on performance improvement like using attributes select, doGetItem etc ..

Reply
  • Hi Angela,

    Interesting topic. Here is my list excluding things that you have already covered

    Regular Checks:

    1. Weekly or bi weekly a DBA runs profiler on ARAS database to identify possible ways to improve performance. DBA does data base tuning, re indexing if required.

    2. As user base increases so is the data and database size. So to improve performance few data heavy reports can be converted from AML to SQL to take advantage of SQL views as a mean of improving performance.

    For performance improvement:

    1. Normally as functionality is built with multiple sprints there is scope for optimization since many times on same event we create multiple methods during different sprints. So we take up short performance improvement project after delivery of particular module, where idea is

      1.1 Aggregate functions on same events

      1.2 Push code to server side method from client side method as much as possible

      1.3 Follow ARAS tips on performance improvement like using attributes select, doGetItem etc ..

Children
No Data