June 3, 2015 at 4:51 am
Hi,
I am working with transactional replication set up.
We installed sql server 2014 in one of environment. I backup the database sql server 2008r2 and restored in sql server 2014. That database is configured for publication in sql server 2008r2.
I need to set up replication again.
Question: Is the previous replication going to be effect anything now? Anything needs to be consider in this situation
I am following the below article
https://msdn.microsoft.com/en-us/library/aa337433.aspx
Agent Location Account name
Snapshot Agent Publisher <machine_name>\repl_snapshot
Log Reader Agent Publisher <machine_name>\repl_logreader
Distribution Agent Publisher & Subscriber <machine_name>\repl_distribution
so if we take machine1 & machine 2 are for publisher/distributor & subscriber. We need the following logins
The Distribution agent must be machine1\repl_distribution @publisher and machine2\repl_distribution at subscriber
June 4, 2015 at 9:27 am
I took the snapshot when I click on replication monitor
I can see so many errors from distributor to subscriber
Cannot use a CONTAINS or FREETEXT predicate on table or indexed view 'tablename' because it is not full-text indexed. (Source: MSSQLServer, Error number: 7601)
I am getting several of these
What is the solution for this?
June 5, 2015 at 1:06 pm
June 8, 2015 at 9:36 am
Yes.
I added the fulltextsearch feature to the installation. I have some full text indexes in publisher database. The fulltextcataloge is created manually in subscriber server.
Under the articles when I tried to change the option copy the fulltext index to true, it is again backing up to the false only. How to change this option to replicate to the fulltext indexes in subscripter server
June 14, 2015 at 8:35 pm
Any suggestion on this issue!
I am getting still same errors and replication is failing.
Do I need to follow the below process even in sql 2008r2
June 16, 2015 at 9:28 am
Hard to say,
I would go over each table that contains those data types and ensure you've created a full-text index on EVERY one.
If you're missing even one, the replication is going to fail.
Using native mode shouldn't be a requirement but it's not going to hurt anything to try it out in a test environment and see if it clears the error for you.
Hope that helps!
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply