Transactional replication issues

SQL 2012 for both servers.
Basically I would like to set up a (transactional I think) replication of few articles from serverA to serverB.
I created publication and I created subscription (push) related to serverB.
In the past, on a sql 2005 instance I used distrib.exe on publication server to deliver changes on subscriber and it worked well.
On sql 2012, running distrib.exe does not deliver anything .. and I don't understand why.
Please remember that my main goal is to deliver changes in articles from serverA to serverB "on demand".
Can you please help ?
Any help appreciated, best regards.

I configured transactional replication because it seems the best choice in my scenario.
"C:\Program Files\Microsoft SQL Server\110\COM\DISTRIB.EXE" -Subscriber %Subscriber%
-SubscriberDB %SubscriptionDB% -SubscriberSecurityMode 1 -Publication %Publication%
-Publisher %Publisher% -PublisherDB %PublicationDB% -Distributor %Publisher%
-DistributorSecurityMode 1 -Continuous -SubscriptionType 0 -SubscriptionStreams 4 Isn't "-Continuos" the contrary of "on demand" ? Do I really need it ?However in my command line instructions I miss these 3 parameters: -Continuous -SubscriptionType 0 -SubscriptionStreams 4however it worked well in the past also without them.I deleted replication jobs (cleanup ... ) too because I would like to start from scratch but now they are not recreatec.Thanks for help.-
The distrib.exe works only with transactional and snapshot replication. I hope you are configured replication with Transactional replication topology.
It should work in the same way that it used to work with SQL 2005.
Reference:-
http://technet.microsoft.com/en-us/library/ms151169.aspx
Push subscriptions can be synchronized programmatically and on-demand by invoking the appropriate replication agent executable file from the command prompt. The replication agent executable file that is invoked will depend on the type of publication
to which the push subscription belongs.
To start the Distribution Agent to synchronize a push subscription to a transactional publication
From the command prompt or in a batch file at the Distributor, execute distrib.exe. Specify the following command-line arguments:
-Publisher
-PublisherDB
-Distributor
-Subscriber
-SubscriberDB
-SubscriptionType = 0
REM -- Declare the variables.
SET Publisher=%instancename%
SET Subscriber=%instancename%
SET PublicationDB=AdventureWorks2012
SET SubscriptionDB=AdventureWorks2012Replica
SET Publication=AdvWorksProductsTran
REM -- Start the Distribution Agent with four subscription streams.
REM -- The following command must be supplied without line breaks.
"C:\Program Files\Microsoft SQL Server\110\COM\DISTRIB.EXE" -Subscriber %Subscriber%
-SubscriberDB %SubscriptionDB% -SubscriberSecurityMode 1 -Publication %Publication%
-Publisher %Publisher% -PublisherDB %PublicationDB% -Distributor %Publisher%
-DistributorSecurityMode 1 -Continuous -SubscriptionType 0 -SubscriptionStreams 4
http://technet.microsoft.com/en-us/library/ms147886.aspx
-Prashanth

Similar Messages

Transactional replication issue

Hi,
i have configured transactional replication with separate distributor server, the data copied and snapshot delivered,last 2days it is running, publisher to distributor is good, but distributor to subscriber it show heavy latency and it is showing critical
status,when i see in the replication monitor, it shows undistributed commands 65000 records, when i see in snchronization status it showing 'deliverimg replication', when i compare to publisher and subscriber records difference is there, i checked the file
tranfer speed 100mbps and bandwidth speed is als good....how to fix it

Was there any issue which caused replication to stop for some time or was there any huge updates that happened at publisher..
Take a look at this link..
http://blogs.msdn.com/b/chrissk/archive/2009/05/25/transactional-replication-conversations.aspx
It explains very clearly to troubleshoot this.. You might only have to look at the distribution agent latency part, as per your description...
Apart from this, check if there are any triggers in the subscriber end which is making the subscriber updates slow..
Regards, Ashwin Menon My Blog - http:\\sqllearnings.com

Transactional Replication Stalled.

