We are a sql 2014 transactional push replication setup, the publisher, distribution server and a subscriber are on-site and it is working. Recently I added a new SQl 2014 subscriber which is located in Azure cloud. This Azure sql server belongs to a workgroup in our Azure environment unlike the domain environment in our on-site data center. To address the connectivity issue, I added an entry of the azure sql server name and IP address in the Hosts file of the publisher Sql server and the distribution server. This allows me to add the new Azure subscription to the existing publisher. The snapshot generated successfully when I started the snapshot agent job. I see the table and its related replication stored procedures being generated in the Azure subscriber. However, when the distribution agent tries to sync the data to the subscriber, I see this "The process could not bulk copy into table". The confusing part about this error is that I am seeing a very small number of records being replicated to this azure subscriber table. For example, the publisher table has10,150,361 and the subscriber so far is stuck at 410,501 and not incrementing. There is no filter involved.
The replication monitor shows the following sequence of events:
Bulk coying data into the table 'xxxx' (about 10 of this line)
Skipping file 'xxxxxx_2#1bcp' because it has already been delivered for a previous article or by a previously interrupted snapshot";
skipping file"xxxx_2_sch' because it has already been delivered for a previous article or by a previously interrupted snapshot. Please advice on what the issue is and how to fix it.
Skipping file 'xxxx_2_pre' because it has already been delivered for a previous article or by a preiously interrupted snapshot.
Initializing
The process could not bulk copy into table 'xxxxxxxxx'
Then repeat and on and on.
Please advice on how to address this Azure subscription issue.
Thanks
OD.
Ocean Deep