Re: The Publisher has been restored from a backup whose schema change version is different from the Sub

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

From: kanu25 (kanu25.1armcb_at_mail.mcse.ms)
Date: 08/10/04


Date: Tue, 10 Aug 2004 01:01:25 -0500


How did you end up solving this issue and are your sites local or via
ADSL?
I am about to go through the same thing using MSDE2000 at the site as
publisher/distributors across ADSL internet to SQL2000 as subscriber at
head office. Know of any potential issues to look out for?

Paul Kleynhans wrote:
> *Hi
> I have been running Merge Replication with SQL200 Sp3a successfully
> for over
> 6 months now. We currently have 15 sites replicating to a central
> server
> with an average of 5000 transactions per site per day.
>
> Everything was going fine up until 3 days ago, when I got the
> following
> error on some of my sites:
>
> -2147200940: The Publisher has been restored from a backup whose
> schema
> change version is different from the Subscriber. Rerun the Snapshot
> Agent
> and reinitialize the subscription.
>
> I followed the instruction in the error message and reinitialised
> the
> affected client sites after creating a new snapshot, but the error
> changed
> to the following error:
>
> -2147201001: The schema script 'exec sp_repldropcolumn
> '[dbo].[c_products]',
> 'ProductDescription', 1' could not be propagated to the subscriber.
>
> The detail of the above error states the following:
>
> 27160: A column was added to or dropped from the replicated table.
> 5074: The object 'DF__c_product__Produ__7A3719BC' is dependent on
> column
> 'ProductDescription'.
> 4922: ALTER TABLE DROP COLUMN ProductDescription failed because one
> or more
> objects access this column.
>
>
> My initial thoughts would've been that a column change I did in the
> database
> would cause this, but the last changes made to the database structure
> was
> done more than 30 days ago, and all sites have been replicating fine
> since
> then. Currently my biggest concern is that the clients are still
> generating
> data and that that data may be lost when recovering from this
> problem. The
> interesting news is that the correct schema is resident at the
> clients that
> are giving me this problem, so I have no idea why this error is
> occuring.
>
> Any help would be appreciated. *

--
kanu25
------------------------------------------------------------------------
Posted via http://www.mcse.ms
------------------------------------------------------------------------
View this thread: http://www.mcse.ms/message230134.html
 


Relevant Pages

  • Re: Replicate 600G db
    ... replicating 600 G is more complex than replicating a smaller amount. ... To do this you replicate to a local database ... test on your subscriber, make the local subscriber database name test. ... Snapshot delivery section, select the use snapshot files from the following ...
    (microsoft.public.sqlserver.replication)
  • RE: INCREMENT IN DATAFILE SIZE
    ... There could be any number of reasons for the difference in size. ... Are there triggers on the subscriber that ... don't exist on the publisher? ... rows including what might currently be in the process of replicating. ...
    (microsoft.public.sqlserver.replication)
  • Re: Replicating between SQl server and MSDE clients!please help
    ... I am replicating over the internet.I am using merge replication anhd ... We are having a central sql server and clients are having dsl ... publication you hard code in the credentials there. ...
    (microsoft.public.sqlserver.replication)
  • Re: Merge replication between two publishers with dynamic filters
    ... But in turn are replicating that table to SiteC. ... SiteB and replicate that to SiteC with the proper filter. ... On the subscriber you can have a view on those two tables that will give you ... I have different publishers of the same table. ...
    (microsoft.public.sqlserver.replication)
  • Merge Replication Error: The process could not enumerate changes at the Subscriber.
    ... When clients are connected to publisher, ... the change gets replicated to the subscriber without any errors. ... insert operation, replication generates an error: ... (Source: ATLAS (Data source); Error number: 1540) ...
    (microsoft.public.sqlserver.replication)