SQL Subscription Publishing Considerations

1. The 2 SQL Servers that subscribe to the publication are best to be version consistent and cannot appear similar to the following:

Sql2008 r2[Release]-sql2008[subscription];

Sql2008 r2[Release]-sql2012[subscription]

2. Subscription release theoretically must subscribe to the publication database in the same LAN, but also can penetrate the LAN to try to achieve the following, information:

http://456852.blog.51cto.com/380820/100822

3.

When SQL Server publishing is scheduled:
The connection to SQL Server must be hostname. When Hostname,port was found and logged in with SQL Server account, it was found unable to parse the format Hostname,port. Although previously ip,port such formats are supported.

Client-side "aliases" I don't think I've solved this problem:

Reference: http://stackoverflow.com/questions/8212032/ Sql-server-replication-requires-the-actual-server-name-to-make-a-connection-to-t

I built a sql2012->sql2008.

Set the hint for sql2012 at the sql2008 Publisher the Subscriber selected does not meet the minimum version compatibility level for the selected publication. ”

Reference: http://social.msdn.microsoft.com/Forums/sqlserver/en-US/664c001a-ace0-4b4f-8545-e80cdc56856c/ Sql-server-2005-to-sql-server-2008?forum=sqlreplication
Build directly on 2012 to succeed.

SQL Subscription Publishing Considerations