I'm cool with it not being a stored procedure.  But we've traditionally used EF Migrations to update the database schema and objects and we're not doing that here. We need an approach for executing scripts like this that is better than interactively running SQL scripts as part of the deployment script.  (I've been down that road, and it always leads to pain ;-)).

I don't know what I want to see here, but if we're not using EF migrations for this, then we need an alternative.