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 |
|
jnghh
Starting Member
10 Posts |
 Posted - 2007-08-08 : 04:44:07
|
| I've been studying/experimenting with the replication features and though the Updating Susbcribers Replication Model was the answer to my data environment. What we want: We have a live server (Publisher) that'll serve content to our users, but we want an "offline/data entry" server (Subscriber) that'll pretty much have the exact same data as the live server for data entry and validation purposes. Changes and inserts would be done on the Subscriber locally, vetted through, and once done, it'd be updated to the Publisher.I've managed to get some semblance of the above working, but the updates are nearly instantaneous. Which means that changes/inserts that may be erroneous on the subscriber machine would almost always be seen on the publisher machine before our operations can do anything about it.Is there a way to configure the replication process to hold off until the admin triggers it? Or am I using the wrong feature? |
|
|
rmiao
Master Smack Fu Yak Hacker
7266 Posts |
Posted - 2007-08-08 : 14:25:05
|
| You can take look at queued update. |
 |
|
|
jnghh
Starting Member
10 Posts |
Posted - 2007-08-08 : 21:56:07
|
I actually thought I was using queued updates--but was puzzled that it seemed to be immediate. (I tried finding the appropriate jobs in the job activity to disable, but still the updates went through almost immediately.) I finally found this : http://technet.microsoft.com/en-us/library/ms151718.aspxquote:
If queued updating is used, the changes are stored in a queue; the queued transactions are then applied asynchronously at the Publisher whenever network connectivity is available.
Does that mean as long as there's a connection available, it's pretty much "immediate"? In order to meet my requiredments (where I want to hold off any updates until a business decision is made), I'd have to disable the connection (outside SQL Server, e.g. taking out the LAN cable, disabling the NIC?!) while updates are being made.. and then re-establish the connection?  |
|
|
|
homebrew
Posting Yak Master
114 Posts |
Posted - 2007-08-15 : 15:55:26
|
| When you set up the subscription, isn't there an option for "continuous" or "scheduled" or "on demand" updates ?? |
|
|
|
jnghh
Starting Member
10 Posts |
Posted - 2007-08-15 : 23:42:12
|
| Oops, I forgot to come back. I couldn't quite get the Transaction with Subscriber Updates to work the way I wanted. Yes, there was a "continuous"/"scheduled"/"on demand" synchronization but this seemed to only affect changes from publisher to subscriber. I managed to changes in the publisher wouldn't be updated until manually triggered from the Replication Monitor, but any changes to the subscriber were immediately updated to the publisher as long as there was a connection.I finally used "Merged Publication" instead to do what I wanted. Manually initiate synchronization of updates (from both publisher and subscriber). |
|
|
|
|
|
|
|
|
Manually Triggered Replication?