include/exclude not working

• 

  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?

  tulla01 March 05, 2025 20:10

  - 0 +
• 

  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!

  Saim01 March 15, 2025 11:09

  - 0 +
• 

  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.

  Hawke john May 22, 2025 07:00

  - 0 +
• 

  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.

  kinseysmith June 19, 2025 10:34

  - 0 +
• 

  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.

  jeemsith June 20, 2025 10:05

  - 0 +
• 

  If your include or exclude directive isn't working, double-check the syntax and path format—issues often arise from incorrect relative paths or missing wildcards. Also, ensure there are no conflicting rules or overrides elsewhere in your configuration.Blooket join

  MARKERM August 02, 2025 07:44

  - 0 +
• 
  • Connect to the specified server and database (details hidden with **).
  • Analyze the code using only rule ME003.
  • Output the results to an XML file.
  • Log the process to a .log file.

  📄 Log Interpretation

  • License terms acknowledged.
  • Successfully connected to the server and database.
  • Rule ME003 was selected for inclusion.
  • No rules were excluded.
  • Objects were loaded in under a second.
  • The analysis process ran for about 4.5 seconds.
  • No errors or warnings were reported.
  • Analysis completed and process finished successfully.

  ✅ Conclusion

  Everything appears to be working as intended! If you're not seeing output in the XML or expected results, you may want to:

  • Double-check that the rule ME003 actually applies to any object in your database.
  • Ensure the output path is valid and not blocked by permissions.

  If you want help parsing the .xml output or adding more rules, feel free to ask!

  Also, if you’re into tools and customizations, take a break and check out some cool game

  gtasanandreas August 04, 2025 07:59

  - 0 +
• 

  Hi Tim,

  It looks like SQL Code Guard is ignoring the /include:ME003 filter and still running all rules. This is a known quirk with some versions where the /include flag doesn't override the full ruleset as expected.

  To narrow down to only ME003, try both:

  /include:ME003 /exclude:ALL
  

  Then, explicitly re-include ME003, which forces the tool to bypass the default rule set. Alternatively, create a custom rule set XML with just ME003 and point to it using /ruleset:yourrules.xml.

  Also, make sure you're using the latest version—some older builds have bugs with include/exclude logic. If the problem still persists, contacting support or checking for patches may help.

   

  jimmycorta August 06, 2025 17:51

  - 0 +
• 

  Interesting thread—filter logic bugs can be frustrating. Reminds me of how older Shadow Fight 2 versions handled things more predictably, with unlocked features and fewer issues. Simpler setups often mean smoother performance.

  Adam August 06, 2025 22:34

  - 0 +
• 

  Based on the command and log you’ve shared, it looks like SQL Code Guard is launching correctly and processing the specified inputs. Here's a breakdown and interpretation of what you're seeing, along with what might come next or what to check extreme car driving simulator  mod apk 

  ✅ Command Breakdown:

  bash

  CopyEdit

  SqlCodeGuard30.Cmd.exe /server:** /database:** /outfile:**.xml /include:ME003 /log:**.log 

  • /server:** – You're connecting to the SQL Server instance (** is masked for privacy).
  • /database:** – Targeting a specific database.
  • /outfile:**.xml – You want the output (violations, issues) written to an XML file.
  • /include:ME003 – You're only including rule ME003 (for example, this might be a rule like "Avoid SELECT *", depending on your rule set).
  •  

  extremecar August 07, 2025 07:30

  - 0 +
• 

  his looks like a known issue where the /include flag in SQL Code Guard doesn’t override the default rule set properly. Even though the log confirms ME003 is selected, it still runs the full set.

  ✅ Workaround that usually works:
  Use both /include:ME003 and /exclude:ALL, like this:

  bash

  CopyEdit

  SqlCodeGuard30.Cmd.exe ... /exclude:ALL /include:ME003 ...

  This forces the tool to wipe out the default rules first, then re-apply only ME003.

  Alternatively, define a custom ruleset XML with only ME003 enabled, and point to it with:

  bash

  CopyEdit

  /ruleset:custom_rules.xml

  Also, double-check that you're using the latest version of the tool—older builds have bugs with filter logic that were fixed later on.

   

  zainbhoohn078 August 07, 2025 18:52

  - 0 +
• 

  If your include or exclude directive isn’t working, review the syntax and path format carefully, as errors often come from incorrect relative paths or missing wildcards. Also,Mobilecric PAK vs IND make sure no other rules or overrides in your configuration are causing conflicts.

  Whelibeiren August 20, 2025 09:55

  - 0 +
• 

  tim_vl, this is actually a known quirk with certain versions of SQL Code Guard. Even when you specify /include:ME003, the tool sometimes still processes the entire default ruleset. A workaround that usually fixes it is running: SqlCodeGuard30.Cmd.exe ... /exclude:ALL /include:ME003 ... That clears out the default rules first, then forces only ME003 to run. Another approach is to create a custom ruleset.xml with just ME003 enabled and reference it using /ruleset. Also make sure you’re on the latest build—some of the older releases had bugs with include/exclude logic. On a side note, if you’re into tweaking tools and getting the most out of software, you might find Spotify Mod interesting—it’s similar in the sense that it unlocks extra functionality compared to the default app.

  scott09 August 22, 2025 04:34

  - 0 +

Add comment

Please sign in to leave a comment.