Welcome to dbFreaks.com!
FAQFAQ    SearchSearch      ProfileProfile    Private MessagesPrivate Messages   Log inLog in

Merge Replication with SQL Server 2005 (server to server)

  
   Database Help (Home) -> Replication RSS
Next:  Curious problem with ftp:// wrapper.  
Author Message
DL

External


Since: Apr 26, 2008
Posts: 32



(Msg. 1) Posted: Fri Dec 19, 2008 3:19 pm
Post subject: Merge Replication with SQL Server 2005 (server to server)
Archived from groups: microsoft>public>sqlserver>replication (more info?)
I've got merge replication between two servers (bi-diretional) data
merge working. Now, when I attempted to do a bit more, got into a
problem. Here's the scoop.

Publisher and Distributor = Central Server which has the main database
-----------------------------------

Subscribers:
------------------
Scenario A
Structure-wise
* using Pull subscription
* using a brand new DB
Process-wise
subscribe to the merge publication only

Notes:
a) I've got the above configuration workiing (b-directional data
update (insert, update and delete) the other day.
b) Downside: to sync everything, tables, SPs, views, UDFs etc. is
quite resources-intensive.


Scenario B
Structure-wise
* using Pull subscription
* using an identical database (to the publisher's db) with data
Process-wise
subscribe to the merge publication only

Notes:
Well, be default, the subscriber will 'import' the snapshot (db schema
etc.), however, it's not needed in this case. I don't see an option
from the subscription to disable snapshot sync. There must be a way
to do it. How?

Thanks.

 >> Stay informed about: Merge Replication with SQL Server 2005 (server to server) 
Back to top
Login to vote
Hilary Cotter3

External


Since: Aug 28, 2004
Posts: 458



(Msg. 2) Posted: Mon Dec 22, 2008 8:30 am
Post subject: Re: Merge Replication with SQL Server 2005 (server to server) [Login to view extended thread Info.]
Archived from groups: per prev. post (more info?)
Use a no-sync subscription.

"DL" wrote in message

>
> I've got merge replication between two servers (bi-diretional) data
> merge working. Now, when I attempted to do a bit more, got into a
> problem. Here's the scoop.
>
> Publisher and Distributor = Central Server which has the main database
> -----------------------------------
>
> Subscribers:
> ------------------
> Scenario A
> Structure-wise
> * using Pull subscription
> * using a brand new DB
> Process-wise
> subscribe to the merge publication only
>
> Notes:
> a) I've got the above configuration workiing (b-directional data
> update (insert, update and delete) the other day.
> b) Downside: to sync everything, tables, SPs, views, UDFs etc. is
> quite resources-intensive.
>
>
> Scenario B
> Structure-wise
> * using Pull subscription
> * using an identical database (to the publisher's db) with data
> Process-wise
> subscribe to the merge publication only
>
> Notes:
> Well, be default, the subscriber will 'import' the snapshot (db schema
> etc.), however, it's not needed in this case. I don't see an option
> from the subscription to disable snapshot sync. There must be a way
> to do it. How?
>
> Thanks.
>
>
>
>

 >> Stay informed about: Merge Replication with SQL Server 2005 (server to server) 
Back to top
Login to vote
DL

External


Since: Apr 26, 2008
Posts: 32



(Msg. 3) Posted: Mon Dec 22, 2008 12:53 pm
Post subject: Re: Merge Replication with SQL Server 2005 (server to server) [Login to view extended thread Info.]
Archived from groups: per prev. post (more info?)
A quick search indicates that one can do that during the subscription
creation process. Since I have one already, I looked at its
properties, however, couldn't find anywhere that would allow me to set
no-sync or am I missing something here? Or could we do it from
scripting? Then which proc?

Thanks.

> On Dec 22, 8:30 am, "Hilary Cotter" wrote:
> Use a no-sync subscription.
>
 >> Stay informed about: Merge Replication with SQL Server 2005 (server to server) 
Back to top
Login to vote
Paul Ibison

External


Since: Oct 03, 2008
Posts: 145



(Msg. 4) Posted: Mon Dec 29, 2008 8:09 am
Post subject: Re: Merge Replication with SQL Server 2005 (server to server) [Login to view extended thread Info.]
Archived from groups: per prev. post (more info?)
Have a look here for more info:
http://msdn.microsoft.com/en-us/library/ms152488(SQL.90).aspx. From BOL: "A
subscription is a "no sync" subscription if a value of none is specified for
the @sync_type parameter of sp_addmergesubscription or
sp_addmergepullsubscription. This type of subscription is not recommended for
merge replication.".
HTH,
Paul Ibison
 >> Stay informed about: Merge Replication with SQL Server 2005 (server to server) 
Back to top
Login to vote
DL

External


Since: Apr 26, 2008
Posts: 32



(Msg. 5) Posted: Tue Dec 30, 2008 1:21 pm
Post subject: Re: Merge Replication with SQL Server 2005 (server to server) [Login to view extended thread Info.]
Archived from groups: per prev. post (more info?)
On Dec 29, 11:09 am, Paul Ibison <Paul.Ibi....RemoveThis@ReplicationAnswers.Com.
(donotspam)> wrote:
> Have a look here for more info:http://msdn.microsoft.com/en-us/library/ms152488(SQL.90).aspx. From BOL: "A
> subscription is a "no sync" subscription if a value of none is specified for
> the @sync_type parameter of sp_addmergesubscription or
> sp_addmergepullsubscription. This type of subscription is not recommended for
> merge replication.".
> HTH,
> Paul Ibison

Thanks. Actually I'd like to step back for a sec, that is, I'll now
do uni-directionary replication first. Then, topology-wise, it would
be a) snapshot; b) transaction. Business case, DR, so, I intend to
use server push to a subscriber like every 1 hour. Some pecularity
here, we have desktop application running against the main/publisher
server all the time and the app created voice data dynamically and
save them to the DB. Yesterday I experienced error during data saving
but it's sort of false positive, data were actaully saved. Without
the replication coming into play this sort of error never occur, so,
is it a bug from MS Replication technology side or on the incorrect
usage side? Secondly, i was thinking to remove table/article that
include the column of such voice data for the replication's
transactional process then create a new replication or some other
process just for this set of data. But this approach is kind of
messy.

