Hi Experts 

Currently I have transaction replication 2008R8(server A)  to 2014 pull subscription on 2014 (Server B).

Please note distribution database configured on Server B( subscriber site). This has configured initialisation using backup and restore to subscribers

 Tt's working fine.

Now I need to configure other subscriptions(Server B 2016 SP1 ) using same publisher Server A(2008 SP3). I need to configure other separate distribution server for Server C itself and use pull subscriptions.

Finally two distribution DBs on Each subscribers. Is that possible to achieve? Please note adding new sub Server C, will that impact to Server B (subscriptions) 

I am not sure  can we do one publisher and two subscribers.  If anyone know any  guide lines 

please note I need to do through initialisation using backup 

many thanks

On newly added subscription on 2016 Sp1 says “uninitialised subscription”  I tried “reinitialise subscription” but no luck. Any idea why is this and how to resolve use backup. When I check Agen jobs on Server C, I didnt find the job distributions  to subscriber job to start sync(log reader.) I am not sure why did't create the SQL Agent job for new subscript on the setps I did. 

Environment

I have transaction replication 2008R8(server A)  to 2014 pull subscription on 2014 (Server B).

Please note distribution database configured on Server B( subscriber site). This has configured initialisation using backup and restore to subscribers

Now I need to configure other subscriptions(Server B 2016 SP1 ) using same publisher Server A(2008 SP3). I need to configure other separate distribution server for Server C itself and should subscriptions.

Steps I did:

Add distribution database on Server C

Restore database full backup and log backup

Create subscriber on publisher(sever A) using log backup

