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 | .... | 152 | 153 | (Page 154) | 155 | 156 | .... | 181 | newer

    0 0

    Hi all,

    I am trying to use Microsoft SQLServer Stored Procedure Resolver for our Merge Replication via Web Sync/LAN

    We have

    User PC <---> Web Service (Server on Cloud) <----> Re-Publisher (DB Server on Cloud) <-----> Publisher (Local DB)

    User PC has SQL Express 2012 installed

    Re-Publisher/Publisher has SQL 2012 SP1 installed

    Web Server (IIS) has dlls from Re-Publisher copied and registered

    Synchronization works well if we use the Default Resolver

    Now we want to use a custom Resolver (registered at Distributor) such asMicrosoft SQLServer Stored Procedure Resolver or a simple one likeMicrosoft SQL Server DATETIME (Later Wins) Conflict Resolver.

    However we encountered an error while doing the synchronization:

    The process could not initialize 'Microsoft SQLServer Stored Procedure Resolver'. Verify that the component is registered correctly.

    We have tried to copy the spresolv.dll from the publisher/republisher to the User's PC and register it with regsvr32 but it did not help.

    Any one has any other ideas, we had a feeling that some other dlls might need to be copied down to the User's PC. We also tried other dlls but still no luck...

    Thanks in advance guys.


    0 0


    I have a SQL replication with  7 pull subscriptions. Recently I modified a SP by adding union with variable assignment inside and all the subscriptions stopped syncing giving the following error;

    "Variable assignment is not allowed in a statement containing a top level UNION, INTERSECT or EXCEPT operator. (Source: MSSQLServer, Error number: 10734)"

    So I Changed the SP as previous and executed. But synchronization is still giving the same error and not replicating. I restarted services and the Server too but the problem still exists.

    Pls help me with a solution.

    Thanks in advanced,

    Chama :)

    0 0


    is supported the merge replication (for each role: publisher, distributor and subscriber) for a database between two "SQL Server 2014" instances configured each on a "SQL Server Failover Cluster" with SAN disks\LUN  configured as "Cluster Shared Volume" (CSV)?

    Note: the datafiles and transaction logs, related to database in merge replication, are located on a "cluster shared volume".



    0 0

    I have a bi-directionally published database with 5 subscribers.  Generally the amount of data transferring is pretty small (sometimes 1 record).  There is a service that runs on each subscriber's workstation that executes a pull merge replication between itself and the publisher every 5 minutes.  On 3 of the workstations, the durations are fairly consistent (2-10 seconds).  On the other two, much of the time the durations are similar to the other 3, but every few times, it takes 30+ seconds to execute, often only sending a record from 1 table.

    I have been capturing performance counters on two of the stations, one consistent and one not, for many different types including SQL Server: Buffer Manager, Replication Merge, General Statistics and others.  In comparing the two, I don't notice much difference, certainly not anything striking, especially at the times that the 30+ second durations occur.

    Has anyone seen anything like this?  If so, what did you do to debug the issue?  If not, any suggestions of debug methodologies, including recommended performance counters and/or other debugging statistics?


    0 0


    I have a replication with couple of subscribers. Recently I made a change to a stored procedure in the publisher DB.

    I out a UNION with variable assignment inside it. after that synchronization stopped throwing the following error;

    "Variable assignment is not allowed in a statement containing a top level UNION, INTERSECT or EXCEPT operator. (Source: MSSQLServer, Error number: 10734)"

    So I changed my SP back as previous and executed. but the error is still there and synchronization ishappening. It's been around 20 hrs now and I'm in a big trouble. pls anyone help me with a solution. I do not want to lost the data in subscribers'

    Thanks a Lot

    Chama :)

    0 0


    Can a SQL Server 2008 R2 server be both a publisher and distributer to a subscribing SQL 2014 AlwaysOn primary replica? I can see a problem with the distribution agent not being able to use the listener, but I haven't tested that yet. Is this true? Anyone have any experience with this configuration? I know with AlwaysOn, that you have to use a remote distributor, but is it required that that server be SQL 2012 or above?


    0 0

    How do you manually do a clean up for change tracking (ie: autocleanup is set to false) in SQL Server 2008?

    0 0


    I'm using SQL Server 2005 Replication Monitor to monitor a number of Publications.

    One Publication node, will not expand however, that is to say that when clicked it's label changes to expanding and then never actually completes in order to provide details of the Publications at the Publisher. This means that I cannot highlight a specific Publication at the Publisher for further investigation and instead have to review all Subscriptions in the subscription watch list, which is cumbersome.

    I have tried removing the Publication and adding it back to Replication Monitor without success, the issue persists. I have also tried creating a SQL Server Login with SYSDBA rights in order to connect to the remote distributor in order to rule out a permissions issue.

    Has anyone else come across this issue before or can perhaps provide further suggestions in order to troubleshoot?

    John Sansom | SQL Server Database Administrator

    0 0

    I've seen many issues with users attempting to use non-default conflict resolvers, but still the standard Microsoft resolvers, and getting errors that: "The process could not initialize 'Microsoft SQL Server DATETIME (Later Wins) Conflict Resolver'. Verify that the component is registered correctly."

    After upgrading the database server and web server to the 2014 SP 1 CU5, this now works for full versions of SQL server, but any SQL Express edition still throws this error (even when on this cumulative update). 

    How can this not be working?  Is this not a supported configuration?  SQL Express supports replication, so why wouldn't it support these conflict resolvers?

    Maybe I should just distribute SQL Standard to all these laptops instead of Express. (NOT SERIOUS)

    0 0

    Environment: Merge Replication with 2 subscribers - SQL Server 2008 R2

    I have setup merge replication with parameterized row filter as discussed in this post:

    After subscribing to publication, the synchronize agent starts and works fine for the first subscriber but doesn't start on a subscriber that its HOSTNAME() is set to  @hostname = N'-8070450532247928832'. The agent shows "Starting Agent" in Replication Monitor and generates error after 10 minutes of inactivity.

    I setup verbose logging and received this error:
    A syntax error occurred near parameter '-8070450532247928832'.

    As an experiment, I just removed the minus sign and used @hostname = N'8070450532247928832' and the agent worked fine. 

    Any idea why minus sign in @hostname generates error?


    0 0

    is there a way to configure SQL Replication so that all traffic is confined to a particular network interface? And that this interface almost definitely won't be the same one as the regular SQL workload is using.

    Probably complicating the issue is the fact that are running clustered publishers.

    0 0

    I have a current client that has replication set up on SQL Server 2008 R2. The current configuration has the distributor on the subscriber server.  The client has built new servers with SQL Server 2012 and will be decommissioning the old servers where the distributor resides. Is there a way to move the distributor to the new server without having to recreate replication?  Is there a better option to this configuration that we should consider going forward? 

    0 0


    I configured replication in our SQL 2012 instance. The snapshot agent executed successfully, but facing the below issue in Distribution agent from distributor to subscriber. Everything is fine, I am not sure where the issue is, Can you please help me. 

    Message: if COLUMNPROPERTY( OBJECT_ID('MSreplication_subscriptions'),'distribution_agent','AllowsNull') <> 1 BEGIN alter table MSreplication_subscriptions alter column distribution_agent sysname null end 
    2016-04-12 18:11:37.382 Category:NULL
    Source:  Microsoft SQL Server Native Client 11.0
    Number:  3609
    Message: The transaction ended in the trigger. The batch has been aborted.

    0 0


    In my Organization, we do have a scenario to get last hour modified data from production database (some of the large tables). 

    So, we are suggesting to go with replication.  However, Our DBA is saying that replication is failure model (they are saying it will slow down the performance).  

    Is there any specific issues exist with SQL Server replication?

    Thanks in advance! 

    0 0

    I have configured logshipping between 2005 and 2014 server

    but end u with following errors

    2016-04-12 11:46:03.57*** Error: Could not retrieve copy settings for secondary ID '6ad12750-ac30-433b-8f3b-b2766b36bc23'.(Microsoft.SqlServer.Management.LogShipping) ***
    2016-04-12 11:46:03.58*** Error: Failed to connect to server QASQL.(Microsoft.SqlServer.ConnectionInfo) ***
    2016-04-12 11:46:03.58*** Error: Login failed for user 'xxxxxxxx'.(.Net SqlClient Data Provider) ***
    2016-04-12 11:46:03.58----- END OF TRANSACTION LOG COPY     -----

    0 0

    Environment: One Head Office (HO) and 2 Stores (S1 and S2), SQL Server 2008 R2


    I need to exclude column Password (varchar (30)) from merge replication on table Users. The Password column needs to be local to where it is originally created (HO or S1 or S2). The POS application requires Password column in Users table to authenticate users. We need this column to be replicated as NULL on other locations.

    Things I tried:

    I excluded column Password from merge publication on table Users but when the snapshot agent works at S1 or S2 for the first time, it drops this column at subscribers. We need this column there.

    I tried to ADD COLUMN back after snapshot is applied using snapshot post snapshot script but it fails saying that objects can't be altered at subscriber.

    Any solution?


    0 0


    I have a SQL replication server working fine for years. I had the need to add a varbinary(max) to a table where the data is filled on distributor. When the data is replicated, the most the of times the filed is filled with null, replacing the original data on both sides. Any tip? <o:p></o:p>

    Thanks and best regards.<o:p></o:p>

    Sql Server Publisher version 10.50.1617<o:p></o:p>

    0 0
  • 09/14/10--10:37: Log Shipping Error
  • hello there,

    I set up log shipping on a database server few months ago and it all worked fine, now I want to add another secondary server but I get the error below:

    *** Error: Could not retrieve copy settings for secondary ID '5c28a1a2-63f5-41c7-9c06-d179fd6ed753'.(Microsoft.SqlServer.Management.LogShipping) ***<nl/>2010-09-14 18:29:41.08 *** Error: The specified agent_id 5C28A1A2-63F5-41C7-9C06-D179FD6ED753 or agent_type 1 do not form a valid pair for log shipping monitoring processing.(.Net SqlClient Data Provider) ***<nl/>2010-09-14 18:29:41.09 *** Error: Could not log history/error message.(Microsoft.SqlServer.Management.LogShipping) ***<nl/>2010-09-14 18:29:41.09 *** Error: The specified agent_id 5C28A1A2-63F5-41C7-9C06-D179FD6ED753 or agent_type 1 do not form a valid pair for log shipping monitoring processing.(.Net SqlClient Data Provider) ***,00:00:01,0,0,,,,0

    I have read that the problem might be because I have to configure all the secondaries in one go , is this true?



    0 0

    Hello! I'm very new to Azure. I haven't had much luck finding a solution. Feel free to point me to another post. 

    We are trying to setup Transactional Replication from a local Server to an Azure Database.

    The publication and snapshot on the local server is created. When setting up the Push subscription to the Azure database, it looks like it creates successfully but looking at the replication monitor it fails.

    The error message is "Could not connect to Subscriber "{Servername} 

    Followed by these details:

    A network-related or instance-specific error has occurred while establishing a connection to SQL Server. Server is not found or not accessible. Check if instance name is correct and if SQL Server is configured to allow remote connections. 

    Login timeout expired (Source: MSSQLServer, Error number: HYT00)

    We are able to connect to the database with SSMS locally. It seems like remote connections are function.

    I have to be missing something pretty simple but I can't figure it out.

    Thanks for the help!


    0 0

    When I tried to use the CDC for Oracle by Attunity (4.0) to enable a Oracle table. I got this error message. And I can't find the SP in either [MSXDBCDC] database or CDC database. Will Microsoft be able to fix it?

    Could not find stored procedure 'sys.sp_cdc_parse_captured_column_list'

older | 1 | .... | 152 | 153 | (Page 154) | 155 | 156 | .... | 181 | newer