Loading
search-img

DavidH asked a question.

October 23, 2020 at 1:38 PM
Should we still use the "RUN_COMPLETE_RULESET_DAY" setting?

Some years back, we were advised by Snow Support to enable the "RUN_COMPLETE_RULESET_DAY" setting. At the time I took notes:

 

...when new rules get added by Snow to the global database, certain parts of the process only happen once. However, sometimes there can be errors during this process which leave the rules in a state of limbo. These rules will look like they are installed when you view them in the SMACC, but in fact they will not be active. This situation can be resolved by "running the complete ruleset". This makes sure that all the rules have been fully imported.

 

However, a lot has changed since then and the DUJ works differently now.

 

Does anybody know if it is still advisable to run the complete ruleset every week? It makes our DUJ take a long time at weekends, and I wonder if we still need it.

 

David

  • 30 answers
  • 330 views

  • Portal User

    Hi David

     

    Yes we were advised the same, and this was something that was checked when we had our technical healthcheck with Snow earlier in the year... So I'm working on the basis that this is still required even with the improvements to the DUJ.

     

    Adam

    Expand Post

    • DavidH

      Thanks @Adam Davies​ that's good to know. Our weekend DUJ now takes over 20 hours, so I was wondering if it's really needed. The complete ruleset takes many additional hours. Following your advice we will leave it on and look for other ways to speed things up.

       

      David

  • carolai

    Hi Adam, David,

     

    It's absolutely interesting for me, that Adam still this year got the recommendation to keep this setting.

     

    I got the information this setting is not necessary anymore.

    So RUN_COMPLETE_RULESET_DAY is set to Never in our SMACC, since a longer time.

    Only RUN_EXCLUSION_RULESET_DAY is activated and set to Saturday.

     

    It seems there are different opinions even at Snow.

    Perhaps @Ester_locked Memoli(Retired)​ , @Geoffrey Macquet​ , @Alessandro Badin​ can give an official recommendation here.

    The User Guide for SLM SMACC does not have any information regarding this.

     

    Carola

    Expand Post

    • Community Manager (Flexera Software)

      Hi Carola,

      I will check with the internal team and will let you know.

       

      Cheers,

      Ester

      Expand Post

    • Portal User

      Thanks Carola - will be very interested to hear if there is a real official stance on this... :-)

  • Laim McKenzie

    We're having a similar issue at the moment, the DUJ on one of our platforms takes around 17 hours to finish but on a Friday (complete ruleset), it runs over so much that I had to cancel it this morning!

     

    This has only started happening in 9.7.X as well, so would be interesting to know if we still need it enabled or not because it's hammering the platform (that is well over spec)

    • DavidH

      Thanks Laim, that's good to know. We have been watching our DUJ times consistently creeping upwards over the past few months. The weekend DUJ really does hammer the system (to the point where we get service failures every weekend). Our environment is over spec too. Hopefully we will all get this sorted :-)

  • SamuelBaughan

    @Joseph Powell​ recommended checking the size of the table tblSoftware in SLM which we did. Our is quite massive (15M+).

    How many records do you see in yours? He says the issue is likely in this ever growing table.

  • Alessandro Badin (Flexera Software)

    Hi all,

    I hope I can help:

    (TLDR: don't be lazy and read this, it will take less time than running a DUJ with RUN_COMPLETE_RULESET)

     

    The RUN_COMPLETE_RULESET setting is a potential source of confusion in big implementations as well as in smaller ones (even though the bigger the database, the bigger the impact, clearly).

     

    RUN_COMPLETE_RULESET is a useful setting to recover the reliability in the recognized application data if something went really wrong in a previous DUJ during the software recognition steps (*).

    Since it has such a high cost, however, it should not be used lightly, and the DUJ should normally run deltas only. Running delta DUJs only is the default setting.

     

    If the DUJ run time allows, it’s not a bad idea to run it every week, thus creating a weekly baseline. Think about an incremental backup policy: one would generally want to take a full backup every now and then.

    Enabling RUN_COMPLETE_RULESET is not a requirement anyway, and if everything goes smoothly always, one doesn't really need it. Just like a full database backup.

     

    But as usual, there is no silver bullet, and whether it is good to use this option or not (and when), is something that should be evaluated on a case-by-case (or installation-by-installation, or customer-by-customer) basis.

     

    (*) cases when something went really wrong with the DUJ during the software recognition steps might include (but are not limited to): killing the DUJ before it has finished, restarting SQL Server, running out of disk space, and so on...

     

    I hope this helps shedding some light.

    Expand Post

    • Alessandro Badin (Flexera Software)

      PS: if all goes according to plan, we will soon get rid of RUN_COMPLETE_RULESET.

      (it is too early to share more details, and this is a teaser)

10 of 30

+1.800.374.4353
CONTACT SALES SUPPORT HUB FLEXERA REVENERA
© 2026 Flexera. All rights reserved.
Privacy policy Terms and conditions Revenera Community Help
Loading
Feed Detail