I have two SQL Server databases that I am trying to replicate. I am able to replicate small tables without any issues.
However I have a table with over 16 Billion rows that is quite problematic.
I am currently using transactional replication to replicate the large table. From the documents I have read online, when you select transactional replication, the process uses @sync_method = N'concurrent' parameter which is not suppose to lock the table, but when I initiate the process, the table seems to lock which renders it un usable. At the same time when I initiate the subscription i.e on the destination server, it also locks the table at the destination.
I would want to know what am missing or doing wrong such that the table locks. Remember that the table is also in use as the replication happens. So it should not lock at any given time.
Read committed snapshot isolation is already enabled on the database.And this is the initial snapshot that I am trying to run.