Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
ddoyley
Starting Member
3 Posts |
 Posted - 2010-09-28 : 13:39:28
|
| I just moved from sql 2000 to sql 2008. The primary database is clustered and is configured as the publisher. There is a separate distributor and subscriber. They were all running sql 2008R2 standard with the exception of the subscriber(that was unintentional), which was running 2008 standard. I started running into the error described in the link below whenever we update a text column. The subscriber has since been upgraded to R2. The link below doesn't say R2 is affected. Has anyone run into the problem and how did they solve it. I will be changing a text column later today and fear that we will run into the same issue. When the problem occurs the only thing we can do is reinitialize.http://connect.microsoft.com/SQLServer/feedback/details/422266/msft-candidatesearch-transactional-replication-log-reader-agent-errors-when-adding-new-article |
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
|
|
|
|
|
Transactional Replication using native snapshot