Are you the publisher? Claim or contact us about this channel

Embed this content in your HTML


Report adult content:

click to rate:

Account: (login)

More Channels


Channel Catalog

Channel Description:

Discussions on SQL Server Replication

older | 1 | .... | 44 | 45 | (Page 46) | 47 | 48 | .... | 181 | newer

    0 0


    I configured a SQL Server Web Synchronization between two domains (without VPN, IIS 7.5, SQL Server 2008 R2, Merge replication with pull). The configuration was successful and  i set output log file and have seen the messages like

    2013-05-07 04:58:42.347 Downloaded snapshot file 'ACTION_ITEM_ATTACHMENTS_3.sch'.
    2013-05-07 04:58:42.862 OLE DB Subscriber 'SERVERNAME\SQL2008R2STD': {call sys.sp_MSadd_merge_history90 (?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?)}
    2013-05-07 04:58:42.862 Percent Complete: 0

    My database contains around 700 tables to replicate. After few hours when i checked the status of replication at subscriber side, i realized that it struck with the message like,

    2013-05-07 05:27:50.050 Downloaded snapshot file 'UOM_MSTR_366.bcp'.
    2013-05-07 05:27:50.752 OLE DB Subscriber 'SERVERNAME\SQL2008R2STD': {call sys.sp_MSadd_merge_history90 (?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?)}
    2013-05-07 05:27:50.752 Percent Complete: 0
    2013-05-07 05:27:50.752 Downloaded snapshot file 'UPGRADE_LOG_367.bcp'.

    I restarted the agent and it started from the beginning. After few hours i checked again it shows message as above (with different table name) .  When i checked internet connection between two domain, i have seen that there is a connection timeout in between (for milliseconds only).  

    Reply from bytes=32 time=475ms TTL=114
    Reply from bytes=32 time=82ms TTL=116
    Reply from bytes=32 time=81ms TTL=116
    Reply from bytes=32 time=240ms TTL=114
    Request timed out.
    Reply from bytes=32 time=443ms TTL=114
    Reply from bytes=32 time=367ms TTL=114
    Reply from bytes=32 time=350ms TTL=116

    Then i increased internet_timeout property to 1800 at subscriber side. But still getting the issue. What is the cause of this ? How can i overcome this issue?




    If a post answers your question, please click "Mark As Answer" on that post and "Mark as Helpful

    0 0


    I would like to know whether SQL Server Web Replication is recommended for database having  more than 700 tables. If not what are the main disadvantages ?

    In this case, replication over VPN is advisable ?



    If a post answers your question, please click "Mark As Answer" on that post and "Mark as Helpful

    0 0

    hi Is it possible for the distribution agent to write this message to event log ?Because we would like to get alerted on the above message, whenever a new table is added to the publication a snapshot that needs to be generated, but we have seen few times this is missed by a dba or our deployment mechanism. We are running sql 2008 sp3. 


    0 0

    I have a SQL Server 2008 cluster and I an setting up a separate SQL server is a disaster recovery site. I would like to know if I can create the same instance name on the SQL server in the disaster recovery site as the instance on the clustered SQL servers. Thanks.

    0 0

    The server is windows 2012 + SQL 2012 sp1 (11.0.3000 web edition) using AWS EC2 instance. 

    The sqlLogShip versin is 11.0.2100.60.

    We have just setup two sql server doing log shipping every 5 mins.

    I got following error every few minutes.

    An unhandled exception ('System.IO.FileLoadException') occurred in SqlLogShip.exe [6400]. Just-In-Time debugging this exception failed with the following error: Debugger could not be started because no user is logged on.
    Check the documentation index for 'Just-in-time debugging, errors' for more information.

    Not sure how to fix this, I can't find any answer from google/Bing.

    Thanks for any help!


    0 0

    Dear all,

    After I recreate the subcriber to a merge replication. It shows the below error. How can I fix it. Thanks.

    The process could not deliver the snapshot to the Subscriber.
    (Source: Merge Replication Provider (Agent); Error number: -2147201001)
    Cannot insert duplicate key row in object 'sysmergeschemachange' with unique index 'schemachangeversion'.
    (Source: POSSTDBY3 (Data source); Error number: 2601)
    The schema change information could not be updated at the subscription database.
    (Source: POSSTDBY3 (Data source); Error number: 21305)

    0 0

    How to modify the filter without reinitialze


    0 0

     I set up a server with SQL 2k8 R2 and want to sync a publication with a remote subscriber.

    Everything is basically set up and I am using RMO.  Subscriptions are being created on both server and client (uses Express version) , but when I use 


    To initialize the subscription on the clients, is gives me an error : 

    The process could not connect to Distributor 'MACHINENAME\INSTANCE'.      

    at Microsoft.SqlServer.Replication.MergeSynchronizationAgent.Run()
       at Microsoft.SqlServer.Replication.MergeSynchronizationAgent.Synchronize()

    What could be the problem ?? How can I check ??

    0 0

    Is there any tweaks to change the subscription type from Client to Server without dropping the subscription.?

    Please remember to mark the replies as answers if they help. - Kerobin

    0 0

    Hello friends,

    I have setup the transitional replication Push with Immediate update mode , and now it failed because subscriber rebooted and now data was out of sync . Snapshot was not available so to reinitialize i have to generate snapshot and then sync the delta data, but from below link it explained that after setting up the Transitional replication there is way we can update the subscription to queued mode automatically fail over. Do any know how to do that...


    message : To change the update mode after the subscription is created, the update_mode property must be set to failover (which allows a switch from immediate updating to queued updating) or queued failover (which allows a switch from queued updating to immediate updating) when the subscription is created. These properties are set automatically in the New Subscription Wizard.

    Or else please let me know how to sync up the data without reinitialize the data and in future how to tackle this senario.

    Friends can any one tell me how to setup :

    Transactional replication push type which should be able to sync after network outage or any temporary outage. 

    0 0

    Recently in a merge replication scenario with SQL 2008 RTM and SQL Compact cleints we experienced a massive slowdown in server operations during sync. Digging into the process we found that the sp_MSsetupbelongs procedure calls are lengthy. Further profiling and tests revealed that the longest step is a simple looking insert statement into a temp table:

    insert into #notbelong (tablenick, rowguid, flag) select distinct 4038005   , [article1].rowguidcol, -1 from [dbo].[article1] [article1], MSmerge_bi_98DAC279CFFC4D03B886B646B914017A_v_3FE29C0B84BE4927B7EAAB819F09F5D5 [article2], #notbelong nb where (article2.fej= and nb.tablenick = 4038006 and [article2].rg = nb.rowguid

    This insert is inside an expand procedure MSmerge_expand_13, and in the reproduced environment takes some 3 minutes to complete. The select itself produces two rows in zero seconds, the #notbelong table contains 24640 rows before the insert. The #notbelong table and its indices are created by sp_MSsetupbelongs. If in MSmerge_expand_13 we drop the index on #notbelong the insert is fast. Replacing the above insert with one that uses a cursor on the select is also efficient even with the index on. Using another temp table accepting all rows from the select without distinct and than inserting distinct rows from this table is also efficient.

    How on earth can such an insert be that slow?

    0 0


    I have setup transactional replication (one way) in Pull model. I need to know if distribution agent fails therefore I tried to configure an alert from Replication Monitor (Replication: agent failure, error 14151). The problem is that the alert resides on Publisher (mine is Distributor as well) but in Pull model, the distribution agent is on the other side (subscriber). 

    I guess the alert will not be raised if there is any connection problem when distribution agent tries to sync.

    Any help would be greatly appreciated.


    0 0

    After the weekly index rebuild I get the error "Could not execute sp_replcmds". The way I fix this is to stop the log reader and execute sp_replrestart on the database in question. There are several other databases that are replicated and indexes rebuilt and do not experience this problem, this one database in particular consistently gives the error every week.

    60g database on SQL Server 2008r2 SP1 Standard Edition.

    0 0

    The comment column of distributor.dbo.MSdistribution_history contains comments such as

    <stats state="2"fetch="11554" wait="214007" cmds="17898546" callstogetreplcmds="106880"><sincelaststats elapsedtime="300"fetch="8" wait="291" cmds="1948689" cmdspersec="6495.000000"/></stats>

    The state value translates to

    STATE   Indication1       Normal Log2       Reader Thread has to WAIT for Writer3       Writer Thread has to WAIT for Reader

    Is the comment telling me that the reader thread is waiting for the writer thread but has read 1948689 cmds since the last stats entry. Or is it telling me that the reader thread is waiting for the writer thread and the writer thread has written 1948689 cmds since the last stats entry?

    0 0
  • 05/13/13--16:32: replication internals
  • Hi, I am trying to understand internals of replication. I am implementing a push transactional replication I understand, Log reader agent Monitors transaction log of all published databases that are using it for replication. When it finds transactions that are part of a publication, it copies them to the distribution database where they can then be applied to the subscribers by the distribution agent.

    But what I do not know is how does all this happen internally? Could somebody please explain.

    Thanks in advance.............

    0 0

    I have a database that is subject to log shipping. I ran a query that dropped restraints, reassigned IDs then added the restraints back in. The log shipped copy of the datbase was automatically updated by log shipping.

    If I query a table in the originaldatabase without an order by clause, the rows are displayed in the "natural" primary key order. This is not the case for the log shipped copy, I need to add "order by ID" to get the same order.

    Can anyone explain why this is so?

    R Campbell

    0 0

    I have a prospective customer for replicated data and I need to set up a distributor on their 'server' which is 32 bit XP SP3

    I did not realise it was 32 bit till today and had been hoping to use a 64bit evaluation of 2008 R2, no such luck and now I cannot find 2008 anywhere - I understand 2008 R2 is only available as 64 bit

    Can anybody help me with this?

    They do have a copy of 2005 on the server if that is what I have to do can I convert the 2008 R2 data to work on 2005? or do I have to export the objects?

    any tips would be great thanks


    0 0


    I have a table that is receiving rows continuosly throughout the day (transactional replication) and I need to update certain columns (the logic is tio complex to use calculated fields). Is there a way, outside of using triggers, to kick off some code every time a row is inserted? This is SQL Server 2008 R2.



    0 0

    Size of publisher database is 1 TB so when we go for re-initialization of Transaction replication it takes a huge time to complete this activity.

    So is there any way to make re-initialization of transaction replication process faster.

    Will table partitioning of big tables will help to make re-initialize process fast.

    I have SQL Server 2008 R2 Enterprise Edition SP2

    0 0

    We have a pubication with only 8 tables but two of them with 4-5 million rows. Via partitioning the row first belongs to a specific client than after a given time the row becomes archive so it is taken from the client partition into the archive partition. Because the clients are SQL Mobile databases on mobile devices even these archiving creates a lot of delete commands for the clients: the server sends delete commands to all clients for these rows.

    We want to delete the unnecessary rows from these tables but this would create delete messages like the archiving. Is it possible to disable the delete trigger created by the server on these tables before deleting rows? After deleting we would re-enable the trigger. We would delete only rows in the archived state.

older | 1 | .... | 44 | 45 | (Page 46) | 47 | 48 | .... | 181 | newer