部署后升级SQL Express数据库的工具 [英] Tool to upgrade SQL Express database after deployment

查看:140
本文介绍了部署后升级SQL Express数据库的工具的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我有一个使用SQL Express的应用程序,我的客户主要是没有专业IT人员的人,所以不知道如何运行脚本。所以部署和升级必须很简单。部署部分全部了解。我需要知道的是当产品的第2版出来,并且更新数据库结构或数据的时候,是否有比传统的脚本方法更好的方法。通常,脚本方法的问题是,您有一组开发人员使用的开发数据库,​​并没有跟踪谁做了什么更改,以便能够将它们并入部署数据库。

解决方案

我建议使用SQLCompare。它允许您进行所有更改,而无需担心脚本,然后可以将Dev / Stage环境与生产环境快速同步,或创建可在远程计算机上运行的脚本。



如果你不想卸载$$$,请保持源代码控制的所有更改就像你的代码一样。您可以单独保留每个更改脚本,也可以将scc系统的中继线作为DB的最终版本,并运行每个DB对象的版本(我更喜欢更改脚本方法,但已经看到其他工作)。


I have an app which uses SQL Express and my customers are mainly people who don't have a dedicated IT staff, so wouldn't know how to run scripts. So the deployment and upgrades has to be easy. The deployment part is all figured out. What I need to know is when version 2 of the product comes out and its time to update the database structure or data, is there a better way than the traditional method of scripts. Often times the problem with scripting methods is, you have a development database being used by a bunch of developers and there is not track of who made what changes, so as to be able to incorporate them into the deployment database.

解决方案

I would recommend using SQLCompare. It allows you to make all of your changes without having to worry about scripts and then you can quickly synchronize the Dev/Stage environment with the Production Environment or create a script to do so that can be run on a remote machine.

If you don't want to shell out the $$$, keep all of your changes in source control just like your code. You can either keep each change script individually, or let the trunk of your scc system be the final version of the DB and run through the versions of each DB object (I prefer the change script method, but have seen the other work).

这篇关于部署后升级SQL Express数据库的工具的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

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