For another, has SQL Server 2008's replication technology improved in
terms of ease of use and bugginess?
 >> Stay informed about: Merge Replication with SQL Server 2005 (server to server) 
Back to top
Login to vote
Display posts from previous:   
Related Topics:
Merge Replication index contention in SQL Server 2005 - We are having problem with merge replication and causing deadlock and found following merge replication index causing contention with one user table index. objectname indexname index_id row_lock_count row_lock_wait_count block ..

SQL Server 2005 Merge Replication: Enumeration Generation .. - Issues: 1) I have machines that out of the blue they take 8+ hours to sync. The log states that the agent is enumerating generation batches 2) I have had a few machines enumerate generation batches for 8+ hours the first sync after a re-initialization....

SQL Server merge replication questions - Hi Merge replication between SQL Server 2000 publisher and SQL Server 2005 Express subscribers. I have the following questions; 1. My tables have int increment primary keys. Do I need anything special for replication to handle PK conflicts between..

Data Replication Options (SQL Server 2005) - We have a database approx 200 GB size. Approx 5-10 GB of data is modified on nightly basis (delete + bulk load) - no updates. Regarding bulk load, we use simple recovery mode. We want to have another server as a warm/cold backup (and read only ..

SQL Server 2005 Start a transactional replication (push) u.. - Hello, We would like to test a transactional replication (push) using a snapshot recently copied on a DVD. Did anyone try this ? Thank's in advance for your answers, Regards, Karine
   Database Help (Home) -> Replication All times are: Pacific Time (US & Canada)
Page 1 of 1

 
 You can post new topics in this forum
You can reply to topics in this forum
You can edit your posts in this forum
You can delete your posts in this forum
You can vote in polls in this forum



[ Contact us | Terms of Service/Privacy Policy ]