Yes in theory you can partition the data anyway you see fit. The geographic
field could then be used as part of the PK and replication will still be
able to use this. When it hits the central site you will not have to worrry
about duplicates cropping up as well.
I use branchid's here but the concept is the same
Let me know if you require any more info.
>I am a newbie to SQLSERVER so I just needed info on the follwing
>I have massive table with a column specifiying the geographic location.
>Can I partition this table accross SQL Servers based on the column
>value. so that each Server services the rows corresponding to the
>specific geographic column value ?