March 20, 2007 at 11:37 pm
Hi all!
Well, we're using merge replication in SQL Server 2000, one database in one server publishing half its tables, the merge runs continuously against a copy of the database in another server. The distributor runs in the publisher, a snapshot is run once a week.
The problem seems simple but we can't solve it yet, the REPLDATA folder is not being cleaned up, so it is filling slowly our disk space. I can clean it manually but I want to know what is the problem.
So far I have two potential clues: one is that the only agents that I see in the Replication Monitor are one snapshot agent and one merge agent, when I would expect one distribution agent too. But otherwise the replication scheme is running fine so I don't think this is the problem.
The other one is that the two agents' owner is not the "agent" account but the account of the DBA who created the replication. In this case I would think there's a problem of permissions on the REPLDATA folder, but the DBA's user account has domain admin privileges on the folder (this is a small shop here).
Any ideas ?? Thanks in advance !!!
Daniel
March 21, 2007 at 3:23 pm
Re reading my post, I guess it sounds like a little newbie. Well, I've read everything I could find on this subject in the SQL Server 2000 help and googled heavily on the subject before posting this, to no avail.
Perhaps this is an obvious issue, but it's ok, I've never certified on SQl Server. I'll keep googling for help in the meantime.
Daniel
March 23, 2007 at 12:01 am
HI Daniel,
Just to give you a brief description of how merge replication works
In Merge there is no distribution agent. This functionality is taken care by the Merge Agent itself. basically the Distribution database stores the history of synchronization.
Comming to your question related to the REPLDATA folder
You can check if the account that is used to run the Merge Agent if it has the required permission on the REPLDATA folder. When i say permissions check if there is any DENY Setting in the Advanced tab.
Try to run the merge agent with the SQL SErver Agent Service account and check if the REPLDATA is getting cleared or not.
This would be our basic troubleshooting. In case this does not work lets take it to one step forward.
Krishna
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply