Replication-priority

[Zen216]

Hello all,
Extreme noob here.. sorry if this question obvious to all...
We replicate to a DR site over a T-1 link, (SQL 2000 on windows 2003 servers)
Sometimes due to some hiccup, replication goes down. When this happens the db admin will just re-start/re-initialize it, and it starts the snapshot,, well when this happens it pretty much locks everyone out of their applications that hit the db server.
So, he stops it, and then tries to re-start it overnight, but most of the time, he will have to wait for the weekend to restart it so the snapshot can complete before business starts again on Monday.

Is there a way to set the priority of the replication to a lower priority, so that the apps can work without gettimg timeouts?

Thanks everyone

 

[mrdenny]

Nope. Replication locks the tables so that it can get the table into a consistent state so that it can create the snapshot.

How long is replication down before it's restarted? You shouldn't need to create a new snapshot just because replication is stopped for a little bit.

All your DBA should need to do is restart the distribution agent. Personally I like to edit the schedule and set it to restart every 5 minutes so that replication starts back up right away.

Denny
MCSA (2003) / MCDBA (SQL 2000)
MCTS (SQL 2005 / Microsoft Windows SharePoint Services 3.0: Configuration / Microsoft Office SharePoint Server 2007: Configuration)
MCITP Database Administrator (SQL 2005) / Database Developer (SQL 2005)

My Blog

 

[Zen216]

Well my problem is.. that I am the "junior" admin, and he is the "all powerful-- senior" admin..
however he doesn't want to do anything that might be work, and will not even look at something if he might now fully understand it,,, (ie. he farms out simple router config changes to a local shop, stating that they are the wan "engineers")... he has no certs, but has been here for 10 years...
sorry for the rant,, I current am A+, Network+, MCSA 2000, and MCSA 2003,, but still get no respect.. doh!

Well, when a network switch has a little power blip, replication on this one server always goes down,, when I try to re-start the agent it never does,, (If I see the roor before the "senior" guy, then I will just re-boot the server and it almost always fixes itself,, if he finds it first he always re-initializes it and starts a new snapshot... freezing everyone on the network...

(next project for me is to start studying SQL)

Thanks,, and again sorry for the rant... just getting frustrated...lol