任何使用Red Gate的SQL Source Control的人 [英] Anybody using SQL Source Control from Red Gate

查看:76
本文介绍了任何使用Red Gate的SQL Source Control的人的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我们一直在寻找SQL Source控件的可能解决方案.我刚遇到Red Gates SQL Source控件,想知道是否有人实现了它?我将下载试用版并试用一下,但只想看看其他人是否有真正的经验.

We have been looking into possible solutions for our SQL Source control. I just came across Red Gates SQL Source control and wondered if anyone has implemented it? I am going to download the trial and give it a shot, but just wanted to see if others have real experience.

一如既往,非常感谢您的投入

As always greatly appreciate the input

-S

推荐答案

从dev-> test->生产时,我使用SQL Compare生成脚本,这节省了我很多时间.

I use SQL Compare for generating scripts when going from dev -> test -> production and it saves me tons of time.

尽管如此,对于源代码控制,我们使用SVN和ScriptDB( http://scriptdb.codeplex.com/ ) 尽管.我主要使用SQL脚本的源代码控制来跟踪更改.我认为很少回滚数据库版本(如果有的话)是可行的,因为在进行结构更改时数据可能已更改.

For source control though, we use SVN and ScriptDB (http://scriptdb.codeplex.com/) though. I mainly use source control of SQL scripts for keeping track of changes. I think that rolling back a version of the database seldomly (if ever) works since data may have changed when making structure changes.

这对于我们当前的一些项目(最大的200个表和2000个sproc)有效.这样做的主要原因是成本,因为并非所有团队成员都必须购买SQL Compare(除非确实需要,否则我避免将依赖项添加到商业项目中.)

This works fine for a few of our current projects (largest is 200 tables and 2000 sprocs). The main reason for doing this though is cost since not all team members have to buy SQL Compare (I avoid adding dependencies to commercial projects unless really needed).

这篇关于任何使用Red Gate的SQL Source Control的人的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