Hi,
We are having a Transactional replication issue where the Data does not get replicated and the log Just keeps grawing.
Last week we had an accidental load 15 Million records, on one of the T replication enabled Db's .Then the replication stopped working i mean i look at the replication monitor it says NO transactions to replicate but we have a lot difference
with the DATA.I also see that the logfile file for the DB is growing.
1.I did a few things like stopping the log reader and restarting.
2.Reinitialize the Snapshot ,the snapshot is taken but is not being applied to the subscriber .No error msg that i can see.
So had to drop the replication entirely , shrink the log and recreate it adding few bunches of articles, creating a snapshot for them wait until they are applied and then add the other articles which worked fine for few days , and DB replication
stopped again and log started growing.This time it is also effecting other replications this time too.
I am running out of options can some one plz help!
THanks,
Jack

That message means the log reader agent is going through the log reading commands from it. If your ETL operation does large batch operations replication many not be able to keep up. You might need to break these batches up into smaller batches - batchsize
works well here.
Another thing to consider is to do your ETL operation on both sides. This works well if the only source of changes occurs from the ETL process - then you would not publish these tables.
If not - think about use MaxCmdsInTran - you can set this to something like 10,000 which means that if you do a million row update - the log reader agent will start to read the commands out of the log for every 10,000 changes and replicate them to the subscriber
- before the transaction is committed on the publisher.
This is a command that you can put in your log reader agent profile so you can turn it off when the ETL process is done and replicated.
looking for a book on SQL Server 2008 Administration?
http://www.amazon.com/Microsoft-Server-2008-Management-Administration/dp/067233044X looking for a book on SQL Server 2008 Full-Text Search?
http://www.amazon.com/Pro-Full-Text-Search-Server-2008/dp/1430215941

Error while setting up Transactional Replication

Hi Team,
I am getting below error while configuring Transactional Replication.
Specifically, when I started configuring the distributor that when I am getting below error. I am getting this in GUI as well TSQL script as well.
SQL Server could not configure 'TEST-PC\SQL2K8' as a Distributor.
ADDITIONAL INFORMATION:
An exception occurred while executing a Transact-SQL statement or batch. (Microsoft.SqlServer.ConnectionInfo)
Destination path D:\SQL2K8DATA is not valid. Unable to list directory contents. Specify a valid destination path.
Changed database context to 'master'. (Microsoft SQL Server, Error: 14430)
Background of the error.
========================
I installed 3 sql instances of "SQL Server 2008 Developer edition, SP3 (x64)".
I started configuring a remote distributor using one of the instance and error started popping up.
Initially I had the replication running fine and I removed it and tried to reconfigure distributor thats when the error starting popping up.
The folder physically exists and the service account has full permissions and I have logged in as service account and trying to setup Transactional Replication.
He is local administrator on the box and also sysadmin login at sql server level.
Not sure why this error is popping up.....
After wasting a lot of time. I tried to install 3 new fresh instances with same service pack level i.e. sp3, but still the error remains the same.
Appreciate if anyone can guide me resolving this issue.
Thank you.

Hi Brandon,
I generated the script and tried again. No Luck. It is throwing error at creation of distribution database itself i.e. exec sp_adddistributiondb .
/****** Scripting replication configuration. Script Date: 2/25/2014 11:43:31 AM ******/
/****** Please Note: For security reasons, all password parameters were scripted with either NULL or an empty string. ******/
/****** Installing the server as a Distributor. Script Date: 2/25/2014 11:43:31 AM ******/
use master
go
exec sp_adddistributor
@distributor = N'TEST-PC\S2',
@password = N'123'
GO
exec sp_adddistributiondb
@database = N'distribution',
@data_folder = N'C:\Program Files\Microsoft SQL Server\MSSQL10.S2\MSSQL\Data',
@log_folder = N'C:\Program Files\Microsoft SQL Server\MSSQL10.S2\MSSQL\Data',
@log_file_size = 2,
@min_distretention = 0,
@max_distretention = 72,
@history_retention = 48,
@security_mode = 1
GO
Error Message :
Msg 14430, Level 16, State 1, Procedure sp_adddistributiondb, Line 227
Destination path C:\Program Files\Microsoft SQL Server\MSSQL10.S2\MSSQL\Data is not valid. Unable to list directory contents. Specify a valid destination path.
use [distribution]
if (not exists (select * from sysobjects where name = 'UIProperties' and type = 'U '))
   create table UIProperties(id int)
