Post reply

Replication from sql 2008 to sql 2012

  • March 5, 2014 at 1:06 pm

    #290555

    Hi,

    can we setup replication from sql 2008 server(publication) to Sql 2012 server(subscriber) with the distribution is on a different server(sql 2008)?

    The tables that are going to be replicated from the publisher are already replicating to an existing sql 2008 server but the subscriber(sql2008) tables on existing subscriber have a diff schema(dbo) than the new subscriber(sql 2012) tables schema(Applictiontbls). So I can not use the existing publication and have to create a new publication.

    Can the same article can be participating in multiple publications?

    Thanks.

  • March 10, 2014 at 7:26 am

    #1695512

    This should work.

    At my place it is not unusual for the publisher and distributor to be at a lower SQL version than some of the subscribers. We are currently publishing from SQL2012 to subscribers on both SQL2012 and SQL2014.

    There is an upper limit on how many versions can be skipped, both from the MS support side and on what will work technically. Typically this is two SQL versions. Both from a support and technical aspect, you cannot mix SQL2012 and SQL2005 in the same publication.

    Original author: https://github.com/SQL-FineBuild/Common/wiki/ 1-click install and best practice configuration of SQL Server 2019, 2017 2016, 2014, 2012, 2008 R2, 2008 and 2005.

    When I give food to the poor they call me a saint. When I ask why they are poor they call me a communist - Archbishop Hélder Câmara

  • March 11, 2014 at 9:41 am

    #1696041

    I already have some publications on the server1. I am trying to create a new publication and new subscriber for a new set of replication.

    After creating publication the snapshot agent running forever and the job on distribution database is running for ever at step2.

    When I check the replication monitor I see the following error.

    The replication agent has not logged a progress message in 10 minutes. This might indicate an unresponsive agent or high system activity. Verify that records are being replicated to the destination and that connections to the Subscriber, Publisher, and Distributor are still active.

    The source table is not huge. They have few thousands records.

    I checked some online solutions but did not workout.

    http://social.msdn.microsoft.com/Forums/sqlserver/en-US/c451721e-03fe-407d-ac5e-f2f15014efcb/error-the-replication-agent-has-not-logged-a-progress-message-in-10-minutes?forum=sqlreplication

    Any ideas to troubleshoot this will be a great help.

    Thanks,

    Hari.

Viewing 3 posts - 1 through 2 (of 2 total)

You must be logged in to reply to this topic. Login to reply