我有一个开发服务器（SQL Server 2008）它有数据库。即Employee（数据库），我还有表、存储过程和数据。
我有另一台生产服务器（SQL Server 2008），它也有相同的数据库，即Employee（数据库），我也有表、存储过程和数据。
现在我的网站从生产服务器运行。
当我在开发服务器中进行更改并创建另一个表、存储过程并插入一些数据时，我想更新我的生产服务器，以便我的更改将转到正在运行的网站
确保我可以通过以下方式执行此操作：
- 使用备份 SQL服务器（.bak 文件）。
- 使用 SQL 脚本处理数据。
- 使用 MDf LDF 文件。
但我想通过使用 SQL Server Integration Services (SSIS) 来做到这一点。
提前致谢。
萨尔曼·安萨里
I have a development server (SQL Server 2008) it has database. i.e. Employee (database) on it, I have tables,stored procedure and data as well.
And I have another production server (SQL Server 2008) also it has same database i.e. Employee (database) on it, I have tables, stored procedure and data as well.
Now my website running from production server.
When I make changes in development server and create one more table, stored procedure and also insert some data, then I want to update my production server so that my changes will go to running website
Make sure i can do it following ways:
- Using Backup SQL Server (.bak file).
- Using SQL script with data.
- Using MDf LDF file.
But I want to do this by using SQL Server Integration Services (SSIS).
Thanks in advance.
Salman ansari
发布评论
评论（1）
为什么要使用 SSIS？我相信您问的是如何部署从开发到生产的数据库更改，而 SSIS 并不是实现此目的的好工具；它用于数据集成，根本不适合同步架构或对象更改。
我认为在决定解决方案之前，您需要更清楚地定义您的要求。例如，通过使用开发数据库的完整副本来升级生产数据库是非常不寻常的，因为您会丢失生产中的所有数据。不过，也许您的用例允许这样做。
无论如何，您需要专注于寻找适合您环境的部署解决方案，例如 VS 数据库项目 或架构比较工具，例如 SQL 比较。完成一些研究后，您也许可以针对您的特定案例提出有关最佳解决方案的更具体的问题。
Why do you want to use SSIS? I believe you're asking about how to deploy database changes from development to production, and SSIS is not a good tool for that purpose; it's used for data integration and is not at all suitable for synchronizing schema or object changes.
I think you need to define your requirements a bit more clearly before you decide on a solution. For example, it's very unusual to upgrade a production database by using a complete copy of your development database, because you lose all the data in production. Perhaps your use case allows for this, though.
In any case, you need to focus on finding a deployment solution that works for your environment, e.g. VS database projects or a schema comparison tool such as SQL Compare. After you've done some research, you may be able to ask more specific questions about the best solution for your particular case.