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


Channel Catalog


Channel Description:

Discussions on SQL Server Replication

older | 1 | .... | 43 | 44 | (Page 45) | 46 | 47 | .... | 180 | newer

    0 0

    I have 2 soon to be 3 customers who have identical database structures, tables, SP's all using merge replication etc they are run on their own servers I want to move them to a single web server and offer web synchronisation from there.

    I know that I can combine all the data into a single database and seperate the data by company but currently there are only 2 tables which directly reference companies and then there are all the stored procedures and code.

    I have tried attaching a second re-named database but their internal name prevents this

    is there any other way I could try?

    I am only ay a suck it ansd see stage


    jnc


    0 0

    Hello,

    when i view replication monitor  i get the following error:

    Procedure or function 'sp_MSupd_dboItems' expects parameter '@bitmap', which was not supplied. (Source: MSSQLServer, Error number: 201)

    also, in what database the stored procedure 'sp_MSupd_dboItems' found

    Can someone help with this error please


    0 0

    I have setup the merge replication between two servers. In server A, created publisher and server B, we have created Subscriber, but the merge agent is running in Server A side.

    Now, we have planned to create one more server C as a Disaster recovery, so I have an idea to create triangular way of replication in SQL server 2012. For example: if server A fails, Server B and server C will be in sync ; if server B fails, server A and C will be in sync; if server C fails(temporary ), server A and C will be in sync.

    Please let me know whether this can be possible in merge replication.

    With Regards,

    Santhosh Wilson


    0 0

    Hi,

    how many servers can participate as subscribers to the central publisher in a bidirectional transactional replication topology? If there is a limit, what are the reasons for this limit?

    What happens if the connection between one of the subscribers and the central publisher fails? Will the replication between the two nodes continue as soon as the connection is reestablished or does it need manual intervention to continue replication?


    0 0

    Hi,

      I have already published the database and several subscribers are connected to it. Now I would like to create trigger on one of the table.

      But I dont want republish and resubscribe again.

      Will this cause any issue to the publisher or subscriber in any way. ?

    Thanks in advance,

    Pavan


    Pavan


    0 0
  • 05/02/13--03:19: Peer_Peer Replication
  • I have just created peer to peer replication on couple of test server.

    Let's say TestServer1 and TestServer2.

    And test database called Test_Peer.

    First i have create couple of tables and create new Peer-Peer Replication from TestServer1-> TestServer2.

    Publication: TestServer1_Peer_TestServer2_SP1.

    My question is, what if i have created new table and want to put them into Peer-Peer replication.

    Do i need to create new publication, configure peer-peer technology and also do i need to take backup every time (After creating table) before putting into peer-peer replication?


    0 0

    Hi,

    I have a merge replication (on a single table) between 4 servers. Two days ago, I had to delete the replication on the publisher/distributor server to purge a large amount of data on the database in the 4 servers. Then, I re-established the replication. Now, no data at all are replicated. After investigation, I saw a huge amount of conflicts with the following error: Unable to synchronize the row because the row was updated by a different process outside of replication. I tried to Reinitialize the subscriptions but it didn't help. I did a Validation on rowcount, but of course, validation failed, as the data are not replicated anymore. Now, the table on each servers is totally out-of-sync.

    What can I do to fix the problem? How can I "restart" the replication and not loosing any data?

    I'm no DBA, so sorry if those questions looks silly.

    thanks for your time and help


    0 0

    I have a situation where I need to use transactional replication from 2 different published database to 1 subscriber database.  Unfortunately, some of the tables share the same name, but are completely different schema and data.   So, I used “Destination object owner” to create use different schemas for the 2 publications. This works fine and gets the tables as expected.  

    PubServerA.DB.dbo.TableA -> SubServer.DB.A.TableA

    PubServerB.DB.dbo.TableA -> SubServer.DB.B.TableA

    However, the problem is the stored proc names do not use the “Destination object owner” field. So I get 1 set of stored procs, “sp_MSxxx_dboTableA”, with last one wins.  This causes replication of the other table to fail with parameter violoations. 

    I realize I can manually change the name of the stored proc.  My question is, why doesn’t it use the “Destination owner name” in the name and save me the trouble, “sp_MSxxx_ATableA” and ““sp_MSxxx_BTableA”?  This is not something which is easy to change in the GUI for all tables.


    0 0

    Is this possible?

    We are deciding which SQL version to use for a new subscriber.  We would like to use 2012, but I wonder how it would handle the published DB being in 80 (SQL2000) compatibility mode. 

    TIA. 


    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 working on creating peer-to-peer replication testing.

    I have created Peer publication from DEV-> DBTEST. 

    All log reader agent job working to be fine on DEV but it give me error on DBTEST as follow.

    Any help should be greatly appreciated. Please let me know if more information is required.

    Executed as user: sqlservices. Replication-Replication Transaction-Log Reader Subsystem: agent DBTEST-Test_PeerReplication-8 failed. The system cannot find the file specified.  The step failed. [SQLSTATE 42000] (Error 14151).  The step failed.


    0 0

    Hi,

      Is there a way to find out identity range set for tables for all the subscribers. Is there any log stored at publisher for all the subscribers.

    Thanks in advancePavan


    Pavan


    0 0

    This does not seem to be a retention period issue but more like a IP/DNS issue as the mobile units is using dynamic Ip.

    Anyone else running into this


    0 0

    I have a MSSQL 2008 on a windows 2008 server.

    I cant delete a publication that isnt in use anymore i get the following error.

    TITLE: Microsoft SQL Server Management Studio
    ------------------------------

    Could not delete publication 'TASS Publication'.

    For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=10.0.1600.22&EvtSrc=Microsoft.SqlServer.Management.UI.VSIntegration.ObjectExplorer.Replication.ReplicationMenuItem&EvtID=CantDeletePublication&LinkId=20476

    ------------------------------
    ADDITIONAL INFORMATION:

    An exception occurred while executing a Transact-SQL statement or batch. (Microsoft.SqlServer.ConnectionInfo)

    ------------------------------

    Cannot execute as the database principal because the principal "dbo" does not exist, this type of principal cannot be impersonated, or you do not have permission.
    Changed database context to 'tass'. (Microsoft SQL Server, Error: 15517)

    For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=10.00.2531&EvtSrc=MSSQLServer&EvtID=15517&LinkId=20476

    ------------------------------
    BUTTONS:

    OK
    ------------------------------

     

    I have tried to delete it by right clicking and delete. I have tried by query.

    execsp_removedbreplicationN'<sqlServerName>'

    execsp_droppublication @publication=N'<sqlServerName>'

     

    I have looked at many forums.

    I am trying to do this as 'sa'.

    Do you have any suggestions?


    0 0

    Hi, 

    I want to configure replication and then i run this commands:

    exec sp_MSupdate_agenttype_default @profile_id = 1
    GO
    exec sp_MSupdate_agenttype_default @profile_id = 2
    GO
    exec sp_MSupdate_agenttype_default @profile_id = 4
    GO
    exec sp_MSupdate_agenttype_default @profile_id = 6
    GO
    exec sp_MSupdate_agenttype_default @profile_id = 11
    GO

    I get:

    Msg 208, Level 16, State 1, Procedure sp_MSupdate_agenttype_default, Line 19
    Invalid object name 'msdb.dbo.MSagent_profiles'.
    Msg 208, Level 16, State 1, Procedure sp_MSupdate_agenttype_default, Line 19
    Invalid object name 'msdb.dbo.MSagent_profiles'.
    Msg 208, Level 16, State 1, Procedure sp_MSupdate_agenttype_default, Line 19
    Invalid object name 'msdb.dbo.MSagent_profiles'.
    Msg 208, Level 16, State 1, Procedure sp_MSupdate_agenttype_default, Line 19
    Invalid object name 'msdb.dbo.MSagent_profiles'.
    Msg 208, Level 16, State 1, Procedure sp_MSupdate_agenttype_default, Line 19
    Invalid object name 'msdb.dbo.MSagent_profiles'.

    How can solve this? 

    Also why then I right click on Replication folder "Configure distributor" is not available?

    thanks


    0 0
  • 04/29/13--23:38: Repilication_Issue
  • hi,

    Login failed. The login is from an untrusted domain and cannot be used with Windows authentication. (Source: MSSQLServer, Error number: 18452)

    i am using mixed authentication mode only .when i configured the transitional replication i can connect to that db  from subscriber server .And i also checked manually i am able accesses files of other server .But i cant get where i am missing 

    help me please !!!


    naveen


    0 0
  • 05/03/13--15:26: Replication and Clustering
  • Hi, 

    Is it possible to set up a Publisher-subscriber replication on a SQl cluster that has two nodes? I have never seen this kind of configuration before. 

    Thanks. 


    0 0

    Hi,

    We recently identified a performance issue with a long running query (usually around 9 seconds using an existing, different index) which is improved with the addition of a new non-clustered index.

    The new index has recently been applied to the primary database and performance improved to around 1-2 seconds.  This index has also been applied to our replicated database (which has exactly the same schema, data and indexes for the table as the primary database in this case) but it is not using this new index, rather the existing, different index.

    All indexes on our replicated database are applied manually rather than automatically.

    We know it's using the existing, different index from looking at actual execution plans.

    We've updated statistics for the table but still no improvement.

    When we initially applied the index to the primary database table we ran an sp_recompile on the table, but this was a step we'd added due to previous slow running stored procs after an upgrade.  That is the only difference we can think of between the steps we've taken in creating the index and can't see why that would make a difference if we updated the statistics for the table anyway.

    Can anyone offer any other checks or steps we could take to get queries to use the index (without using hints)?

    Thanks

    Chris


    0 0

    Dear,

         An accident, I deleted data in  MSmerge_contents in publisher database. From there, data can not sync from publisher to subscriber. How can I fix it?

     

    Thanks


    0 0

    I have a transactional replication where synchronization periodically stops when we receive a large amount of transactions (million) and sometimes there is a network interruption.  When we start the subscription, the data does not flow until after we have validated the subscriptions, which comes back with correct counts and then the undelivered transactions starts to decrease.  Any idea why this keeps happening?  What is the validation subscription doing?

older | 1 | .... | 43 | 44 | (Page 45) | 46 | 47 | .... | 180 | newer