Create  new subscriber on server C(This shows as uninitialised subscription

I have servers with different type of replication setting.

How to query or check the type of replication especially for  Bi-direction replication, p2p  replication and merge   ?

Thanks in advance for any helps.

I have this query to retrieve some info for the replication. However, i don't know how to get also the distributor info . If possible also can get the type of replication like bi-direction , p2p, merge, normal transaction replication and etc. Anyone know how to enchance the query below?

Thanks.

 select  distinct
 @@servername
,db_name() PublisherDB
, sp.name as PublisherName 
, s.dest_db as  SubscriberDB
, UPPER(srv.srvname) as SubscriberServerName
, s.subscription_type  --0 = push, 1= pull
from dbo.syspublications sp 
join dbo.sysarticles sa on sp.pubid = sa.pubid
join dbo.syssubscriptions s on sa.artid = s.artid
join master.dbo.sysservers srv on s.srvid = srv.srvid

Hi.

Here is the same question I have already asked, but this time the acceptance criteria would be not only to provide a solution for this, but more importantly to provide an explanation of why this happens, please. Here it goes:

I started getting the following issue on my Transactional Replication with a remote Distributor:

• Distribution Agent fails with the message 
  The row was not found at the Subscriber when applying the replicated DELETE command for Table '[dbo].[Active Session]' with Primary Key(s): [Server Instance ID] = 56, [Session ID] = 13 (Source: MSSQLServer, Error number: 20598)
• I got the SeqNo of the Transaction

I took the following action:

• Went to the Publisher to check the dbo.Active Session Table - was empty (as I guess it should be since there was a DELETE statement applied)
• Went to the Subscriber to check the dbo.Active Session Table - contained a row with the [Server Instance ID] = 56 and [Session ID] = 13
• Went to Distributor Server and queried sp_browsereplcmds with the xact_seqno obtained from the error log - this showed there are two Transactions (command_id 1 and 2), nr. 2 being the one for MSdel_dboActiveSession

I am wondering why the Replication says it cannot find the row when it is clearly exists right there, at the Subscriber dbo.Active Session Table (this started occurring even after I drop-create the entire Publication, and seems to be only relative to this Active Session Table)?

With thanks and kind regards,

Bogdan

We are currently on SQL Server 2016 SP2 EE.  Does anyone know if there are any specific replication related efficiencies on SQL Server 2017 or planned for SQL Server 2019?

Thanks.

We are using Oracle publisher to replicate data from oracle to SQL server,everything works well but i see the rowlevel triggers captures old data and new data also so i am seeing duplicates records in HREPL_POLL for two operations,any idea why its tracks old data?its slowing the process as we are having multiple records.As per the trigger logic whenever updates happens its stores old data and new data,can it update data basing on primary key?or its the expected behavior

/* Formatted on 8/30/2019 10:06:55 AM (QP5 v5.256.13226.35510) */
CREATE OR REPLACE TRIGGER HREPL_ARTICLE545_TRIGGER_ROW
   AFTER DELETE OR INSERT OR UPDATE
   ON "FLXUSER"."TEST"
   FOR EACH ROW
DECLARE
   Seq         NUMBER := 0;
   Stmt        NUMBER;
   Op1         NUMBER := 0;
   Op2         NUMBER := 0;
   EntryTime   NUMBER
                  := ROUND (TO_NUMBER ( (SYSDATE - HREPL.BaseTimeT) * 86400));
BEGIN
   IF HREPL.SQLORIGINATOR = FALSE
   THEN
      BEGIN
         SELECT HREPL_SEQ.NEXTVAL INTO Seq FROM DUAL;

         IF     UPDATING
            AND (   :old."ID" != :new."ID"
                 OR :old."NUM" != :new."NUM")
         THEN
            SELECT HREPL_STMT.CURRVAL INTO Stmt FROM DUAL;

            Op1 := '15';
            OP2 := '16';
         ELSE
            IF INSERTING
            THEN
               Op2 := '2';
            ELSIF DELETING
            THEN
               Op1 := '1';
            ELSE
               Op1 := '3';
               Op2 := '4';
            END IF;
         END IF;

         IF UPDATING OR DELETING
         THEN
            INSERT INTO HREPL_ARTICLE545LOG_1
                 VALUES (Seq,
                         Stmt,
                         Op1,
                         0,
                         EntryTime,
                         :old."ID",
                         :old."NUM");
         END IF;

         IF UPDATING OR INSERTING
         THEN
            INSERT INTO HREPL_ARTICLE545LOG_1
                 VALUES (Seq,
                         Stmt,
                         Op2,
                         0,
                         EntryTime,
                         :new."ID",
                         :new."NUM");
         END IF;
      END;
   END IF;
END;
/

Kiran

Hi All,

There is replication setup between SQL & Aurora in our environment. And its reported that the data is not matching between them. I have less experience in troubleshooting SQL replication issues. Also have no idea on sql-aurora replication setup & how it works.

The publisher & distributor is a SQL DB and subscriber is an Aurora DB in this case. I could just see the log reader agent running on SQL. Replication type - transactional replication.

Verified the below:

Checked the log reader agent status - its running fine. And every time I refresh I could see the updated time in the last action time with message as '1 transaction with 1 command delivered'. Also, I see lot entries stating ''approximately xxx log records have been scanned n pass #4, 0 of which were marked for replication". No other errors found under log reader history & also could see the 'xact_seqno' which gives the transaction number of last processed transaction continuously changing.

Under replication monitor, it’s not showing the subscription details as the subscriber is Aurora. So unable to verify any issues from distributor to subscriber end. Unable to check the no.of undistributed commands as well.

Seems there is a job running in Aurora which pulls the data & it’s in not working.

Could someone let me know what should be cause for data not being replicated & also tell me the other checks that needs to be done from SQL or Aurora end on this.

Thank You.

We are getting below error in SQL 2008 R2 MERGE REPLICAITON

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.

even after changing below seeting also no use.

USE master
exec sp_changedistributor_property
    @property = N'heartbeat_interval',
    @value = 5;
GO

Adding new articles (new tables) to replicate.

This is the process I followed which worked the last time I used it.

•Publisher (REPL_ISIS_APPS) --> Properties
•Articles page
•Click off ‘Show only checked articles in the list’
•Click on extra tables to add
•Click on OK
•Publisher (REPL_ISIS_APPS) --> View Snapshot Agent Status
•On View Snapshot Agent Status page click on Start

On the last step an error message is displayed.

Error message reads :-
BEGIN
The Agent could not be started

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

Could not find regular snapshot job for specified publication 'REPL_ISIS_APPS'.
Supply either @job_id or @job_name to identify the job.
Changed database context to 'ISIS'. (Microsoft SQL Server, Error 20678)
END

Q1) Does anyone know what caused this error?
Q2) Is there anyway to fix this error?
Q3) Would the option 'Reinitialize All Subscriptions' (with Use a new snapshot and generate the new snapshot now) correct this issue or make the issue worse?

At present all tables replicate (except the new ones I want to replicate) fine. What I don't want is to be in a situation where things stop replicating all together.

