What is the best way to version control my SQL server stored procedures? [closed]

version-control svn sql-server visual-studio stored-procedures

What is the best way to version control my database objects? I'm using Visual studio 2005/2008 and SQL server 2005. I would prefer a solution which can be used with SVN.


Solution 1:

Same as your other code, add a "Database project" to your application solution and keep the sql files used to build the database objects in there. Use the same version control for those code files as you do for the application.

Solution 2:

Look at the tools offered by RedGate. They specifically deal with backup / restore / comparison cases for SQL Server objects including SP's. Alternately I am not sure but I think that Visual Studio allows you to check sp's into a repository. Havent tried that myself. But I can recommend RedGate tools. They have saved me a ton of trouble

Related

nm: "U" The symbol is undefined
C++ doesn't tell you the size of a dynamic array. But why?
Is there a consensus what should be documented in the classes and __init__ docstrings?
Mercurial branching and bookmarks
Finding "dead code" in a large C++ legacy application [closed]
MongoDB 'count()' is very slow. How do we refine/work around with it?
What is the difference between numpy.fft and scipy.fftpack?
optimal architecture for multitenant application on django
"The POM for ... is missing, no dependency information available" even though it exists in Maven Repository
In C++, does initializing a global variable with itself have undefined behaviour?
What is a regex "independent non-capturing group"?
Automating creating NuGet package as part of build process