Thank you. It is not possible to use a single SQL Server user that has access to multiple Invantive Data Replicator repositories stored in different databases.
When the Data Replicator driver is started, the software scans what databases the SQL Server user has access to. It determines for each database whether there is a Data Replicator repository by checking for the presence of the table
When there are multiple, it should raise an error. It is weird that it doesn’t display this one:
The user in the backing SQL database should have access to at most one repository. Multiple repositories are accessible.
Please make sure that the user has only access to exactly one repository.
It would be highly appreciated when you can send a trace file together with the settings*.xml files (without passwords) to our support system for evaluation.
When there is no database found, it should create such a table and all other tables of the repository in the current database.
When there is exactly one, it will use that database as the repository.
Summarizing: make sure a separate SQL Server user is used for each Invantive Data Replicator repository. Note that a single Data Replicator repository easily scales above 1 TB of managed data, so there is no need performance-wise to create different repositories. There might be security-wise, but in that case the SQL Server users should be split for the same time.
Relates to Incremental script - Exact Online met Datahub.