if (exists (select * from ::fn_listextendedproperty('SnapshotFolder', 'user', 'dbo', 'table', 'UIProperties', null, null)))
   EXEC sp_updateextendedproperty N'SnapshotFolder', N'\\TEST-PC\repldata', 'user', dbo, 'table', 'UIProperties'
else
   EXEC sp_addextendedproperty N'SnapshotFolder', N'\\TEST-PC\repldata', 'user', dbo, 'table', 'UIProperties'
GO
exec sp_adddistpublisher @publisher = N'TEST-pc\s1',
@distribution_db = N'distribution',
@security_mode = 1,
@working_directory = N'\\TEST-PC\repldata',
@trusted = N'false',
@thirdparty_flag = 0,
@publisher_type = N'MSSQLSERVER'
GO

Taking snapshot of oracle tables to sql server using transactional replication is taking a long time

Hi All,
I am trying to replicate around 200 oracle tables onto sql server using transaction replication and it taking a long time i.e the initial snapshot is taking more than 24 hrs and it still going on.
Is there any way to replicate those these tables faster?
Kindly help me out..
Thanks

Hi,
According to the description, I know the replication is working fine. But it is very slow.
1. Check the CPU usage on Oracle publisher and SQL Server. This issue may due to slow client processing (Oracle performance) or Network performance issues.
2. Based on SQL Server 2008 Books Online ‘Performance Tuning for Oracle Publishers’ (http://msdn.microsoft.com/en-us/library/ms151179(SQL.100).aspx). You can enable the transaction
job set and follow the instructions based on
http://msdn.microsoft.com/en-us/library/ms147884(v=sql.100).aspx.
2. You can enable replication agent logging to check the replication behavior. You may follow these steps to collect them:
To enable Distribution Agent verbose logging. Please follow these steps:
a. Open SQL Server Agent on the distribution server.
b. Under Jobs folder, find out the Distribution Agent.
c. Right click the job and choose Properties.
d. Select Steps tap, it should be like this:
e. Click Run agent and click Edit button, add following scripts by the end of scripts in the command box:
-Output C:\Temp\OUTPUTFILE.txt -Outputverboselevel 2
f. Exit the dialogs
For more information about the steps, please refer to:
http://support.microsoft.com/kb/312292
Hope the information helps.
Tracy Cai
TechNet Community Support

Transactional replication very slow with indexes on Subscriber table

I have setup Transactional Replication for one of our databases where one table with about 5mln records is replicated to a Subsriber database. With every replication about 500-600.000 changed records are send to the Subscriber.
Since one month I see very strange behaviour when I add about 10 indexes to the Subscriber table. As soon as I have added the indexes replication speed becomes extremely slow (almost 3 hours for 600k records). As soon as I remove the indexes the replication
is again very fast, about 3 minutes for the same amount of records.
I've searched a lot on the internet to solve this issue but can't find any explaination for this strange behaviour after adding the indexes. As far as I know it doesn't have to be a problem to add indexes to a Subscriber table, and it hasn't been before on
another replication configuration we use.
Some information from the Replication Log:
With indexes on the Subscriber table
Total Run Time (ms) : 9589938 Total Work Time : 9586782
Total Num Trans : 3 Num Trans/Sec : 0.00
Total Num Cmds : 616245 Num Cmds/Sec : 64.28
Total Idle Time : 0
Writer Thread Stats
Total Number of Retries : 0
Time Spent on Exec : 9580752
Time Spent on Commits (ms): 2687 Commits/Sec : 0.00
Time to Apply Cmds (ms) : 9586782 Cmds/Sec : 64.28
Time Cmd Queue Empty (ms) : 5499 Empty Q Waits > 10ms: 172
Total Time Request Blk(ms): 5499
P2P Work Time (ms) : 0 P2P Cmds Skipped : 0
Reader Thread Stats
Calls to Retrieve Cmds : 2
Time to Retrieve Cmds (ms): 10378 Cmds/Sec : 59379.94
Time Cmd Queue Full (ms) : 9577919 Full Q Waits > 10ms : 6072
Without indexes on the Subscriber table
Total Run Time (ms) : 89282 Total Work Time : 88891
Total Num Trans : 3 Num Trans/Sec : 0.03
Total Num Cmds : 437324 Num Cmds/Sec : 4919.78
Total Idle Time : 0
Writer Thread Stats
Total Number of Retries : 0
Time Spent on Exec : 86298
Time Spent on Commits (ms): 282 Commits/Sec : 0.03
Time to Apply Cmds (ms) : 88891 Cmds/Sec : 4919.78
Time Cmd Queue Empty (ms) : 1827 Empty Q Waits > 10ms: 113
Total Time Request Blk(ms): 1827
P2P Work Time (ms) : 0 P2P Cmds Skipped : 0
Reader Thread Stats
Calls to Retrieve Cmds : 2
Time to Retrieve Cmds (ms): 2812 Cmds/Sec : 155520.63
Time Cmd Queue Full (ms) : 86032 Full Q Waits > 10ms : 4026
Can someone please help me with this issue? Any ideas?
Pim

Hi Megens:
Insert statement might be slow with not only indexes and few others things too
0) SQL DB Blocking during inserts
1) If any insert triggers are existed
2) Constraints - if any
3) Index fragmentation
4) Page splits / fill factor
Without indexes inserts will be fast because, each time when new row going to insert to the table, SQL Server will do
1) it will check for the room, if no room page splits will happen and record will placed at right place
2) Once the record updated all the index should be update
3) all these extra update work will cause can make insert statement bit slow
Its better to have index maintenance jobs frequently to avoid fragmentation.
If every thing is clear on SQL Server Side, you need look up on DISK IO, N/W Latency between the servers and so on
Thanks,
Thanks, Satish Kumar. Please mark as this post as answered if my anser helps you to resolves your issue :)

