Viewing 15 posts - 1 through 15 (of 41 total)
few possible issues here:- spaces in the login name at the end of login (when creating login or subscription).- some mistake with password provided for subscription- incorrectly...
February 13, 2019 at 10:06 am
If you have identity column on the table that property will be ALWAYS there. Even when table is not published. That property is part of any identity column (with or...
December 12, 2018 at 3:55 am
You doing full backup again after u changing back to FULL recovery
November 9, 2018 at 12:22 am
Backup log should should clear up the log and leave only one VLF active. AS far I see it most probably on your dry run u did not...
October 31, 2018 at 8:20 am
that may not be related to replication. Status=2 means that this VLFs is active (at given point at least one VLF need to be active). what log_reuse_wait says this time?
October 31, 2018 at 3:54 am
Transaction log backup won't affect replication at all. You can run transaction log backup without any issues. Yes once u backup the log you will need to run...
October 29, 2018 at 9:35 am
I do not think it is replication issue in that case.I believe you are running in full recovery model. I am assuming u created new db on new instance...
October 29, 2018 at 8:06 am
if we are talking about transactional the only place that the changes are logged is distribution database in msrepl_transactions and msrepl_commands. as Sue mentioned you can read these by using...
October 29, 2018 at 2:47 am
Did u check log_reuse_wait? Does log reader is working properly? (no errors?) Do you see data being replicated to Subscriber? What recovery u using on that published db?
October 29, 2018 at 2:24 am
Configuration 2 will be way to go. 1 publication adding second subscriber.The problem with Conf 1 is that you are creating new publication with same tables but from Replication...
March 22, 2018 at 8:35 am
Is the error occurring when delivering snapshot or just when normal replication is delivering transactions? In error u getting LSN/seqno? If so u can try to browse replicated...
December 25, 2017 at 11:06 am
December 7, 2017 at 6:03 am
As Sue_H said snapshot should run continuously and used only to initialize entire publication or new articles added to publication.About locking we had similar issue but when we moved...
October 11, 2017 at 6:46 am
As already been said. you option at this point is use TSQL. Also u can use SSMS from 2016 that have access to Publisher, Distributor and Subscriber. SSMS for 2016...
October 6, 2017 at 3:13 am
Nope. You creating publication and subscriptions on Publisher. Later on when Distribution Agent connects for the first time is creating msreplication_subscriptions table and all the replication procs (that is needed...
September 7, 2017 at 3:12 am