I have tried searching the internet for resolutions to this but I cannot seem to find this exact scenario.

Can you help?

Regards,
Richard.

I have configured tracer tokens  on my distributed database which is in system database on by distributor instance.

i want to move the distributed database to another instance database.

is it possible ?

how can we do that ?

Microsoft SQL Server 2017 (RTM) - 14.0.1000.169 (X64)   Aug 22 2017 17:04:49   Copyright (C) 2017 Microsoft Corporation  Enterprise Edition: Core-based Licensing (64-bit) on Windows Server 2016 Standard 10.0 <X64> (Build 14393: ) (Hypervisor) 

on the server I get:

TITLE: New Publication Wizard
------------------------------

SQL Server is unable to complete the New Publication Wizard.

For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft%20SQL%20Server&ProdVer=15.0.18142.0&EvtSrc=Microsoft.SqlServer.Management.UI.PubWizardErrorSR&EvtID=CantCompleteCreatePubWizard&LinkId=20476

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

Could not load file or assembly 'Microsoft.SqlServer.Replication.dll' or one of its dependencies. The specified module could not be found. (Microsoft.SqlServer.Rmo)

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

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

from my PC:

I can create and delete merge replications with no errors. however, when I create a transactional replication, attempts to delete it yields though it does delete the replication even when I did not create a snapshot:

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

Could not delete publication 'tashtit'.

For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft%20SQL%20Server&ProdVer=14.0.17199.0&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)

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

Only one Log Reader Agent or log-related procedure (sp_repldone, sp_replcmds, and sp_replshowcmds) can connect to a database at a time. If you executed a log-related procedure, drop the connection over which the procedure was executed or execute sp_replflush over that connection before starting the Log Reader Agent or executing another log-related procedure.
Only one Log Reader Agent or log-related procedure (sp_repldone, sp_replcmds, and sp_replshowcmds) can connect to a database at a time. If you executed a log-related procedure, drop the connection over which the procedure was executed or execute sp_replflush over that connection before starting the Log Reader Agent or executing another log-related procedure.
Changed database context to 'tashtit'. (Microsoft SQL Server, Error: 18752)

For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft%20SQL%20Server&ProdVer=14.00.1000&EvtSrc=MSSQLServer&EvtID=18752&LinkId=20476

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

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

it is followed by:

TITLE: Publication Properties
------------------------------

Cannot save Peer conflict detection properties.

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

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

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

The publication 'tashtit' was already enabled for peer-to-peer conflict detection.
Changed database context to 'tashtit'. (Microsoft SQL Server, Error: 22828)

For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft%20SQL%20Server&ProdVer=14.00.1000&EvtSrc=MSSQLServer&EvtID=22828&LinkId=20476

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

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

if I try and change the transactional replication to p2p, I get the following error:

TITLE: Publication Properties
------------------------------

Cannot save Peer conflict detection properties.

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

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

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

A .NET Framework error occurred during execution of user-defined routine or aggregate "sp_MSscriptcustominsproc_sqlclr": 
System.Data.SqlClient.SqlException: String or binary data would be truncated.
System.Data.SqlClient.SqlException: 
   at Microsoft.SqlServer.Server.SmiEventSink_Default.DispatchMessages(Boolean ignoreNonFatalMessages)
   at Microsoft.SqlServer.Server.SqlPipe.SendResultsRow(SqlDataRecord record)
   at Microsoft.SqlServer.Replication.SqlPipeTextWriter.FlushRow()
   at Microsoft.SqlServer.Replication.SqlPipeTextWriter.WriteLine(String value)
   at Microsoft.SqlServer.Replication.SqlCodeGeneration.TransCustomProcedureScripter.ScriptInsertProcedure(TextWriter outputTextStream)
   at Microsoft.SqlServer.Replication.TransSqlClrCodeGenerators.GenerateArticleCustomProcedureScript(SqlDataReader dataReader)
   at Microsoft.SqlServer.Replication.TransSqlClrCodeGenerators.ProcessMetadataResults(SqlDataReader dataReader)
   at Microsoft.SqlServer.Replication.TransSqlClrCodeGenerators.GatherMetadataAndGenerateScript()
   at Microsoft.SqlServer.Replication.TransSqlClrCodeGenerators.ScriptCustomProcedure(SqlInt32 articleId, SqlString publisher, SqlString publisher_type, CustomStoredProcedureType customStoredProcedureType)
   at Microsoft.SqlServer.Replication.TransSqlClrCodeGenerators.sp_MSscriptcustominsproc_sqlclr(SqlInt32 articleId, SqlString publisher, SqlString publisher_type)
