May 6, 2005 at 11:32 pm
Hi there,
I have been using merge replication with pull subscription. I managed to add a constraint using the following steps and schema changes were taken place at the publisher, but when i do syncronization at the subscriber, it does not sync,instead it gives en error. I have even re-initialized the subscription, still it does not work. Is anyone out there to give me a solution.
Your help would really be appreciated. Thanks in advance.
steps, that i have used to create a constraint on the published table is given below.
a. Open Notepad
b. Paste the following Transact – SQL Command
alter table <PublishedTableName>
add constraint <ConstraintName>
go
c.Save the files as addConstraint.sql
d. use <PublicationDatabase>
go
sp_addscriptexec @publication = <PublicationDatabase>,
@scriptfile = <path of addConstraint.sql>
go
Error that i have encountered at the subscriber when i syncronize is given below
The schema script '0\\machinename\repldata\20050506184002630\addConstraint.sql could not propagate
Cheers
Visu
May 9, 2005 at 8:00 am
This was removed by the editor as SPAM
May 13, 2005 at 11:04 am
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/replsql/replplan_2ipa.asp
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/replsql/repltypes_5r5a.asp
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/replsql/replbackup_3js7.asp
Check thsi line particularly
In synchronous mode, the sync with backup option is set on the publication database. This causes the Log Reader Agent to synchronize with the publication database backup. In this mode, the Log Reader Agent does not propagate any transactions from the Publisher to the distribution database if they have not been backed up. This ensures that no Subscriber will get ahead of the Distributor; however, this also means that replication latency (the time it takes changes made at the Publisher to appear at the Subscriber), which can usually be as low as a few seconds, is now constrained to be greater than or equal to the log shipping interval. Typically, this is between two and ten minutes.
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply