Functions called in stored procedures are not captured by Guardium for Microsoft MSSQL server

This is expected due to the nature of stored procedures. The content of the procedure is defined when the procedure is created, but not actually executed each time the stored procedure runs. Hence in Guardium report you will see the execute procedure command but not the commands that are within that procedure.


Due to nature of how stored procedures are run and stored on the database when stored procedure is executed, we can not see the SQL contained within when they are executed. Executing a stored procedure is not the same as running all the SQL within the stored procedure.


Stored procedures differ from ordinary SQL statements and from batches of SQL statements in that they are precompiled. The first time you run a procedure, Adaptive Server's query processor analyzes it and prepares an execution plan that is ultimately stored in a system table. Subsequently, the procedure is executed according to the stored plan. Since most of the query processing work has already been performed, stored procedures execute almost instantly.