November 22, 2006 at 9:49 am
Hi,
I have a live SQL Server 2000 database that I currently replicate (using transactional replication) to another SQL Server 2000 database on a seperate server.
When setting up the pull subscription I was unable to select the "Yes, initialize the schema and data" option, I had to select the "No, the Subscriber already has the schema and data" option as the snapshot would have locked out the tables on the live database.
Therefore I applied the following steps ...
1. I took a backup of the live database.
2. Restored it into the other server.
3. Created a pull subscription from the database I have just restored and selected the "No, the Subscriber already has the schema and data" option.
The data is replicating fine from the published database into the subscriber database, however last night the transaction log on the subscriber database ran out of disk space, so when I came in this morning I had to re-create the pull subscription and then use the RedGate data comparison tool to re-syncronize the two databases as I cannot take a snapshot of the live database as this will lock out the tables.
Can anyone suggest a better way of re-syncronizing the two databases? Or do the databases automatically re-syncronize when I re-create the pull subscription?
Basically I cannot take a snapshot of the live database, and if a problem occurs which stops the data replicating I need to know how to get the two databases in sync again.
Thanks in advance for your help.
www.sqlAssociates.co.uk
November 23, 2006 at 10:13 am
you have to re-initialize replication with no synch or drop te SUB & run the snapshot.
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply