In hindsight (and it was at the time) my favourite team setup was that the .NET developers would write the stored procedures (SP). They were written to a production level of quality. They were then reviewed by the SQL Server DBA who decided whether the SP was good enough having considered performance and many other aspects. If not the original SP was considered a specification and the SP rewritten. Once a SP was considered at least good enough then it was passed to the Oracle DBA who converted it for the Oracle schema.

As long as the SP was originally written to coding standards there was no shame attached. There was a feedback loop to advance the developers' skills. Also there was kudos to be attained when a SP with complex business and technical requirements was accepted as is (an occurrence that became more and more frequent).

Done as a collaborative effort with positive feedback loops not only allowed for rapid developement (the first cut SPs worked even if non-performant) but also provided an environment encouraging a higher quality of code by targetting the efforts of the most time constrained resource (or, rather, person :Whistling:).