Choosing replication type

Hello!
I'm trying to put together replication for a small application that
works like this: The central database contains data that is to be
copied to several laptops. The laptops are going to be used on
inspections of real-estate all over this city. When the user is
finished with his work, he wants his data transferred/updated to the
main database. This updating only concerns a few columns in a few
tables. NOT the whole database.
I figured Snaphot Replication was a good idea, but this only work one
way - to the laptop, with the database structure and all the data.
When data is going back to the central database, snapshot replication
will only try to add rows, as it doesn't know which rows to update.
Merge Replication will update all of the data both ways, and that is
not "allowed" in this context.
Any good suggestions?
Thanx!
Dagfinn Rosnes
Use Merge replication - only replicate the tables and columns that the
laptops will be changing.
"Dagfinn Rosnes" wrote:

> Hello!
> I'm trying to put together replication for a small application that
> works like this: The central database contains data that is to be
> copied to several laptops. The laptops are going to be used on
> inspections of real-estate all over this city. When the user is
> finished with his work, he wants his data transferred/updated to the
> main database. This updating only concerns a few columns in a few
> tables. NOT the whole database.
> I figured Snaphot Replication was a good idea, but this only work one
> way - to the laptop, with the database structure and all the data.
> When data is going back to the central database, snapshot replication
> will only try to add rows, as it doesn't know which rows to update.
> Merge Replication will update all of the data both ways, and that is
> not "allowed" in this context.
> Any good suggestions?
> Thanx!
> Dagfinn Rosnes
>
|||Clarify my previous post:
Use a "one-way" merge replication
http://www.microsoft.com/sql/techinf...t/mergerep.asp
"Dagfinn Rosnes" wrote:

> Hello!
> I'm trying to put together replication for a small application that
> works like this: The central database contains data that is to be
> copied to several laptops. The laptops are going to be used on
> inspections of real-estate all over this city. When the user is
> finished with his work, he wants his data transferred/updated to the
> main database. This updating only concerns a few columns in a few
> tables. NOT the whole database.
> I figured Snaphot Replication was a good idea, but this only work one
> way - to the laptop, with the database structure and all the data.
> When data is going back to the central database, snapshot replication
> will only try to add rows, as it doesn't know which rows to update.
> Merge Replication will update all of the data both ways, and that is
> not "allowed" in this context.
> Any good suggestions?
> Thanx!
> Dagfinn Rosnes
>