Viewing 15 posts - 136 through 150 (of 353 total)
By design, merge replication is very resilient.
When you say it fails to work, are you getting any replication errors or is it just the case that the network/connection that you...
July 2, 2008 at 1:20 am
Have you checked all the indexes are in place...do you have any large tables that are being replicated. If these tables are missing indexes then the replication will slow down...
July 2, 2008 at 12:52 am
Hi Lynn,
Are there any major updates or data changes of any types around the time of your increased latency ?
Are there any processes running at this time ?
Is there any...
July 1, 2008 at 4:37 am
Try using a windows account that has the right permissions.
Graeme
July 1, 2008 at 4:35 am
Hi,
Can't you simply add a job that will update the column after the snapshot has run?
HTH
Graeme
July 1, 2008 at 4:32 am
Further to my initial comment.
I made a comment that may have sounded as if I was knocking the the DBA who had been dropped in the job and struggled and...
June 30, 2008 at 8:17 am
Hi,
That's probably a question for another forum 🙂
Returning to the issue...
I've used SQL for a while now and I think I know quite a bit (enough to offer advice on...
June 25, 2008 at 4:09 am
Yes you may have to drop the subscriptions, add the articles then push out a completely new snapshot...yes not ideal.
You could set up another publication for the new article(s)...that way...
June 23, 2008 at 9:44 am
Hmmm...
When you have the concurrent snapshot option set, I think the only thing you can do is drop the subscriptions totally, add the article and resynch with a totally new...
June 23, 2008 at 9:30 am
Hi,
You should have a read about merge replication 🙂
When the merge agent runs it will apply changes that have been applied elsewhere and show the changes that it is pushing.
So...
June 23, 2008 at 9:05 am
Are you running this against the Publishing database?
June 23, 2008 at 8:56 am
Look at MSArticles in the Distribution database
June 23, 2008 at 5:19 am
Can you check that the article is actually being subscribed. I know you've added it back to the publication but check the table MSsubscriptions in the Distribution database.
The normal process...
June 23, 2008 at 2:32 am
Any ideas on why the publication might have failed...
Did it just happen or was it caused by a process ?
June 16, 2008 at 5:12 am
Have you looked at the system replication tables...the ones that store the publications and subcribers ?
June 11, 2008 at 1:18 am
Viewing 15 posts - 136 through 150 (of 353 total)