Single Script Store Procedure Update

At the moment every change must be made in a different script. This is correct for most changes but for stored procedures you really don't want a different script for each change you make, mainly because it then makes if difficult to see the changes made to the sp over time.

So a change planned for the near future is to allow one directory in the 'structure' that contains all sp scripts. Those scripts are a direct reflection of what is in source control, any changes to the file will cause the script to be run against the database (DBUpdater will still keep track of the fact that it was run and against which build). This way there is only one file that contains the script for each sp and you will therefore be able to easily get a full change history.

Last edited May 25, 2008 at 3:07 PM by wallism, version 1

Comments

No comments yet.