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


Embed this content in your HTML

Search

Report adult content:

click to rate:

Account: (login)

More Channels


Showcase


Channel Catalog


Channel Description:

Discussions on SQL Server Replication

older | 1 | .... | 39 | 40 | (Page 41) | 42 | 43 | .... | 181 | newer

    0 0

    The script below seems to work fine in SQL Server 2008 R2 SP1 (Enterprise Edition), but not in SP2.
    Is this a bug?

    Ivar

    use master
    go
    
    create database CdcTestDb
    go
    
    use CdcTestDb
    go
    
    exec sys.sp_cdc_enable_db
    go
    
    create table Tab (col1 int not null primary key, col2 varchar(10) null)
    go
    
    exec sys.sp_cdc_enable_table
    @source_schema = N'dbo',
    @source_name   = N'Tab',
    @role_name     = NULL
    GO
    
    exec sys.sp_cdc_disable_table
    @source_schema = N'dbo',
    @source_name   = N'Tab',
    @capture_instance = 'all'
    GO
    
    exec sp_rename N'dbo.Tab.col2', N'col2b', N'COLUMN';
    -- Msg 4928, Level 16, State 1, Procedure sp_rename, Line 547
    -- Cannot alter column 'col2' because it is 'REPLICATED'.
    -- Msg 0, Level 20, State 0, Line 0
    -- A severe error occurred on the current command.  The results, if any, should be discarded.
    


    0 0

    hi my frnds....

    greetings.....!

    pls forward common issues in transactional replication ?

    this is my interviw quetion.

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

    Best regards..

    vijay


    0 0

    Checking upgrade possibility of SQL Server 2008 R2 to 2012 without any down time.

    I have two nodes cluster with active\passive setup. SQL server version is of 2008 R2 with SP1.

    Is it possible to upgrade passive node first and then failover the active instance to passive and then upgrade again that first node. Please note this will be sql server complete upgrade from 2008 R2 to SQL server 2012.

    Please confirm.

    Santosh Singh


    0 0

    How do I identify the tables replicated in

    transactional replication and in non-transactional merge replication


    0 0

    how to resolve these and am unable updating both sides of the databases.

    can any one say step by step process for merge replication which it works



    0 0

    Hi,

    How can we identify that who has latest updates Publisher or Subscriber ?

    I want to update latest changes while synchronization.

    Please suggest me.

    Thanks in advance


    0 0

    I use transactional replication among 4 sql servers to keep data synchronized (Peer-to-Peer).  The databases are highly transactional.  This morning, one of the servers was unable to be reached for period of time.  The result is this (calling them Servers A, B, C, and D):

    If transactions occur on B, C, or D, they successfully replicate to ALL servers, including A

    If transactions occur on A, they do not replicate anywhere.

    What I found when looking in the Replication Monitor, Selecting the Publication on Server A and right clicking a subscription in "All Subscriptions" tab, choosing "View Details" and then the "Undistributed Commands", is that the "Number of commands in the distrubution database waiting to be applied to this Subscriber" is 1.2 million.

    If I start the distribution agent on these subscriptions, it takes a lock that blocks all the other servers, and undistributed commands for those servers/subscriptions begins to accumulate.  It seems like the time to get through 1.2 million commands will take a long time, and i'm concernd the other publications/subscriptions will accumulate a large number as well.

    I would like to "reinitialize" these subscriptsions, but i cannot do this from a backup or snapshot.  The database cannot be taken offline, or altered like that.  What's more, i have verified that the data in the database on all 4 servers is pretty much synchronized. (which makes me wonder what these commands are).

    Essentiall what I would like to do is clear the pending commands, and have replication continue.  I can fix any discrepancies that might remain manually.

    Is there a way to accomplis this?

    Thanks


    Matt


    0 0

    I have a merge replication with 4 tables on the publication and used  filter rows with a condition.  When I tried to synchronize I am stuck with the message

    "Waiting 60 second(s) before polling for further changes." for ever.

    What is wrong?

    0 0

    This is actually a post on a non MS forum from my coworker who deals with SQL I'm assisting him on this SQL Replication issue.

    Both SQL server 2005 SP4 on Windows 2003. Replication was working untill about a week ago and we tried to rebuild a couple of times but no luck.

    "

    I have a transactional replication publication with about 30 tables. Most of these tables are being replicated as expected. When I run a trace I can see their sp_MSupd_dboXXXXX procedures running, I can verify that the data is in sync.

    However, for one table, this is not happening. When I looked in the database the table was being replicated to, it did not even
    have its own sp_MSins, upd, and del procedures.

    When I run sp_browsereplcmds and provide its publication_database_id and article_id, I can see that the command is waiting to be run.

    For example, it might say
    {CALL sp_MSins_dboTableName (fields here)}. It will sit there for a while, then disappear.

    My first assumption was that it wasn't being applied because the procedure didn't exist. So I wrote my own insert proc to confirm this (@c1
    datatype, @c2 datatype etc...) and tested it to be sure it worked.

    But even then, when I do an insert, the command sits in the repl_commands table for
    a while, then disappears, and no row ever hits my table.

    I'm getting pretty lost here. Can anyone help? Thanks!

    EDIT I should add some more detail:

    The distribution DB lives on the subscriber. There are several publications from the same database on the publisher to the same database lon the subscriber (three to be exact, two work fine, one does not).

    On two of the publications, a tracer token is processed within about 4 seconds. On the one I'm having trouble with, the tracer token hangs in
    limbo indefinitely

    "


    , Kristofer Olafsson


    0 0

    What is the next best option if I can't do transactional replication because the table I need to replicate does not have a PK? The reason I wanted to do transactional replication is because I only wanted incremental changes from the publisher table. (So, doing a snapshot replication would defeat that purpose)


    0 0

    Hi all,

    My understanding is that in merge replication the identities on the publisher is auto managed if auto_identity_management is enabled but some times i am getting an error about identity range consumption for a certain table on the publisher. and asks to execute a stored procedure to adjust the identity ranges.

    so my question how to prevent for all and once identity ranges consumption on the publisher ?


    0 0
  • 04/13/13--03:56: Replication
  • hi......

    greetings.....

    when Recovery model is SIMPLE so, log file will be truncate . backup not possible

    In transaction replication. recovery model is SIMPLE.  eevn recovery model is simple  but transaction replication working .

    how it was working ?

    Best Regards .

    vijay


    0 0

    Hi All,

    is there any relation between AWE , merge replication  and sql server performance ?


    0 0

    I need to do a full clean for table "MSmerge_generation_partition_mappings" in merge replication during a maintenance window,  how to do this ?

    or in other words i need the publication to be back like if it was just newly created.

    my target is to improve the initial sync so it won't take time.


    0 0

    Hi all,

    I need to call my SP when merge agent has finished its work, but only if any data has been exchanged. 

    I was thinking of adding a new step to merge agent, but don't know how to detect if any data was replicated.

    Many thanks in advance,

    Leila


    0 0

    I am trying WebSync with RMO and it works well with no filtering, and few joins

    But when adding several joins on all tables I am getting this issue :

    The connection with the server was terminated abnormally

    I tested the few joins on a subset of the tables I need to replicate, can this error be related to the number of tables ? I don't see how it makes sense, is large data a problem ?




    0 0

    Hi guys,

    I'm hoping if you guys could help to explain the weird situation I'm facing.

    On our main Windows Server 2008 R2, we have SQL Server 2012 Standard setup with Merge Replication. The server has around 15 subscribers. One of the subscribers replicates data on a VPN connection set up over a mobile broadband connection. Now what has happened is the mobile connection dropped and the subscriber could not connect to the server through VPN. After a few days when the connection was back up, the replication monitor started giving this error --

    Error messages:
    The subscription to publication 'abc' could not be verified. Ensure that all Merge Agent command line parameters are specified correctly and that the subscription is correctly configured. If the Publisher no longer has information about this subscription, drop and recreate the subscription.  (Source: MSSQL_REPL, Error number: MSSQL_REPL-2147201019)
    Get help: http://help/MSSQL_REPL-2147201019
    The subscription could not be found. (Source: MSSQLServer, Error number: 20021)
    Get help: http://help/20021

    I checked the subscription at the subscriber and indeed the said subscription was missing from there. This has happened for the second time in the last few months and I'm not exactly sure if it's entirely because of the network dropout. I have had similar situations where a subscriber was off-network for a while and when it was connected back to the network, it replicated fine. I tried checking the error logs to get a clue of why this was happening but no success.

    It's a pain to drop the database and recreate the subscription back again as it's very time consuming. Any help on why this is happening would be great.

    Thanks


    0 0

    I am looking for guidance in setting up replication (Merge) between SQL server 2008 r2 (based at HQ) and severeal SQL CE databases on Windows mobile 6.5 handhelds

    Is this even possible?if  so where is the best place to start.

    I am interested to know if we wil need to set up each device as a subscriber to the SQL server 2008 r2 publisher?

    Jawahar

     

    Jawahar


    0 0

    I just started a new job and inherited an environment that has two SQL server running Transactional Replication as a failover.  The publisher and Distributor is on one server while the subscriber is on the other.  It's just one main database that is being replicated and it's for a helpdesk software that we're running.   From all accounts the replication looks like it is running fine.

    I have never used this method for HA before and consider myself to be not an advance SQL person.  Can anyone tell me the procedure to take for failing over to the Subscriber DB in an event of the Server hosting both the publisher and Distributor goes down?  Also what would be  the procedure to take once the Publisher and Distributor comes back up?

    I'm trying to document this process and learn how it works so I don't get caught in a bad situation in an event that this happens.  I would probably make a recommendation to go with other alternative for HA in the future.

    Thanks


    0 0

    We have
    A single publisher running SQL server 2008 R2
    9 subscribers, each subscribing with merge replication to 2 or 3 publications

    One of the subscriber servers went down and has been replaced, but three subscriptions on this server were lost.
    The subscriptions were deleted from the publisher and this seemed to be partly successful as they are no longer listed under the publications. However the agent still showed two of the jobs and would not delete them. However eventually after some weeks these were deleted. But they are still showing up in Replication monitor. The message is that the subscriptions don't exist. (One out of the three subscriptions seems have been completely successfully removed.)

    Error messages in Replication Monitor:
    Unable to retrieve subscription information for the 'Subscriber' from the 'Publisher'. The subscription to publication 'publication_name' is invalid or has not been setup correctly. (Source: MSSQL_REPL, Error number: MSSQL_REPL-2147201019)
    Get help: http://help/MSSQL_REPL-2147201019
    The subscription could not be found. (Source: MSSQLServer, Error number: 20021)
    Get help: http://help/20021

    The problem:
    Simple updates on subscribers are occasionally showing up as a conflict and the old record on the publisher always wrongly wins. However there should not be a conflict in this situation as the record is only being changed on one subscriber.
    I found a post with a similar problem and it was suggested this may be caused by an orphaned subscription, but no solution was apparent at the time.

    Any help will be greatly appreciated.
    Many thanks

    Steve


older | 1 | .... | 39 | 40 | (Page 41) | 42 | 43 | .... | 181 | newer