From what I gathered one of the biggest problems of stored procedures is that they do not play well at all with source control and associated tooling such as code review.
Ok. I did not know that. As I said this is what I have gathered from what I have read around as a common complaint. Out of curiosity, what is the testing-deployment cycle of stored procedures in source control? How do you assure yourself that the database uses a procedure coming from a specific commit?
How do you assure yourself that your non-database code uses code coming from a specific commit?
In general, you have a deployment procedure that overwrites all the old code with all-new code, and from there on out you trust, right? Why not use the same approach?
I then asked a colleague to review it. This also worked.