Whereas SONAR-487 was dedicated to improve Sonar database use on class measures, this new improvement focus on other kind of resources (projects, modules, packages).

Here is a tip to improve Sonar database use by reducing the number of rows in project_measures table for this king of resources :

• For each couple "resource/rule" there are currently 6 measures whereas two are really used (Violations on mandatory rules and Violations on optional rules)
  o Stop calculating the others four measures (Coding rules compliance, Optional coding rules compliance, Coding rules compliance, including optional rules, Violations, including optional rules)
  o For the two remaining measures, they should be filled only when the value is not 0

Those improvements should reduce the number of measures by resources (projects, module, package) from 700 to less than 100.

With this new improvement, I think we can divide the number of rows in project measures by 2.