"Jim Hubbard" <reply@groups.please> wrote in message
news:QmgXf.3168$L6.2890@bignews5.bellsouth.net...
>I have a client that desires a new application for use at several stores in
>different cities. He wants "real time" access to all store data and the
>ability to continue to run locally even if the internet connection goes
>down.
>
> It occurs to me that a local SQL Server 2005 instance should definitely be
> in each store to continue work if the net is down for any reason. But,
> what is the best way to synchronize/share data among all of the stores?
>
> Any help that you give will be greatly appreciated.
>
> Thanks!
>

"Simon Sabin" <ContactThroughMyBlog@nospam.com> wrote in message
news:443ab9b3$0$2539$ed2619ec@ptn-nntp-reader02.plus.net...
> Transactional Peer to Peer replication is probably the answer, however it
> is
> not just as simple as installing it you need to consider how the stores
> own
> the data, i.e. who is allowed to modify what data. In Peer to Peer
> replication each store should only modify its data. For this reason your
> database design needs to be able to support this.
>
> You will also have common data shared across the sites, you will to decide
> how this is maintained.
>
> --
> Simon Sabin
> SQL Server MVP
> http://sqljunkies.com/weblog/simons
>
> "Jim Hubbard" <reply@groups.please> wrote in message
> news:QmgXf.3168$L6.2890@bignews5.bellsouth.net...
>>I have a client that desires a new application for use at several stores
>>in
>>different cities. He wants "real time" access to all store data and the
>>ability to continue to run locally even if the internet connection goes
>>down.
>>
>> It occurs to me that a local SQL Server 2005 instance should definitely
>> be
>> in each store to continue work if the net is down for any reason. But,
>> what is the best way to synchronize/share data among all of the stores?
>>
>> Any help that you give will be greatly appreciated.
>>
>> Thanks!
>>
>
>
>

"Jim Hubbard" <reply@groups.please> wrote in message
news:lrE_f.2434$zh1.1351@bignews1.bellsouth.net...
> Translation: This is going to be a tremendous pain in the ass.
>
> Got it!
>
> "Simon Sabin" <ContactThroughMyBlog@nospam.com> wrote in message
> news:443ab9b3$0$2539$ed2619ec@ptn-nntp-reader02.plus.net...
>> Transactional Peer to Peer replication is probably the answer, however it
>> is
>> not just as simple as installing it you need to consider how the stores
>> own
>> the data, i.e. who is allowed to modify what data. In Peer to Peer
>> replication each store should only modify its data. For this reason your
>> database design needs to be able to support this.
>>
>> You will also have common data shared across the sites, you will to
>> decide
>> how this is maintained.
>>
>> --
>> Simon Sabin
>> SQL Server MVP
>> http://sqljunkies.com/weblog/simons
>>
>> "Jim Hubbard" <reply@groups.please> wrote in message
>> news:QmgXf.3168$L6.2890@bignews5.bellsouth.net...
>>>I have a client that desires a new application for use at several stores
>>>in
>>>different cities. He wants "real time" access to all store data and the
>>>ability to continue to run locally even if the internet connection goes
>>>down.
>>>
>>> It occurs to me that a local SQL Server 2005 instance should definitely
>>> be
>>> in each store to continue work if the net is down for any reason. But,
>>> what is the best way to synchronize/share data among all of the stores?
>>>
>>> Any help that you give will be greatly appreciated.
>>>
>>> Thanks!
>>>
>>
>>
>>
>
>

"Simon Sabin" <ContactThroughMyBlog@nospam.com> wrote in message
news:443c1c5b$0$33900$ed2619ec@ptn-nntp-reader03.plus.net...
>I would say pain in the arse. Its just not simple.
>
> The scenario you want is complex you can't expect it to be really easy.
> Imagine trying to do this with Oracle :)
>
> --
> Simon Sabin
> SQL Server MVP
> http://sqljunkies.com/weblog/simons
>
> "Jim Hubbard" <reply@groups.please> wrote in message
> news:lrE_f.2434$zh1.1351@bignews1.bellsouth.net...
>> Translation: This is going to be a tremendous pain in the ass.
>>
>> Got it!
>>
>> "Simon Sabin" <ContactThroughMyBlog@nospam.com> wrote in message
>> news:443ab9b3$0$2539$ed2619ec@ptn-nntp-reader02.plus.net...
>>> Transactional Peer to Peer replication is probably the answer, however
>>> it is
>>> not just as simple as installing it you need to consider how the stores
>>> own
>>> the data, i.e. who is allowed to modify what data. In Peer to Peer
>>> replication each store should only modify its data. For this reason your
>>> database design needs to be able to support this.
>>>
>>> You will also have common data shared across the sites, you will to
>>> decide
>>> how this is maintained.
>>>
>>> --
>>> Simon Sabin
>>> SQL Server MVP
>>> http://sqljunkies.com/weblog/simons
>>>
>>> "Jim Hubbard" <reply@groups.please> wrote in message
>>> news:QmgXf.3168$L6.2890@bignews5.bellsouth.net...
>>>>I have a client that desires a new application for use at several stores
>>>>in
>>>>different cities. He wants "real time" access to all store data and the
>>>>ability to continue to run locally even if the internet connection goes
>>>>down.
>>>>
>>>> It occurs to me that a local SQL Server 2005 instance should definitely
>>>> be
>>>> in each store to continue work if the net is down for any reason. But,
>>>> what is the best way to synchronize/share data among all of the stores?
>>>>
>>>> Any help that you give will be greatly appreciated.
>>>>
>>>> Thanks!
>>>>
>>>
>>>
>>>
>>
>>
>
>