.
A .NET Framework error occurred during execution of user-defined routine or aggregate "sp_MSscriptcustomupdproc_sqlclr": 
System.Data.SqlClient.SqlException: String or binary data would be truncated.
System.Data.SqlClient.SqlException: 
   at Microsoft.SqlServer.Server.SmiEventSink_Default.DispatchMessages(Boolean ignoreNonFatalMessages)
   at Microsoft.SqlServer.Server.SqlPipe.SendResultsRow(SqlDataRecord record)
   at Microsoft.SqlServer.Replication.SqlPipeTextWriter.FlushRow()
   at Microsoft.SqlServer.Replication.SqlPipeTextWriter.WriteLine(String value)
   at Microsoft.SqlServer.Replication.SqlCodeGeneration.TransCustomProcedureScripter.ScriptUpdateProcedure(TextWriter outputTextStream)
   at Microsoft.SqlServer.Replication.TransSqlClrCodeGenerators.GenerateArticleCustomProcedureScript(SqlDataReader dataReader)
   at Microsoft.SqlServer.Replication.TransSqlClrCodeGenerators.ProcessMetadataResults(SqlDataReader dataReader)
   at Microsoft.SqlServer.Replication.TransSqlClrCodeGenerators.GatherMetadataAndGenerateScript()
   at Microsoft.SqlServer.Replication.TransSqlClrCodeGenerators.ScriptCustomProcedure(SqlInt32 articleId, SqlString publisher, SqlString publisher_type, CustomStoredProcedureType customStoredProcedureType)
   at Microsoft.SqlServer.Replication.TransSqlClrCodeGenerators.sp_MSscriptcustomupdproc_sqlclr(SqlInt32 articleId, SqlString publisher, SqlString publisher_type)
.
A .NET Framework error occurred during execution of user-defined routine or aggregate "sp_MSscriptcustomdelproc_sqlclr": 
System.Data.SqlClient.SqlException: String or binary data would be truncated.
System.Data.SqlClient.SqlException: 
   at Microsoft.SqlServer.Server.SmiEventSink_Default.DispatchMessages(Boolean ignoreNonFatalMessages)
   at Microsoft.SqlServer.Server.SqlPipe.SendResultsRow(SqlDataRecord record)
   at Microsoft.SqlServer.Replication.SqlPipeTextWriter.FlushRow()
   at Microsoft.SqlServer.Replication.SqlPipeTextWriter.WriteLine(String value)
   at Microsoft.SqlServer.Replication.SqlCodeGeneration.TransCustomProcedureScripter.ScriptDeleteProcedure(TextWriter outputTextStream, Boolean reconciliation)
   at Microsoft.SqlServer.Replication.TransSqlClrCodeGenerators.GenerateArticleCustomProcedureScript(SqlDataReader dataReader)
   at Microsoft.SqlServer.Replication.TransSqlClrCodeGenerators.ProcessMetadataResults(SqlDataReader dataReader)
   at Microsoft.SqlServer.Replication.TransSqlClrCodeGenerators.GatherMetadataAndGenerateScript()
   at Microsoft.SqlServer.Replication.TransSqlClrCodeGenerators.ScriptCustomProcedure(SqlInt32 articleId, SqlString publisher, SqlString publisher_type, CustomStoredProcedureType customStoredProcedureType)
   at Microsoft.SqlServer.Replication.TransSqlClrCodeGenerators.sp_MSscriptcustomdelproc_sqlclr(SqlInt32 articleId, SqlString publisher, SqlString publisher_type)
.
Changed database context to 'tashtit'. (Microsoft SQL Server, Error: 6522)

For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft%20SQL%20Server&ProdVer=14.00.1000&EvtSrc=MSSQLServer&EvtID=6522&LinkId=20476

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

OK
------------------------------
TITLE: Publication Properties
------------------------------
it is followed by :

Cannot save Peer conflict detection properties.

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

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

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

The publication 'tashtit' was already enabled for peer-to-peer conflict detection.
Changed database context to 'tashtit'. (Microsoft SQL Server, Error: 22828)

For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft%20SQL%20Server&ProdVer=14.00.1000&EvtSrc=MSSQLServer&EvtID=22828&LinkId=20476

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

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

