Just because you got yourself into the mess, doesn't mean that database schema is suddenly bad. Data definition language (DDL) is a declarative and well thought-out DSL that can guarantee the business logic to a certain extent, at a very very low cost.

On the other hand, stored proc is a relic of the integration database [1], and is definitely less flexible compared to using your programming language of choice.

Instead of jumping from 2000 tables / 45000 stored procs straight to "schema in code", perhaps a saner tables design with no stored proc is the better way to go?

[1] http://www.martinfowler.com/bliki/IntegrationDatabase.html