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

SQL Server 2005 - Merge Replication

 
   Database Help (Home) -> Replication RSS
Next:  ON UPDATE CASCADE when collation considers string..  
Author Message
ravivarman

External


Since: Jan 01, 2009
Posts: 1



(Msg. 1) Posted: Thu Jan 01, 2009 7:25 am
Post subject: SQL Server 2005 - Merge Replication
Archived from groups: microsoft>public>sqlserver>replication (more info?)

Hi,
we are shifting our data-setup from SQL Server 2000 to SQL Server 2005. With
regard to this, I am facing an issue with replication of the databases.

We have a database with over 600 articles that are published.
The procedure that we followed with SQL Server 2000 in order to have a
smooth and quick replication scenario was as below:

On the publisher:
1. Create the database snapshot.
2. Back up the published database.
3. Create a temporary database and restore the published database on the
temporary database.
4. Create a new 'no-sync' pull subscription from the temporary database to
the published database
5. Run the merge agent to synchronize the databases.
6. Copy the subscription databases (XYZDatasbe.msf file)
7. Register the subscriber computer
8. Register the subscribing database using sp_addmergesubscription

On the subscriber:
1. Attach the subscription database copy (XYZDatasbe.msf)
2. Create a pull subscription using sp_addmergepullsubscription
3. Connect to the publisher using a dial up connection
4. Run the merge agent to synchronize the data.

In such a case, the initial synchronization would take less than a minute as
no schema was transfered.

In the case of a senario with SQL Server 2005:
a. The attachable subscription databases (.msf files) have been depricated.
So we cannot create .msf files to transfer the snapshot to the subscribers.

b. Instead of .msf files, we can backup and restore the publication datbase
at the subscriber and make the pull subscription with the no-sync option. But,
for the sp_addmergepullsubscription, the parameter sync_type with value
'none' has been depricated. i.e sync_type='none' is depricated, however
sync_type='automatic' is valid.

Hence when we create a pull subscription by restoring a backup of the
published database and indicate 'do not initialize', the database schema
alone (not data) once again gets transfered from the publisher to the
subscriber on the first synchronization. This takes a very long time over a
dial up connection.

There is an option to 'initialize with backup' or 'replication support only'.
But these options are available only for transactional replication and not
merge replication.

Please guide me on overcoming this issue.

 >> Stay informed about: SQL Server 2005 - Merge Replication 
Back to top
Login to vote
Paul Ibison

External


Since: Oct 03, 2008
Posts: 145



(Msg. 2) Posted: Mon Jan 05, 2009 2:51 am
Post subject: RE: SQL Server 2005 - Merge Replication [Login to view extended thread Info.]
Archived from groups: per prev. post (more info?)

Nosync initializations are deprecated but not yet discontinued for merge
replication. Provided you meet a few caveats (see
http://msdn.microsoft.com/en-us/library/ms152488.aspx) you can still do it
this way, at least until the next version of SQL Server that is.
HTH,
Paul Ibison, www.replicationanswers.com

 >> Stay informed about: SQL Server 2005 - Merge Replication 
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....

Merge replication betwen 2005 standar and 2005 CE - Hello: I have an application in a laptop using SQL CE as database (a .sdf file). I have configured a merge replication in this laptop throw Sql Server Management Studio using web sinc. and runs ok. The publisher is the SQL Server 2005 standar machine...

Merge replication sqlserver 2005 and CONSTRAINT - hi, I have added a constraint on a column of a table. This constraint use a function. When i synchronise the subscriber, i have the error: Le script de schéma « if object_id(N'[Reference].[TRADUCTION]') is not null exec('ALTER TABLE..

merge replication sql 2005 64bit - i was setting up merge replication and received a message that a table couldn't be replicated because it has more than 254 columns. THe table in question has 288 columns. So - I can only replicate 254 columns? Darin *** Sent via Developersdex..
   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 ]