when I cancel, the properties show p2p enabled.







???

Hi,

I'm having a SQL Server Replication which has a Publisher and Distributor in the same server and 7 Subscribers in different physical locations. This works fine (minor problems time to time) for couple of years and recently one subscriber server is started to give troubles as follows.

01. All the agent jobs related to pull subscriptions were gone(missing). I generated scripts from another sever and managed to run few subscriptions running. but failed for some subscriptions.

02. Tried to create new subscribers for the same server after failures. But failing to create new subscribers.

 > When I check in the Replication Monitor it shows like follows,

     > Tried to access the publishing servers share with the server name and works fine.

     > Date/time is equal in both servers.

Pls help me with a solution to overcome from this problem,

Thanks in advance,

Chama

 To monitor the replication pending commands, I understand that there is another better way to check.

 Anyone can advise on this way of the related checking ?=>  all commands that are greater than the earliest/MIN trans_seqno of the publication for all subscribers in the distribution agent history table.

Appreciate if someone can show the query statement for above.

Thanks

Hello.

I would like to kindly ask for your thoughts with the following:

1) I have a Transactional Replication (TR) with a remote Distributor (DIS), between the Source (PUB) and the Subscriber (SUB) Servers

2) There are 8 Databases being replicated

3) All three servers are on Azure VMs

4) I have not (intentionally :) ) changed any authorizations on any of the replication-related users (both local users and sql users)

From yesterday, as following the same cue, all of the replications started failing with the same error message:

...

2019-09-10 10:17:37.527 Connecting to Subscriber 'SUB'
2019-09-10 10:17:38.152 Initializing
2019-09-10 10:17:40.574 Agent message code 21100. The distribution agent failed to create temporary files in 'C:\Program Files\Microsoft SQL Server\140\COM' directory. System returned errorcode 5.

When I went to see the state of the Jobs on DIS, I found that all of the Distribution Agents were retrying and retrying, always resulting in the same error.

Since the error message implied that the Agent was connecting to the SUB, I went there to see if the repl_distribution Account has the right permissions - and it did.

However, when I went to the DIS Server to check the same, I did not find that the repl_distribution Account was authorized for this Folder, and once I did this, the replication came back up.

Now I am a bit confused and have the following questions:

1) What is the 140\COM Folder used for in the first place?

2) Could it be that all of this time the Agent never needed to create anything on the DIS side (but only on the SUB side), but now all of a sudden it needs to create some temp files on the DIS Server?

3) On the other hand, if it was always enabled on the DIS side (since the replication was working for the past two months), how can it be that the Distribution Account was removed?

4) Can a restart of the VM hosting the DIS Server cause this? Can a change in Active Directory and/or an update of the DNS Server(s) cause this?

5) Have there been any updates on the SQL Server's (Transactional) Replication feature yesterday?

With thanks and kind regards,

Bogdan

Hi,

I am trying to add extra subscriber on already established transnational replication using below code.

TransSubscription subscription = new TransSubscription();
                        subscription.PublicationName = this.PublicationName;
                        subscription.SubscriberName = subscriber.SubscriberServerName;
                        subscription.DatabaseName = this.PublicationDBName;

                        subscription.ConnectionContext = this.ServConn;
                        subscription.SubscriptionDBName = subscriber.SubscriptionDBName;
                        subscription.CreateSyncAgentByDefault = true;
                        subscription.SubscriberSecurity.SqlStandardLogin = subscriber.SubscriptionLogin;
                        subscription.SubscriberSecurity.SqlStandardPassword = subscriber.SubscriptionLoginPassword;
                        subscription.SubscriberSecurity.WindowsAuthentication = false;
                        if (!subscription.IsExistingObject)
                        {
                            if (!this.IsSnapshotGenerated)
                                GenerateFullSnapShot();

            
                            subscription.Create();

But iam facing the the below issue , that is also on first run  from next run onwards could able to configure secondary subscription.

Hi Team

I have TBs of SQL DBs on Azure IAAS. I would like to have these production DBs to be replicated to my Pre prod IAAS SQL environment on daily or weekly intervals. Since DBs are in TBs I don't want to incur huge replication time. During replication I would also like to do some data scrubbing for sensitive info. I have already see Azure Recovery Vault for backup etc. any other best alternative anyone can suggest? appreciate your help! Thank you