blocks|key|1522607|text|与其他代码一样，将“数据库项目”添加到应用程序解决方案中，并将用于构建数据库对象的sql文件保留在其中。对这些代码文件使用与应用程序相同的版本控制。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1522608|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

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.

blocks|key|1522715|text|看看RedGate提供的工具。它们专门处理SQL+Server对象(包括sp)的备份/恢复/比较案例。或者，我不确定，但我认为Visual+Studio允许您将sp签入存储库。我自己还没试过呢。但是我可以推荐RedGate工具。他们帮我省去了一大堆麻烦|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1522716|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

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

blocks|key|1737900|text|我将SVN用于我所有的表/sproc/function源代码控制。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1737901|我找不到任何满足我需要的东西，所以我最终编写了一个utility，允许我将代码转储到一个很好的目录结构中，以便与SVN一起使用。|offset|length|1737902|对于那些感兴趣的人，源代码现在可以在svn://finsel.com/public/VS2005/GenerateSVNFilesForSQL2005上找到。|1737903|entityMap|0|LINK|mutability|MUTABLE|url|http://www.reluctantdba.com/dbas-and-programmers/sqltools/svnforsql2005.aspx|1|http://svn//finsel.com/public/VS2005/GenerateSVNFilesForSQL2005^0|0|P|7|0|0|I|1L|1|0^^$0|@$1|2|3|4|5|6|7|R|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|S|8|@]|9|@$D|T|E|U|1|V]]|A|$]]|$1|F|3|G|5|6|7|W|8|@]|9|@$D|X|E|Y|1|Z]]|A|$]]|$1|H|3|-4|5|6|7|10|8|@]|9|@]|A|$]]]|I|$J|$5|K|L|M|A|$N|O]]|P|$5|K|L|M|A|$N|Q]]]]

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 <a href="http://www.reluctantdba.com/dbas-and-programmers/sqltools/svnforsql2005.aspx" rel="nofollow noreferrer">utility</a> 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 <a href="http://svn://finsel.com/public/VS2005/GenerateSVNFilesForSQL2005" rel="nofollow noreferrer">svn://finsel.com/public/VS2005/GenerateSVNFilesForSQL2005</a>.

blocks|key|1737853|text|我们使用Subversion，我们所要做的就是将sql代码保存在subversion项目的目录中，然后在准备好时将代码提交到存储库，并在开始处理已经存在的内容之前从存储库进行更新。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1737854|真正的诀窍是说服开发人员这样做。我们的dbas通过定期删除任何不在Subversion中的存储过程(或其他数据库对象)来做到这一点。丢了东西一次，几乎没有人会再这样做了。|1737855|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

We use Subversion and all we do is save the sql code in the directory for our subversion project and then commit the code to the repository when we are ready and update from the repository before we start working on something already in there.

The real trick is to convince developers to do that. Our dbas do that by deleting any stored proc (or other database object) that isn't in Subversion periodically. Lose stuff once and pretty much no one does it again.

blocks|key|1522778|text|我不知道有没有预装的解决方案，抱歉...|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1522779|..。但是您不能只使用一个连接到数据库的小脚本，并将所有存储过程作为文本文件保存到磁盘上吗？然后，该脚本将通过对“SVN+add”进行系统调用，将所有文本文件添加到svn存储库。|1522780|然后，您可能需要另一个脚本连接到DB，删除所有存储过程，并从磁盘加载所有存储库存储过程。每次运行"svn+up“并具有新的/更改的存储过程时，都需要运行此脚本。|1522781|我不确定这是否可以用MySQL完成，但我相当有信心MySQL会适应这一点。如果编写SVN扩展来做这件事太复杂，Capistrano支持签入/签出脚本。|offset|length|1522782|entityMap|0|LINK|mutability|MUTABLE|url|http://www.capify.org/^0|0|0|0|1J|A|0|0^^$0|@$1|2|3|4|5|6|7|R|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|S|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|T|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|U|8|@]|9|@$H|V|I|W|1|X]]|A|$]]|$1|J|3|-4|5|6|7|Y|8|@]|9|@]|A|$]]]|K|$L|$5|M|N|O|A|$P|Q]]]]

I don't know of a pre-packaged solution, sorry...

... but couldn't you just a little script that connected to the database and saved all the stored procedures to disk as text files? Then the script would add all the text files to the SVN repository by making a system call to 'svn add'. 

