...
Two databases are assigned as target for the publisher. If the primary one is active at the web application, then the secondary is the new target for the publisher. Last step will swap active database and initialize the web application when the publisher is finished. If not the primary is the active database, it is selected as the new target.
| Note |
|---|
The target databases must be publication databases, not editor databases. The data model is not similar. Id columns are “Identity specification = Yes” for editor database, but No for publication databases. Thus the publisher can maintain database relations even though only a subset of all data is copied to the publish database. |
The remote publish definition has a new section, where the new publish mode may be is enabled.
...
The instance name is that of the editor database itself and cannot be changed, is is displayed here as a reminder of where the target database is located. The publish engine can only publish data within the same instance since database links are not available in the limited Azure environment; editor database and primary and secondary databases are always in the same database instance.
...
A sql server login may be assigned to the publish engine, it is applied to the target database. Access to the editor database is already defined in its site definition, in the server.config file.
During the publish process the assigned new target database is emptied and filled with new data, but is not created as in the regular publish process.
...