Viewing 15 posts - 16 through 30 (of 41 total)
not exactly. In order to create publication and subscription u need to connect to Publisher and create it there. However if Publisher don't have an access to Subscriber creating subscription...
September 5, 2017 at 3:14 am
In your scenario just Distributor need to have access to both Publisher and Subscriber. If you want to create subscription just connect remotely to Distributor, connect to publisher from there...
September 5, 2017 at 2:55 am
Try to test DTC first by running some simple selects and using BEGIN DISTRIBUTED TRANSACTION:
https://docs.microsoft.com/en-us/sql/t-sql/language-elements/begin-distributed-transaction-transact-sql
You may need to modify the linked server to...
September 1, 2017 at 3:22 am
Then I think the only option will be dropping articles from replication and adding these back after the change and sending snapshot down again (just tables that been dropped). However...
August 31, 2017 at 3:44 am
The question is do you really need to stop/drop replication for these specific changes that vendor will be doing? The only thing (that I know of) that can't be done...
August 21, 2017 at 4:37 am
old distribution db is still there? run select * from msdistribution_agents and check if old subscriptions are there.
August 7, 2017 at 9:29 am
yes then it means you still have information about old replication in remote Distributor. Try removing old publisher from remote distributor as I mentioned before. Just remember that it will remove...
August 7, 2017 at 8:22 am
Hi,
The Replication Monitor is taking most of the data (subsriptions, latency, pending cmds) from Distributor. You ran cleanup with ignore_distributor=1.
What exactly you migrate Publisher only? Was...
August 7, 2017 at 8:00 am
Still u can run this on Publisher:
exec sp_dropdistributor @no_checks=1,@ ignore_distributor=1
It will cleanup publisher. I did not say to remove publication database just distribution db (as the data inside...
July 14, 2017 at 7:34 am
Hi,
Not sure why you restoring distribution db when later you want to drop everything to recreate all replication setup? You can create new distribution db and configure it...
July 13, 2017 at 1:23 pm
Could you check settings on the article for UPDATE? u using SCALL for updates?
Here is more info:
https://docs.microsoft.com/en-us/sql/relational-databases/replication/transactional/transactional-articles-specify-how-changes-are-propagated
June 20, 2017 at 4:29 am
You wont be able to split publications on ONE publisher to multiple distribution dbs.
One publisher can only have one distributor and one distribution db. ALL transactions from SERVERA will...
May 12, 2017 at 1:39 am
Try to create new agent profile with bigger timeouts, readbatch and Logscan settings.
Also check if there are any locks on distribution db as log reader may lock with...
May 9, 2017 at 11:03 am
I have a question. how often you need to re-initialize? Why u need to re-initialize?
If you really need to re-initialize very often then maybe You can try to use...
May 9, 2017 at 10:55 am
Hi,
Please check sysarticles on publisher first (or setting of the given article- via GUI) if there are update and delete replicated. del_cmd and upd_cmd columns should have procedures...
May 1, 2017 at 3:17 am
Viewing 15 posts - 16 through 30 (of 41 total)