Transactional Replication: Alter view changes are not reflect on Subscription database

Hi All,
we are configured transactional replication in our environment on sql server 2008 R2 , Yesterday I made a view alter on publisher database the view also present in replicated articles but unfortunately the changes not reflect in subscription, I already have
checked the : Replicate Schema change option in Subscription option its also true, there is not latency exist in replication monitor , i have checked the blocking on subscription and publication. one more thing I tested the changes on replicated table its
working fine
Please help me to fix the issue.
Regards,
Pawan Singh
Thanks

Hi Pawan,
According to your description, the alter on the view in publication doesn't be reflected in subscription database. As my analysis, the issue could be caused by that the distribution agent job doesn’t run after altering the view.
I make a test on my computer, and set up transactional replication to replicate tables and views. Firstly, when creating subscription, I set the distribution agent job ‘Run continuously’(as the screenshot below), and alter the view in publication database,
then the change is successfully reflected to the corresponding view in subscription database.
However, I also make another test with setting the distribution agent job ‘Run on demand only’(It is determined by you), and find that it is not reflected to subscription database unless I run the distribute agent job manually.
The distribution agent is used to read the updated transactions written to the distribution database and applies the change to the subscription database, so please check if your distribution agent job runs after you alter the view. If not, please run the
job and check if the issue still occurs.
Regards,
Michelle Li

How to verify replication is in sync or not in transactional replication

Hi Freinds,
How o verify whether transactional replication is in sync.
Thanks in advancce.
Shashikala

They are many ways,
Monitoring Replication with Replication Monitor
http://msdn.microsoft.com/en-us/library/ms151780%28v=sql.105%29.aspx
Through Programing:
http://msdn.microsoft.com/en-us/library/ms147874%28v=sql.105%29.aspx
By row counts
http://www.sqlservercentral.com/articles/Replication/70545/
By using Validate option
http://sqlblog.com/blogs/maria_zakourdaev/archive/2012/03/06/transactional-replication-are-you-sure-your-data-is-totally-synchronized.aspx
Thanks,
Thanks, Satish Kumar. Please mark as this post as answered if my anser helps you to resolves your issue :)

Transactional Replication sp_MSupd RUNNABLE and never ends

Hello,
I came across not understandable problem connecting transactional pull replication. Once or twice a month I have a problem that stored procedure on subscription server (sp_MSupd) cannot be finished. It is not blocked by any other session and does not have
any wait type. It simply hangs and remains in task status RUNNABLE. The only one way to recover the replication is initilizing it from backup or snapshot. Do you have any suggestions. Have you faced similiar problem?

