Activity overview
Latest activity by rogindare
It looks like SQL Code Guard is correctly processing your /include:ME003 parameter based on the log, but the fact that the XML still contains all rules usually points to how SQL Code Guard handles filtering at different stages. From what I’ve seen, the /include switch limits which rules are executed during analysis, but the XML formatter may still output the entire rule set unless the tool explicitly filters the export stage. In older versions especially, the XML output isn’t filtered the same way the analysis engine is — so even though only ME003 is triggered, the report template still lists all available rules. A couple of things worth checking: Verify whether only ME003 has findings Even if the XML lists all rules, check whether only ME003 has actual entries. Often the others are simply present as empty nodes. Try using /include together with /exclude Some users reported that forcing exclusions for “all other rules” helps the export formatter produce a restricted XML. Ensure you’re using the latest CLI version Earlier builds had inconsistent behavior between command-line filtering and export formatting. Check if the XML schema includes a “ruleset” section In some cases, the XML includes rule metadata regardless of what was analyzed, because it’s part of the report structure rather than the results. If the analysis time and log indicate that only ME003 ran, then Code Guard is honoring the include filter — the XML output may just not be designed to trim unused rules. If you need a minimal XML, you might have to post-process it or use a different export mode if available. / comments
It looks like SQL Code Guard is correctly processing your /include:ME003 parameter based on the log, but the fact that the XML still contains all rules usually points to how SQL Code Guard handles ...