Hello all,
I have a question about setting up a replication job.
We have SQL 2000 standard servers, running on Windows 2003.
We have a website that hosts Customer data, so we have a SQL server at our co-loc. There is one table of data that the clients can alter from the web site, so they can update their e-maill address, paper or paperless statements.. etc.
At our main office, our client services department has a client app that reads from this same table, off of our production sql server at our office.
Right now there is a job that pulls the info from the co-loc, and it only works one way... if the client updates their info on the website, it will be replicated up here, so our reps can see the new info in their client app.
However, if the client calls into customer service to update the info, and the client service rep enteres it into the application here,,, it will not get replicated down to the co-loc,,,,
actually, about 5 minutes later, the old info from the website will be pulled back up to our production database, overwriting the new legit info just entered...
Is there a way to setup a bi-directional replication of this one table,, so if the client updates it on the website it will get replicated to the production DB, and if a client service rep updates it on the production DB, it will get replicated back down to the website?
I hope I'm making sense..
Thanks everyone.
I have a question about setting up a replication job.
We have SQL 2000 standard servers, running on Windows 2003.
We have a website that hosts Customer data, so we have a SQL server at our co-loc. There is one table of data that the clients can alter from the web site, so they can update their e-maill address, paper or paperless statements.. etc.
At our main office, our client services department has a client app that reads from this same table, off of our production sql server at our office.
Right now there is a job that pulls the info from the co-loc, and it only works one way... if the client updates their info on the website, it will be replicated up here, so our reps can see the new info in their client app.
However, if the client calls into customer service to update the info, and the client service rep enteres it into the application here,,, it will not get replicated down to the co-loc,,,,
actually, about 5 minutes later, the old info from the website will be pulled back up to our production database, overwriting the new legit info just entered...
Is there a way to setup a bi-directional replication of this one table,, so if the client updates it on the website it will get replicated to the production DB, and if a client service rep updates it on the production DB, it will get replicated back down to the website?
I hope I'm making sense..
Thanks everyone.