...
- Editor database server: hosting one SqlServer database for the editor server
- Source database, the editor database, hosted at: DatabaseServerComputer
- Editor server hosting the server application: EditorServerComputer
- Target database: local database at EditorServerComputer created each time a publication is run
Requirements
There are some requirement to setup Signifikant to use a separate, external database server computer, for publishing. The publisher copies data from the source database to a target database, the latter is on editor server file system.
The copy process uses a link between the source- and target- databases. Initially the target is empty, it is filled up during the publish process when data is pushed to the target. The target database files are detached at the end, to be freed to be uploaded to a remote web-server.
Link and login
This link is created in the source database using a priviledged privileged account, to have all rights to do this.
- So you’ll need to create an SqlServer login in the source database: in the sysadmin SYSADMIN role.
- Also add a User Mapping to the master database for the account
- Then enter the login/password it in the server configuration file: server.config.
- To enable full access to target databases at the editor server, add login/password to the editor server SqlServer instance.
We suggest to use same login/password in source and target to keep things simpler. And ensure all protocols are enabled on the target SqlServer instance, use SQLServerManager15.msc to manage protocols and restart the SqlServer instance afterwards
More details below.
A
This is the address/login to the target database, it is a local database at the editor server. It is used to attach to the database from the external editor database server.
...