New To Merge Replication - Simple Scenario......

Jul 23, 2005

I have a product that sits on a main server and wish to implement
functionality to allow salesmen to come along, pick up a snapshot of the
database, go away and maybe modify/add to it and then come back and
"synchronise" their data. I'm reading up on Merge Replication for this
purpose. But anyway, I created a publisher on my server and it went away
and generated a "rowguid" column on all of my tables (my tables all have an
Identity column key field). Now of course my "Inserts" no longer work, as
they expect a GUID. I would have expected SQL Server to automatically
generate a guid for new inserts (in a similar way to it's TIMESTAMP), but it
appears it doesn't, despite the fact I have "(newid())" as the default for
the column. It always inserts the same value:
{00000000-0000-0000-0000-000000000000}.

So, back to basics, now I have a guid field for each record, how do I manage
inserts?

Thanks.

View 3 Replies

Merge Replication Weird Scenario?

Dec 15, 2005

On the national Server:           SQL 2005 Enterprise
On the mobile clients:             SQL 2005 Workgroup.

I was asked to find a solution to such scenario

2 mobile subscriber S1 and S2 to the same simple merge publication P1 on server N

Day 1,

S1 and S2 both synch up with N and both go off to do fieldwork
Day3,

S1 and S2 both synch up with N.

S1 goes back to work

S2  shutdown the laptop and goes on 2-week vacation.
2 Weeks late

S1 Synch up wit the server and goes off to do fieldwork.

S2 meets S1 in the field. Their workfield is in the North Pole.

S2 has the laptop with data 2-weeks old but no longer can have access to the master publisher N to synch the replica and get latest changes.

S2 will have to sync with S1 since S1 database is fresh. The challenge is to have S2 and S1 replica identical

The Questions:

Is it possible for S2 to sync with S1?

if yes, How to go about it�� we need S1 and S2 to have identical replica on their machines?

Now that S1 and S2 are have identical databases and are both doing their fieldwork in the northpole. Can they both sync back with the national publisher N when they have access?
Keep in mind that S2 got its data updated from the replica on S1?

Thank you!

View 3 Replies View Related

Replication Scenario

Dec 17, 2006

Hi all,

I have a huge replication task I need to perform. The source table has over 250,000,000 records and everyday approximately 400,000 records are added to the system regularly.

Currently, I am running snapshot replication and it's taking 10 to 11 hours to complete (The internet connection between the production and the report server is slow). The reason I am using this method is because the source table does not have a timestamp column (so I can run an incremental replication) and I cannot modify that table because it belongs to a third party software. It does have a field which is linked to another table holding the timestamp.

Here is the source table and the other table's structure for reference:

DataLog

Name Datatype Size

DataLogStampID int 4
Value float 8
QuantityID smallint 2

DataLogStamp

ID (Which is foreign key to DataLogStampID field in the above table) int 4

SourceID smallint 2

TimestampSoruceLT datatime 8

What I would like to know is, what is the best practice to handle such replication with MSSQL Server 2000.

I am thinking of developing a procedure which follows the following step using a temp table:

This procedure will run (say) every night.

The temp table will contain a timestamp field.

For one time only, I will run a snapshot replication, so that I can have the existing data into the destination db.

I will record this timestamp into a repl_status table which holds the timestamp of the last replication.

The procedure will read the record from repl_status and select all records from the source table which were added since this date and put them into a new temp table (this table will have the same structure as the source and destination tables) and then a snapshot replication will "add" these new records only every night to the dest. table. By using this method, I will only transfer the records which have been added since the last replication (last night - less records).

Any comments would be greatly appreciated.

Thanks for your time in advance,

Sinan Topuz

View 8 Replies View Related

MSDE Replication Scenario

Aug 23, 2005

Greetings to fellow fleetfingers:

View 1 Replies View Related

Replication Scenario - Seeking Suggestion

Jul 2, 2007

I have two sites. Site A and Site B

Each site has two databases

Site A

Db1

Db2

Site B

Db1

Db2

Site A Db1 has to perform transaction replication to Site A- Db2 and Site B- Db1 and Db2.

I started Site A as pubisher and distributor and Site A and Site B both as subscriber.

Site B is in a different geographical area (state).

----------

Please suggest the best scenario to save bandwidth and server load for Publisher, and Distributor.

-------

Earlier I thought that I will implement local replication between Site B - in between Db1 and Db2. The Sql Server does not let me set Db1 as publisher, and distributor for its local database Db2.

-------

P.S. My all databases need same transactions though they are connected to different hardware at different places. So please don't question that why I need four similar databases.

View 7 Replies View Related

Sql Server CE 2.0 Proxy Replication Scenario

Jul 14, 2006

Dear all,

Since Windows Integrated Authentication does not work over proxy for Replication, could I still use SSL or SQL authentication over proxy? Thanks for any advice.

View 1 Replies View Related

Replication :: Difference Between Snapshot And Transaction And Merge Replication?

May 26, 2015

What is the main difference between snapshot and transactional and merge replication?

View 5 Replies View Related

How Do We Add A New Column To A Merge Replication Article, But Specify It As Not For Replication?

Aug 30, 2007

Hi all,

I know that adding a column using ALTER TABLE to add a column automatically allows SQLSERVER 2005 to replicate the schema changes to the subscribers, however, I would like to add a new column to an existing article that is being used for merge replication, however, I don't want this column to be replicated. Re-initialising the subscriptions is not a option. Help would be appreciated.

I am using SQLSERVER 2005 (SP1).

View 3 Replies View Related

Mobile Merge Simple Question

Oct 6, 2006

So when a mobile device pulls down information, say a typical order entry scenario, then continues to edit/add orders and merges those changes back to the server, when/how are those records ever purged from the device once they are no longer needed?

View 5 Replies View Related

Merge Replication Set Off Transactional Replication

Oct 9, 2007

I am working on bringing our disaster recovery site to be a live site. Currently we replicate to one of out servers (server B) with merge replication (from server A). Server A also does one way transactional replication form some table to several other servers including servers at the DR site.

This setup is not going to be fast enough for what we need so I am wondering if a table is receiving merge replication will the merge updates also replicate down the transaction path??

Example...
Server B update a row and merges to Server A. With this update them replicate (via transactional) to Server C??

thanks...

View 5 Replies View Related

Simple Replication

Jan 2, 2008

Greetings,

I am building a system that requires a small database to be replicated.

The DB is made up of a few tables that do not change much, primarily by user-input or triggers on those tables, and one constantly growing table for incoming messages with rows constantly being added to it.

We require having two systems (System=Hardware&OS/SQLDB/Application) running in parallel where one could act as a failover to the primary system. Both systems would be run in the same site and have a direct network link.

My goal is to have both systems maintain identical databases and to be able to "re-synchronize their data after a failure in some recovery state.

I am looking at:

1. SQL Server Replication Methods (Publishers/Subscribers)
A possible scenario i need to support:
ServerA: primary server acts as publisher
ServerB: secondary failover server acts as subscriber
ServerA: Fails!
ServerB: Assumes role of primary server (i.e Publisher)
ServerA: recovers later, becomes subscriber to ServerB(secondary)

Q: Can Roles Be Switched or A server be a subscriber and
a publisher at the same time?

2. Use ServiceBroker Queues and Have Each server SEND a message
to the other server whenever it gets incoming data?

3. Use Transact-SQL in ServerA to write data to ServerA
and ServerB and vice versa.

4. Not worth replication, just have the application write data
to both servers in two seperate requests.

Which is the preferred way to accomplish this?

Thanks,
-ali

View 4 Replies View Related

One Way Merge Replication

Feb 14, 2002

Hi everbody,
I setup the Merge Replication , it is working perfectly. But i have one problem now it is updating both ways. I nedd one way. Any body tell me which parameter i have to change.

Thanks in advance