How to detach replication dbs?

Hot Topic

Merege Replication Failed
move db from sql server 2000 to sql server 2005
Grant Database Access
Setting up MSSQL 2005
Scope and Grand Total
Report does not render
Installation of SQL Server 2005 post-SP1 hotfix 918222 (Build 2153) fails at copyengine.cpp Line: 689
Forcing Calculated Measure to be calculated at processing
Errors processing data from Oracle to SQL
SSIS Package Failing - SQL JOB

SQL Server

can i restore sql 2000 from veritas under sql 2005?
Windows integrated security and subscription
CREATE ENDPOINT failing with no errors
Row by row operations in sqlserver
SP2 CTP November 2006 installation failed
Repeate group values in Matrix
Scheduling multiple reports at one time
Deployed reports have javascript errors?
Unable to backup or restore SQL 2005 database to desired drive
Replaceable parameters in Subscriptions

How to detach replication dbs?

There are two databases on two web servers, db01 is on server01, db01_replica is on server02, db02 is on server02, db02_replica is on server01. db01 and db02 are both for one system. Each time after doing performance test, I have to recover databses. I copy the data files in a folder, try to use detach and attach to recover databases. But with two replication dbs, I don't know how to do it. The replication db should also be recovered.



Answer this question

How to detach replication dbs?

  • Heilke

    The situation is: my project is partitioned in two db servers, which all use SQL Server 2005. db01 is on server01 and has replication in server02, db02 is on server02 and has replication in server01. Each time there is a new build of the project, I have to do performance test for it. Unluckily, prepare for the performance test data need 2 days, each time do deployment for the new build, the db will be re-deployed, so all data will lose. I have keep the old build database and data, the most important thing is how to resotore data into new build. I ever used "bcp" to export and import data. But I don't know when replication will end up. So I think maybe detach/attach can help.

  • Florian 0.

    Detach/attach is breaking the link between replication and these databases.

    Depending on some specifics, there may be several ways to get what you want to do.

    First, knowing what version and edition will tell us what tools we have to work with.

    Off the top of my head, you could tear down your replication setup, detach/attach, and recreate the replication config. Not pretty, but you could automate it with scripts.

    You can use backup/restore instead of detach/attach.

    You could possibly create database snapshots of all the databases, and then to reset use RESTORE DATABASE <dbname> FROM DATABASE_SNAPSHOT=<snapshot name> to limit the amount of data being moved.



  • How to detach replication dbs?
Answer this question