August 4, 2005 at 11:40 am
Hi,
We have a project with the following setup:
A primary site with the main server. Then we have several child sites with individual servers. All SQL Server 2000. The static data available on the child sites need to be available at the child sites and be kept in sync with the primary site. Changes to this data is only allowed from the primary site and these changes need to get filtered down to the child sites. At the child sites they will be capturing orders which need to be sent to the primary site once per day.
We are at this point considering using replication, but we have VERY little knowlege on the subject at the moment. I have done a bit of research on the subject, but I want to know what the limitations of replication is and if there is any problems that we would need to consider in the use of the said technoogy.
Any information and/or suggestions are very welcome.
Regards,
Stefan Venter.
August 5, 2005 at 5:03 am
I am confused with your requirements. You say the static data available on the child sides needs to be available at the child sites and kept in sync with the primary site.
Are you saying that the data on all child sites is not modified by database activity on the child sites? Does this mean that all database modifications occur on the publisher and needs to be replicated to the child sites?
If so transactional replication will work for you. If not, please explain how data flows.
--
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
August 5, 2005 at 5:03 am
I am confused with your requirements. You say the static data available on the child sides needs to be available at the child sites and kept in sync with the primary site.
Are you saying that the data on all child sites is not modified by database activity on the child sites? Does this mean that all database modifications occur on the publisher and needs to be replicated to the child sites?
If so transactional replication will work for you. If not, please explain how data flows.
--
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
August 5, 2005 at 5:15 am
Hi,
Sorry about the confusion, it is supposed to be primary site.
As such, static data will be managed from the primary site, child sites will never be able to modify the static data. The static data has a time constraint coupled to it in the sense that if an item is changed at the primary site it has to be filtered through to the child within a few minutes to reflect the changes.
Order data from the child sites is basically needed once a month for billing purposes during our month end process. Theoretically it would be fine to copy the day's transactions to the primary server once per day.
I hope this clarifies it a bit more.
Regards,
Stefan
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply