Merge Transactional With Updates
Merge Transactional With Updates
Triggers are created at publisher and subscriber 4. Conflicts may be there 5. Less performance 6. Subscriber may be of lower version 7. No need of MSDTC Transactional with Updates 1. SA, DA, LRA, QRA 2. Primary Key is must on published tables 3. Triggers are created at subscriber 4. No conflicts with immediate updates 5. High performance 6. It supports same version and only SS subscribers 7. MSDTC is required.
Note: Article(s) used in merge cannot be used in Transactional with updates and vice versa.
2. I have configure Transactional replication. There is an error "Primary Key violation in distribution". What may be the possible reason? Ans: * There may be a record in subscriber which is conflicting with publication table. i.e. There is duplicate record exist in subscriber. * Import rows from publisher table into subscriber table once.
3. Tell me some issues related to Transactional publication? Ans: Scenario1: Log Reader Agent was failing Database in publisher has gone into suspect mode. * Check error log * Data file was damaged * Recovered it * Now log reader working fine
On same database we have configured mirroring and mirror server was not online Scenario 2: Distribution Agent was failing Database in subscriber has gone into suspect mode. * Check error log * Data file was damaged * Publisher backups * Restore in subscriber with "Preserve Replication Settings"
Scenario3: Log Reader Agent was failing On same database we have configured both Mirroring and T.Repication. Mirroring state was disconnected i.e mirror server was down. Hence Log reader agent was failing. * Check Log Reader Agent history * Make mirror server online. * If not possible remove mirroring.