Hi, Lydia
Thank you for your reply. What do you mean that this is the "busy update on the publication". Could you please describe it in more details? Does it mean that on the publisher there was a huge update on a huge amount of rows? On the Publisher to
Distributor History I can see that there is no problem. All transactions are delivered without any delays (few seconds). But in Distributor to Subscriber History I have all actions completed in few seconds except the last one that hangs. How can I check if
it is the "busy update on the publication" problem? What should be done if it hangs more than few hours?
I found out that sp_MSget_repl_commands hangs on Publisher for remote Subscriber. It hangs with ASYNC_NETWORK_IO
Hi KirKuz,
I originally mean distribution agent reader &writer latency issue, and you can use SQL profiler or DMVs to examine in detail the Transaction Replication, which is described in this
blog.
Regarding to ASYNC_NETWORK_IO, based on my research, it's simply waiting for something external to SQL. The drive with your distribution database might be a bottleneck of such issue, or maybe the distribution tables are getting too large. Please check your
disk performance, also check your indexes on the replication tables for fragmentation.
Here is a similar thread for your reference.
https://social.msdn.microsoft.com/Forums/sqlserver/en-US/d0117651-f94c-488a-83e8-30038e38d510/transactional-replication-slow-running-spmsgetreplcommands?forum=sqlreplication
Thanks,
Lydia Zhang
Lydia Zhang
TechNet Community Support

Transactional replication triggers disabled after server restart

Hello Everyone,
I have been facing this issue since couple of days. I have configured transactional replication with updatable subscriber in sql server 2008 R2. It was working fine till date. Recently we are facing an issue where subscriber whenever restarts, one
of the table's replication triggers(insert, update and delete) are disabled automatically. We have to manually enable all the triggers for that table. Other tables are working fine. Please help. Thanks in advance.
Regards,
Sai

Have you checked information from replication monitor?
You should disable all triggers because you don't want SQL Server to fire the trigger on the Subscriber database when the database receives an insert, update, or delete operation. Because the trigger has already fired on the Publisher database, firing the trigger
on the Subscriber database might repeat the transaction.
http://technet.microsoft.com/en-us/library/ms151718(v=sql.110).aspx
http://msdn.microsoft.com/en-us/library/ms152529.aspx

Transactional replication cross-country - where should distributor go?

Hi All,
SQL Server 2005 standard edition using transactional replication from Montreal to Vancouver.
Our current distributor is region-based, so it is within our data centre in Toronto. So basically it goes MTL--> TO -> VAN.
However, i'm thinking that the extra step to TO is unnecessary because its in another physical location and the extra hope/latency from MTL-->TO before going to VAN adds overhead..
I know that a separate distributor is best practice but in this case, 3 physical locations, each with ~50ms latency between each one, is it better to have the publisher and distributor on the same server (in MTL) and then just go directly to the subscriber
(VAN)? We don't have enough resource within MTL to build a separate distributor there so it would go on the same server as publisher.
DB size is 135 MB, all tables synchronizing.
Thanks in advance for any input.

The network hop is normally insignificant when replicating locally, but it can be an issue when replicating across a WAN. IT should be local not only to factor out the network latency but also to simplify your recovery and DR plans.
A remote distributor is required when you have high cpu issues on your publisher. If you don't have this or your workload is not characterized by high cpu you will be able to get away with a local distributor.
looking for a book on SQL Server 2008 Administration?
http://www.amazon.com/Microsoft-Server-2008-Management-Administration/dp/067233044X looking for a book on SQL Server 2008 Full-Text Search?
http://www.amazon.com/Pro-Full-Text-Search-Server-2008/dp/1430215941

Transactional Replication Not replicating non-clustered Indexes

Hi
I have created a transactional replication.I am sure that I have configured it to replicate Non-Clustered indexes,
but It does not do so.
I tried several times to reinitialize the subscription,but still no luck.
Regards

