SQL Server Replication
am 02.03.2005 14:09:51 von DavidCHolleyI'm looking at migrating the AccessDB backend of my website to
SQLServer. There will be a copy of the SQLDB sitting on my PC and
another copy sitting on the web server. The copy on the PC will be
considered the master.
How does replication work when access to the replicant is via IP?
Also, is it possible with replication to designate a table as one-way
only replication? For security reasons, I don't want changes in the
SQLDB tables on the web server to propigate back to my PC, with the
exception of 1 maybe 2 tables used to collect data from visitors. Think
of it as if I'm setting up an online catalog that allows orders. The
information on the products & pricing should be read-only to the user
and with changes NOT being propigated back. Information on the orders
placed should of course be propigated back. I'm thinking about
situations where someone might hack into the SQLDB on the webserver and
change information. If it should happen, after setting up appropriate
security to begin with, I don't want the changes to be sent back to the
master. (One last security measure to protect the original data.)
Where can I get more information on setting up the replication as well
as assorted isssued related to the topic?
David H