Then you'd probably want another script to connect to the DB, drop all stored procedures and load all the repository stored procedures from disk. This script would need to be run each time you ran "svn up" and had new/changed stored procedures. 

I'm not sure if this can be accomplished with MS SQL, but I'm fairly confident that MySQL would accommodate this. If writing SVN extensions to do this is too complicated, <a href="http://www.capify.org/" rel="nofollow noreferrer">Capistrano</a> supports checkin/checkout scripts, IIRC.

blocks|key|1737957|text|我同意，如果可能的话，你应该使用数据库项目来版本你的数据库和你的应用程序源代码。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1737958|但是，如果您处于企业场景中，则还应考虑使用工具来跟踪服务器上的更改，并对这些更改进行版本化。仅仅因为数据库项目存在并不意味着某些管理员或开发人员不能在服务器上更改这些sprocs。|1737959|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

I agree that if possible, you should use database projects to version your db along with your application source. 

However, if you are in an enterprise scenario, you should also consider using a tool to track changes on the server, and version those changes. Just because the database project exists doesn't mean some admin or developer can't change those sprocs on the server.

blocks|key|1737583|text|我们对明文进行转储，并将它们保存在我们的VCS中。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1737584|您可以编写一个备份并提交脚本来执行类似的操作。|1737585|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

We do dumps to plaintext and keep them in our VCS.

You'd be able to script a backup-and-commit to do something similar.

blocks|key|1737987|text|我正在使用来自http://scriptdb.codeplex.com/的scriptdb.exe|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|1737988|使用rails的方式可能会很有用：http://code.google.com/p/migratordotnet/wiki/GettingStarted|1737989|entityMap|0|LINK|mutability|MUTABLE|url|http://scriptdb.codeplex.com/|1|http://code.google.com/p/migratordotnet/wiki/GettingStarted^0|7|T|0|0|H|1N|1|0^^$0|@$1|2|3|4|5|6|7|P|8|@]|9|@$A|Q|B|R|1|S]]|C|$]]|$1|D|3|E|5|6|7|T|8|@]|9|@$A|U|B|V|1|W]]|C|$]]|$1|F|3|-4|5|6|7|X|8|@]|9|@]|C|$]]]|G|$H|$5|I|J|K|C|$L|M]]|N|$5|I|J|K|C|$L|O]]]]

I'm using scriptdb.exe from <a href="http://scriptdb.codeplex.com/" rel="nofollow noreferrer">http://scriptdb.codeplex.com/</a>

And it might be usefull to use the rails way: <a href="http://code.google.com/p/migratordotnet/wiki/GettingStarted" rel="nofollow noreferrer">http://code.google.com/p/migratordotnet/wiki/GettingStarted</a>

blocks|key|1738025|text|使用versaplex转储您的模式：http://code.google.com/p/versaplex/|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|1738026|Versaplex附带Schemamatic，它读取数据库模式(表、SP等)和数据(数据被转储为CSV)。我使用它，通过SVN和git，它很棒:)如果你需要帮助，请告诉我，这是值得一试的！http://github.com/eduardok/versaplex|1738027|entityMap|0|LINK|mutability|MUTABLE|url|http://code.google.com/p/versaplex/|1|http://github.com/eduardok/versaplex^0|I|Z|0|0|2M|10|1|0^^$0|@$1|2|3|4|5|6|7|P|8|@]|9|@$A|Q|B|R|1|S]]|C|$]]|$1|D|3|E|5|6|7|T|8|@]|9|@$A|U|B|V|1|W]]|C|$]]|$1|F|3|-4|5|6|7|X|8|@]|9|@]|C|$]]]|G|$H|$5|I|J|K|C|$L|M]]|N|$5|I|J|K|C|$L|O]]]]

Use versaplex for dumping your schema: <a href="http://code.google.com/p/versaplex/" rel="nofollow noreferrer">http://code.google.com/p/versaplex/</a>

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!
<a href="http://github.com/eduardok/versaplex" rel="nofollow noreferrer">http://github.com/eduardok/versaplex</a>

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.

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

Visual Studio

SQL Server

数据库

服务器

MySQL

对数据库对象进行版本控制的最佳方法是什么？我使用的是Visual studio 2005/2008和SQL server2005。我更喜欢一个可以与SVN一起使用的解决方案。

问对SQL server存储过程进行版本控制的最佳方法是什么？
EN

回答 9

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问对SQL server存储过程进行版本控制的最佳方法是什么？EN

回答 9

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问对SQL server存储过程进行版本控制的最佳方法是什么？
EN