Is it good practice to keep all stored procedures in separate database which has no data and all tables with real data in separate database(s)? Main reason: to be able to upgrade stored procedures with simple restore which does not affect the production data. Second (optional) reason: 2+ databases can be processed by the same set of stored procedures.
closed as primarily opinion-based by mustaccio, SqlWorldWide, Tom V, Erik Darling, RDFozz Feb 8 '18 at 16:15
Many good questions generate some degree of opinion based on expert experience, but answers to this question will tend to be almost entirely based on opinions, rather than facts, references, or specific expertise. If this question can be reworded to fit the rules in the help center, please edit the question.
I have never seen that approach used. If you are keeping your database schema in a source control system, then you can generate deployment scripts. Such tools can compare previous versions of your schema and deploy the changes. SQL Server Data Tools is available in Visual Studio.