It is True for sure.
But the problem is solved.I had to wait until the Initialize process get completed.
But I am sure that this problem happened before.Sometimes it works fine but sometimes not.
Hi ArashMasroor,
According to your description, it seems that you encounter the issue that non-clustered indexes property is reset to “False” sometimes.
To work around this issue, you can use a post-replication SQL script to create the indexes. Whatever articles you’re publishing open up the indexes drop down list of the article in object explorer, right-click on an index and levitate over Script Index as,
then Create-to, then click New Query Window editor.
Up will pop up a new query window with the resulting index. Work your way through all the indexes on all the articles of the publication, copy and pasting just the create index line and below of each script, pull them all together into one query window.
Once you’re done find a safe folder somewhere on your hard drive and save the SQL query as an .sql file with a sensible name. Then you can execute this script after applying the Snapshot. For more details, please review this
blog.
There is also a similar thread for your reference.
https://social.msdn.microsoft.com/Forums/sqlserver/en-US/b0f3870d-1a65-4384-a17b-96825ec5f098/transactional-replication-nonclustered-indexes-not-copying?forum=sqlreplication
Thanks,
Lydia Zhang
Lydia Zhang
TechNet Community Support

Unable to drop publication database from publisher server in transactional replication

Dear All,
we are getting one issue when the time of dropping publication database on publisher server in transactional replication in sql server 2008 r2.
TITLE: Microsoft SQL Server Management Studio
Could not delete publication 'dbname_Pubs'.
For help, click:
http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=10.50.1600.1&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)
Could not find stored procedure ''. (Microsoft SQL Server, Error: 2812)
For help, click:
http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=10.50.4000&EvtSrc=MSSQLServer&EvtID=2812&LinkId=20476
BUTTONS:
OK
mastanvali shaik

try this..
exec sp_removedbreplication N'<dbname>'
exec sp_droppublication @publication = N'<dbname>'
Raju Rasagounder Sr MSSQL DBA

Dropping existing subscriber from a pualisher who has multiple subscriber in Transactional Replication

Hi Everyone,
We have a transactional replication(one publisher and multiple subscribers). If I drop one of subscribers, will this cause any locking or performance problem for publisher or other subscribers? I am going to do that using SSMS.
Thanks
Aspet
A.G

Hi Mourmansk,
Agree with others，In addition, before you deleting Subscriber, we need to verify that Publisher define a source database where replication starts, Subscriber is the destination database where replication ends. If you want to drop a Subscriber, it means that
you should delete the related pull subscription or push subscription in transaction replication. Usually, for example, to delete a push subscription, you use
sp_dropsubscription on the publication database, and execute sp_subscription_cleanup to remove replication metadata in the subscription database. There is a similar issue about delete subscriber from replication, you can review it.
http://social.technet.microsoft.com/Forums/en-US/1354e29f-4904-46dd-8e64-d1150263ba7c/unable-to-drop-subscriber-from-replication?forum=sqlreplication
For more information, see：http://msdn.microsoft.com/en-us/library/ms151212.aspx
http://msdn.microsoft.com/en-us/library/ms151861.aspx
Regards,
Sofiya Li
Sofiya Li
TechNet Community Support

Noncovergence in transactional replication with updatable subscription

Hello all,
I have a Transactional replication with updatable subscription setup having 1 publisher and 3 subscribers. All the servers are SQL 2008 and have conflict resolution
policy set as subscriber wins. Of late, I have been observing data mismatch for few tables. Some tables have records but their column values doesn't match. Some records are there on one subscriber but missing on publisher and other subscribers. However replication
is running fine without any issue. I am trying to understand what could have caused this issue and how it could be avoided in future.
Do you guys have any idea what might be causing this and how to fix this?
Let me know if you need any further details.
FYI: There is no filter defined for any articles in replication.
Thanks,
Nainesh.

If these problem rows do not show up as conflicts you will need to create audit tables and triggers to determine why these rows are not being picked up for replication.
looking for a book on SQL Server 2008 Administration?
http://www.amazon.com/Microsoft-Server-2008-Management-Administration/dp/067233044X looking for a book on SQL Server 2008 Full-Text Search?
http://www.amazon.com/Pro-Full-Text-Search-Server-2008/dp/1430215941

Transactional replication issues

Similar Messages

Maybe you are looking for