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 |
|
tyaramis
Starting Member
3 Posts |
 Posted - 2005-03-09 : 05:31:38
|
| Hi AllI have already checked the answers in discussions to find a solution for my problem but I could not..I am using Trancation Replication for my customer. There is one server (Publish) in a city and 5 more Subscription in different citys. We are only replicating one Table, that is called "Adresse"So far I got 2 kind of problems. 1.One of them subscriptions being "inactive".2.the other one is that some of the subscriptions have connection problem with Publisher DB.For the Problem 1, if there is no transaction occurs within "14 days(default value)" between publishing server and subscription servers, becoming Subscriptions inactive. I changed this value as "never expired" but I am not sure it is a good idea. As I read, Distribution DB is growing. But only one Table is it a problem?The 2. Problem that I yesterday had is connection Problem. 3 of subscriptions was working fine but 2 of them were not available.The error messages are at replication monitor like this for these 2 server."The agent is suspect.No Response within last 10 minutes"I know that is only a information messages. But in subcription side, the error was;"The Process could not connect to Distributor 'Server1' "The customers Network is really bad and they are living disconnections very often.Then, in replication monitor screen, I made right click to subcriptions which are not running and clicked "Start synchronizing". After that, the transactions are made and the situations of these 2 subscriptions became normal and active.Regarding this problem, if there is a network problem in Subcriptions, how can replication (synchronizing) start automatically, after the network is up again.Because, its not good, everytime connecting to Customer server and start synchronizing. Could it be made with and stored procedures or with a Job, script??Thanks alot in advance...Tolga |
|
|
jen
Master Smack Fu Yak Hacker
4110 Posts |
Posted - 2005-03-09 : 21:50:09
|
| I feel for you, coz i had similar problems...1. changing the value to never expire just ensures that replication will be continuous with the client (otherwise, refer to your company contract), this is ok. By default, distribution db is set to simple recovery model, so no need to worry about the log file growing too much, otherwise set it to simple. If you're really worried about the size, restrict the size to a manageable size, create an alert to monitor the current used log size, the alert triggers a job, that truncates the log file.2. create an alert that will monitor if replication is down then create a job that will start the job for the specific distribution agent that failed.Should you need assistance to number 2, just email me and i'd be glad to help...best of luck--------------------keeping it simple... |
 |
|
|
|
|
|
|
|
Trancation Replication Problems