Comments
5 comments
-
It looks like SQL Code Guard didn't filter out the rules correctly. Have you tried explicitly specifying exclusions using
/exclude:ME001,ME002
? Also, does the log confirm only ME003 was applied? -
You’re right to check the exclusions explicitly. I’ll try using
/exclude:ME001,ME002
and review the log to confirm if only ME003 was applied. If the issue persists, I’ll investigate further or adjust the configuration. Thanks for the suggestion! -
It seems like SqlCodeGuard isn't properly filtering the output for rule ME003, even though it's specified in the command. Double-check that the rule code is correct and ensure the tool is handling the
/include
flag properly. If the issue continues, consider checking the documentation or contacting support for help. -
It looks like SQL Code Guard isn't correctly filtering the output—even though ME003 is specified using the
/include
flag, other rules may still be applied. Try explicitly excluding unwanted rules using/exclude:ME001,ME002
, and then check the logs to confirm whether only ME003 was enforced. If the issue persists, it might be worth revisiting the configuration or consulting the official documentation or support for more clarity. -
It seems that SQL Code Guard isn't limiting the output strictly to ME003, even though the /include:ME003 flag is used. To ensure only ME003 is enforced, try explicitly excluding other rules using /exclude:ME001,ME002. After that, review the app logs to verify if only ME003 is active. If the issue still occurs, it might be a good idea to recheck the tool’s configuration or refer to the official documentation or support for a more precise fix.
Add comment
Please sign in to leave a comment.
I run: R:\Tim van Loosbroek\code guard>SqlCodeGuard30.Cmd.exe /server:** /database:** /outfile:**.xml /include:ME003 /log:**.log
The log:
But the XML output files contains all rules?