On 4/25/06, Ruslan Sivak <rsivak@istandfor.com> wrote:
>
> Is there some utility somewhere which allows MS SQL Server's stored
> procedures to be kept in subversion?
The stored procedures are kept within the database itself. What you
can do (and I would do, if the need was large enough), is have the
developers/DBAs write the SPs outside SQL Server, save to files, and
manage those files via SVN. It does require some discipline, but if
you separate by role the individuals installing the SPs from those
writing them, it can be done. You can do your table & view definitions
this way as well, and track your user accounts/roles/permissions as
well.
Example: For my system, I'm required to produce a monthly report of
any changes (code and DB table definitions) to the system. The code
changes are easy. For the database, we don't make table changes via
SQL (we use the GUI), and we don't have stored procedures. I go into
Enterprise Manager and script each object in the database, and check
the resulting files into SVN. Then the diff from one month to the
next tells me what, if anything, has changed. I used the procedure
described here ->
http://www.databasejournal.com/features/mssql/article.php/3389411 to
create the SQL scripts; just make sure you select "one file per
object" to make diffs easier.
It's kind of backwards from your question, but should hopefully give
you an idea.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Tue Apr 25 17:58:25 2006