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.
相关问题
- sql execution latency when assign to a variable
- How to know full paths to DLL's from .csproj f
- Importing NuGet references through a local project
- What is the best way to cache a table from a (SQL)
- Visual Studio 2019 - error MSB8020: The build tool
相关文章
- How to show location of errors, references to memb
- Entity Framework 4.3.1 failing to create (/open) a
- How to track MongoDB requests from a console appli
- What is the tortoisehg gui equivalent of doing “hg
- Code for inserting data into SQL Server database u
- Visual Studio Hangs on Loading UI Library
- How to use Mercurial from Visual Studio 2010?
- SSIS solution on GIT?
I'm using scriptdb.exe from http://scriptdb.codeplex.com/
And it might be usefull to use the rails way: http://code.google.com/p/migratordotnet/wiki/GettingStarted
I use SVN for all of my table/sproc/function source control.
I couldn't find anything that met my needs so I ended up writing a utility to allow me to dump the code out into a nice directory structure to use with SVN.
For those interested, the source is now available at svn://finsel.com/public/VS2005/GenerateSVNFilesForSQL2005.
Use versaplex for dumping your schema: http://code.google.com/p/versaplex/
Versaplex comes with Schemamatic, which reads database schema (tables, SPs, etc) and also data (data is dumped as CSV). I use it, with SVN and git, and it's awesome :) If you need help let me know, it's worth a try! http://github.com/eduardok/versaplex
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.