Dear Wendy,
Thank you so much for the quick and helpful response! This explains exactly why the Data Exfiltration rule wasn't triggering-we never considered that stored procedures in MS-SQL could return a negative "Records Affected" value (-1).
Your insight has been a huge help in troubleshooting the issue, and I'll dive into the documentation right away to understand all the scenarios that cause negative numbers.
Really appreciate your support on this!
------------------------------
Bing Fang
------------------------------
Original Message:
Sent: Wed December 03, 2025 10:08 AM
From: Wendy Zemba
Subject: "Records affected" value on full sql dashboard is not correct.
Hi Bing,
There are certain conditions where negative numbers are thrown. For example: using a stored procedure in MS-SQL sets produces a Records Affected as -1.
Here's a link to the documentation that explains various scenarios that will produce negative numbers: https://www.ibm.com/docs/en/gdp/12.x?topic=system-configuring-inspection-engines#task_b2n_lvv_m2c__how_log_records_affected_works
------------------------------
Wendy Zemba
Sr. Consultant, Data Protection
Converge Technology Solutions
wendy.zemba@convergetp.com
Need help with your Guardium deployment? Contact me directly to discuss engagement opportunities. Currently serving North America.
------------------------------