On Fri, 2 Dec 2022 at 02:24, raf <raf@xxxxxxx> wrote: > Same here. Accessing the loaded stored procedure source > is how I audit the state of stored procedures in the > database against the code in the code repository. Exactly. If our software is audited, how can I reliably prove to auditor that the running version of the procedure has not been tampered with either by customer, rogue developer or some malicious party? Suggested solution "store the text in user table" does not work, because it requires following a process. And the process overriding changes are those we are interested in. I'm not so much concerned about whether the stored procedure text compiles anymore (because of object name changes etc.) I just really would like to have the exact source code stored with the database. So if release management goes horribly wrong, there is at least the possibility to compare procedure text manually. Pasi
