It sounds like you have a database client that issues a stored procedure call (STC) to the database, you are seeing the stored procedure call in the full SQL report, but mot the statements within the stored procedure.
My experience is that this is the expected result.
The S-TAP only captures what is in the network traffic or inter-process traffic within the server. The statements within the STC are kept within the database engine and not seen by the S-TAP.
__PRESENT
------------------------------
Frank Bates
------------------------------
Original Message:
Sent: Mon March 04, 2024 02:36 AM
From: Oluwadamilola Olowojolu
Subject: Unable to see full update commands ran on the DBs via Guardium report
Hello All,
Please I haven't still been able to resolve this issue and it is delaying the close of our POC.
------------------------------
Oluwadamilola Olowojolu
Original Message:
Sent: Wed February 14, 2024 05:08 AM
From: Oluwadamilola Olowojolu
Subject: Unable to see full update commands ran on the DBs via Guardium report
Hello Everyone,
After installing the STAP agent on a windows server we have been getting logs from it but we noticed that logs generated by update commands are not showing fully in the full sql command column. The full sql command always starts from the stored procedures instead of the update verb.
Can you all assist with what could be possible causes of this and how you think we can fix this?
Thank you,
------------------------------
Oluwadamilola Olowojolu
------------------------------