Premise: The publication of the subscription can only be used on the same intranet machine, in fact, this can be configured with the Configuration Manager alias function can be set, the external network can also be done in this way.
The configuration process references old D's article: http://www.cnblogs.com/daizhj/archive/2009/11/18/1605293.html
SQL Server Publish subscription feature test:
(I found this function is not good, why not, I have one of the following settings error will be all over again, then if I have hundreds of machines below, how to do it again? )
1, the use of the release subscription mechanism can only be read and write separation scheme, that is, a release B subscription, can only operate a data, B is synchronized, even after the addition of B, a will not be added.
2, 2008 when creating a new subscription, if the input error, is unable to find the subscription, can only delete the publication, and then to re-engage.
3, 2008 If the database connection port changes, not the 1433 default, then the two ends of synchronization will not work, even if the configuration Manager to create a new alias, it is not possible. (The last discovery is yes, if you create a new alias, you want to delete the original release and rebuild)
Research on SQL Server publish subscription function