数据库项目和 TFS 如何帮助我们的开发团队？
我刚刚开始在一家新公司的一个非常小的 IT 部门和一个更小的开发团队（包括我在内只有 2 个开发人员）工作。我们主要为公司开发内部网络应用程序。
现在我的背景是桌面应用程序，因此对于以前从未开发过 ASP.Net Web 应用程序的我来说，这项工作有一点学习曲线。目前我们不使用 TFS，但我已经提出了建议，我们很快就会采用它。
我还在考虑建议我们将 SQL 数据库移至数据库项目中，因为目前我们每晚进行备份以保护数据，但所有更新都是手动的，我们连接到数据库并执行查询等。
我不是 DBA，但在我上一份工作中，我们我们正在将数据库迁移到数据库项目，DBA 似乎很喜欢这个想法。这样做的好处和潜在的缺点是什么？开发完成后，它会帮助我们在实际环境中更新数据库吗？显然我们不想丢失任何数据，而只是更新表/存储过程等。
作为一个附带问题，我对 TFS 的了解非常有限，尽管我们将使用它来处理我们的版本控制，但是否可以使用 TFS 来开发完成后自动更新我们的实时网站？
抱歉，如果这是一个相当广泛的问题，我正在尝试自己研究这个问题，但我想听听实际使用这些产品并做这些事情的人的意见。
谢谢
I have just started working with a new company in a very small IT department, and an even smaller dev team (just 2 developers including me). We mainly develop in house web applications for the company.
Now my background is in desktop applications so this job comes with a slight learning curve for me having never developed ASP.Net web applications before. Currently we do not use TFS however I have made the suggestion and it is something we are going to be adopting soon.
I am also considering recommending we move our SQL databases into database projects as currently we do nightly backups to protect the data but all the updates are manual, we connect to the database and execute queries etc.
Im not a DBA but in my last job we were in the process of migrating our databases to database projects and the DBAs seemed to love the idea. What would the benefits and potential downfalls of this be? Would it aid us with updating databases in our live enviroment after development has been done? Obviously we dont want to loose any data but just update tables / Stored Procs etc.
As a side question I have very limited knowledge of TFS, and although we are going to be using it to handle our version control is it possible to use TFS to update our live websites automatically once development has finished?
Sorry if this is quite a broad question, I am attempting to research this myself but I would like to hear from people who actually use the products and do these things.
Thanks
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
关于数据库项目：我和我认识的几位 dba 都有过不同的经历。我不确定它们现在到底在哪里，但这可能只是我工作方式的一个函数。部署模型...很困难，并且可能会导致一些意外的行为。如果您按照这条路线进行测试测试，以确保您准确理解发生了什么。
如果您只是想获得数据库的版本控制，您可能会考虑
至于从 TFS 部署，你绝对可以做到这一点。我们设置了一个构建服务器，以便每当在构建服务器中检查代码时都会自动启动以编译并将其部署到我们的测试站点之一。 查看此处入门指南。这确实需要在您的网络服务器上进行一些配置才能正确支持，并且文档充其量也很参差不齐。
一旦您对测试区域感到满意，您就可以将某些内容与构建质量的更改挂钩，以便将代码推送到临时服务器甚至生产服务器......或者只是有一个构建设置来重新编译和部署在那里。尽管我不建议以这种方式进行生产推送。不是因为技术问题，而是因为时间问题。必要时从一个位置复制/粘贴到生产环境通常会更快，从而限制停机时间。
About database projects: I, and several dba's I know, have had mixed experiences with them. I'm not sure they are exactly where they should be at this time but it may be simply a function of how I work. The deployment model is... difficult and can result in some unexpected behavior. If you go this route test test test to make sure you understand exactly what's happening.
If you are just trying to get version control for the database you might consider SQL Source Control from Red Gate. It looks pretty nice and hooks into TFS. I used one of the early versions (beta and 1.0) for awhile and was very happy with it. Now that I think about it, I'm not sure why I don't have it here... ;)
As far as deploying out of TFS, you can absolutely do this. We have a build server set up so that whenever code is checked in the build server automatically spins up to compile and deploy it out to one of our testing sites. Look here for a primer to get you started. This does require some configuration on your web server to properly support and the documentation is spotty at best.
Once you are happy with the test area, you can hook something into changes to the Build Quality so that it pushes the code to a staging or even production server... Or simply have a build setup to recompile and deploy out there. Although I don't recommend doing production pushes this way. Not because of a technical issue, but rather a timing one. It's usually much faster to just copy / paste from one location to production when necessary thereby limiting downtime.