I have a production database i.e. where there are constant updates and I've configured this to be published to another server using Transactional Replication.
When I configure transactional replication I've been doing the following:
- disable access to the source database
- backup source DB then restore to subscription server
- configure replication
- re-enable DB access to our apps
The problem with this approach is scheduling in downtime, having to suspend all the various timed scheduled tasks we run and shutting down access to our various applications that are dependant on this database.
Can I just configure transactional replication without disabling access to the publishing database and the subscriber database will correctly catch up? i.e. are all the DML statements queued on the publisher and as soon as the subscriber is ready they are picked off and executed?