|
|
Posted by Damien on 11/24/06 08:29
bfausti@gmail.com wrote:
> I have never used replication before and I have been asked to consider
> it in a project I am currently working on.
>
> I have created an application for a sales team which is loaded on their
> machines, it uses ms sql as its data source and connects via the
> internet back to the central server in the office.
>
> Problem is this has shown to be too slow causing time out error
> messages and so on. I have been told to research the possibility of
> replication, but am unclear what type of replication to use or where to
> start.
>
> Any assistance would be appreciated.
>
> Regards,
>
> Ben
Hi Ben,
Books On Line can be quite helpful, since it describes what is
available, and typical characteristics of situations in which you would
apply each type of replication.
Typical questions you have to ask yourself are where data is going to
be updated (at the central server, at the remote machine, both), how
frequently data changes, how rapidly data needs to be transferred to
other machines, etc.
For instance, if each sales team member needs to be able to access and
update all data (and be offline for long periods?), then you probably
would be looking at merge replication. If the sales team members should
only have access to some subsets of the data (e.g. They're only allowed
to view their own sales history), then you'd still be looking at merge,
but you'd also want to look at dynamic filters.
On the other hand, if the central server is only hosting catalog
information, and everything else is only dealt with locally, then
snapshot replication would probably be more appropriate.
Damien
Navigation:
[Reply to this message]
|