Hi All ,
Previously i have set up my replication to be on sync per hour but i want
to change it to be continuously
is there a way to do it w/o removing the existing publication & subscriber
and thus save the task of re-creating the snapshot ?
appreciate ur advice
tks & rdgs
Message posted via http://www.droptable.com
Hi All ,
Furthermore , is there any drawbacks in changing it to continuously mode ?
kindly advise
tks & rdgs
maxzsim wrote:
>Hi All ,
> Previously i have set up my replication to be on sync per hour but i want
>to change it to be continuously
> is there a way to do it w/o removing the existing publication & subscriber
>and thus save the task of re-creating the snapshot ?
>appreciate ur advice
>tks & rdgs
Message posted via droptable.com
http://www.droptable.com/Uwe/Forums...erver/200601/1
|||Open the job in SQL Server Agent. Change the schedule to "start when SQL
Server starts" or whatever it says. Remove the schedule that executed it
once per hour.
Mike
Mentor
Solid Quality Learning
http://www.solidqualitylearning.com
"maxzsim via droptable.com" <u14644@.uwe> wrote in message
news:59ef504952a00@.uwe...
> Hi All ,
> Previously i have set up my replication to be on sync per hour but i want
> to change it to be continuously
> is there a way to do it w/o removing the existing publication & subscriber
> and thus save the task of re-creating the snapshot ?
> appreciate ur advice
> tks & rdgs
> --
> Message posted via http://www.droptable.com
|||tks Michael , but would you know of any drawbakcs using the continuously mode
? especially when the network is not that fast ? i.e while the previous
changes are still being replicated , there are new changes so will it cause
the system to be cranky or anything like that ?
tks & rdgs
Michael Hotek wrote:[vbcol=seagreen]
>Open the job in SQL Server Agent. Change the schedule to "start when SQL
>Server starts" or whatever it says. Remove the schedule that executed it
>once per hour.
>[quoted text clipped - 7 lines]
Message posted via droptable.com
http://www.droptable.com/Uwe/Forums...erver/200601/1
|||Changing the agent to only start when SQL Server Agent starts will have it
process only a single batch and then the distribution agent will shut down.
It will not restart until you restart SQL Server agent. Try it. Stop your
SQL Server agent, insert a bunch of rows into a replicated table, bounce SQL
Server, observe your distribution agent starting up, processing the batch
and then shutting down.
You also need to edit your agent to and add the -Continuous switch. Right
click on your agent, select agent properties, click on the steps tab, and
double click on run agent. Click in the commands text box and hit the end
key, then press the space bar and type in -Continuous. Restart your
distribution agent. If you distribution agent does fail, it will restart
again in 1 hour if you leave the scheduling option on.
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"maxzsim via droptable.com" <u14644@.uwe> wrote in message
news:59f0f9aab1351@.uwe...
> tks Michael , but would you know of any drawbakcs using the continuously
> mode
> ? especially when the network is not that fast ? i.e while the previous
> changes are still being replicated , there are new changes so will it
> cause
> the system to be cranky or anything like that ?
> tks & rdgs
> Michael Hotek wrote:
> --
> Message posted via droptable.com
> http://www.droptable.com/Uwe/Forums...erver/200601/1
|||No. It will simply send as much as possible during every synch cycle.
Mike
Mentor
Solid Quality Learning
http://www.solidqualitylearning.com
"maxzsim via droptable.com" <u14644@.uwe> wrote in message
news:59f0f9aab1351@.uwe...
> tks Michael , but would you know of any drawbakcs using the continuously
> mode
> ? especially when the network is not that fast ? i.e while the previous
> changes are still being replicated , there are new changes so will it
> cause
> the system to be cranky or anything like that ?
> tks & rdgs
> Michael Hotek wrote:
> --
> Message posted via droptable.com
> http://www.droptable.com/Uwe/Forums...erver/200601/1
Thursday, March 8, 2012
changing replication type for hourly to continuously
Labels:
changing,
continuously,
continuouslyis,
database,
hourly,
microsoft,
mysql,
oracle,
removing,
replication,
server,
sql,
sync,
type,
wantto
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment