Okay so there are 2 computer servers. The one is running SQL Server 2008 and the other is SQL Server 2000. Let's call them DB1 and DB2. So Db1 (SQL Server 2008) is a production server. And everyday we need to backup DB1 server to DB2 server (SQL Server 2000). We have tried SSIS in VS 2008. It works great. However, any changes that will occur in the future pertaining to the database structure of Db1 (SQL Server 2008) will not be reflected in the mirrored database which is DB2 (SQL Server 2000) unless reconfigured manually. For example if in Db1 (SQL Server 2008), an admin added a table or add/delete columns in a certain table, the SSIS package will get an error thus we need to rebuild or reconfigure manually again in VS 2008. We don't want to do that from time to time, right?
好的,所以有2台电脑服务器。一个运行SQL Server 2008,另一个运行SQL Server 2000.让我们称它们为DB1和DB2。所以Db1(SQL Server 2008)是一个生产服务器。每天我们需要将DB1服务器备份到DB2服务器(SQL Server 2000)。我们在VS 2008中尝试过SSIS。它运行良好。但是,除非手动重新配置,否则将来发生的与Db1(SQL Server 2008)的数据库结构相关的任何更改都不会反映在DB2(SQL Server 2000)的镜像数据库中。例如,如果在Db1(SQL Server 2008)中,管理员在某个表中添加了表或添加/删除列,则SSIS包将出现错误,因此我们需要在VS 2008中再次手动重建或重新配置。我们不需要想不时这样做吧?
1 个解决方案
#1
This is a really bad idea. You should use the standard backup features of SQL Server 2008. You should also test your recovery process as well make sure that if you have a disaster that you will be able to recover your production server 100%. It's really too much detail to get into here on all your options but look into the SQL Server Books to get a general overview of the process.
这是一个非常糟糕的主意。您应该使用SQL Server 2008的标准备份功能。您还应该测试恢复过程,并确保如果您遇到灾难,您将能够100%恢复生产服务器。在所有选项中进入这里真的太详细了,但是查看SQL Server Books以获得该过程的一般概述。
https://msdn.microsoft.com/en-us/library/ms189621%28v=sql.100%29.aspx
As a starting base at the very minimum, set your databases to simple recovery model and do a full backup every night. If you create a maintenance plan, it will kind of wizard your way though creating a simple backup plan to do a full backup on a schedule. Then practice a restore to a different database name... just to be sure you know how it works. As you learn more, you can enhance your disaster recovery plan by using full recovery model... etc. I'm just worried that what you have in place now might not be enough to cover you if you have a catastrophic data loss situation.
作为起始基础,将数据库设置为简单恢复模型,并每晚进行完整备份。如果您创建了一个维护计划,它将通过创建一个简单的备份计划来按照计划进行完整备份。然后练习恢复到不同的数据库名称...只是为了确保你知道它是如何工作的。随着您了解更多信息,您可以使用完整恢复模型来增强灾难恢复计划...等等。我只是担心,如果您遇到灾难性的数据丢失情况,您现有的内容可能不足以覆盖您。
#1
This is a really bad idea. You should use the standard backup features of SQL Server 2008. You should also test your recovery process as well make sure that if you have a disaster that you will be able to recover your production server 100%. It's really too much detail to get into here on all your options but look into the SQL Server Books to get a general overview of the process.
这是一个非常糟糕的主意。您应该使用SQL Server 2008的标准备份功能。您还应该测试恢复过程,并确保如果您遇到灾难,您将能够100%恢复生产服务器。在所有选项中进入这里真的太详细了,但是查看SQL Server Books以获得该过程的一般概述。
https://msdn.microsoft.com/en-us/library/ms189621%28v=sql.100%29.aspx
As a starting base at the very minimum, set your databases to simple recovery model and do a full backup every night. If you create a maintenance plan, it will kind of wizard your way though creating a simple backup plan to do a full backup on a schedule. Then practice a restore to a different database name... just to be sure you know how it works. As you learn more, you can enhance your disaster recovery plan by using full recovery model... etc. I'm just worried that what you have in place now might not be enough to cover you if you have a catastrophic data loss situation.
作为起始基础,将数据库设置为简单恢复模型,并每晚进行完整备份。如果您创建了一个维护计划,它将通过创建一个简单的备份计划来按照计划进行完整备份。然后练习恢复到不同的数据库名称...只是为了确保你知道它是如何工作的。随着您了解更多信息,您可以使用完整恢复模型来增强灾难恢复计划...等等。我只是担心,如果您遇到灾难性的数据丢失情况,您现有的内容可能不足以覆盖您。