A:Yes, there is some overhead when the task issues the select statement on the source in order to get the data.
Q:If our target database is used by another development, will it be affected? Is there any possibility of data deadlock?
A: Yes, if the other application ever issues a lock on the target table rows that could cause an error for the Replicate task.
Q: Is there a way to setup a Notification that sends only a few e-mails when a Task has an Error or Task Stops because it can't connect to the Target and needs to stop? My experience has been that it fills my e-mail inbox with hundreds of pages. A: You can set up rules in your mail, or send notifications to the event viewer and have a program that scans the event viewer and sends emails based on the logic coded into the program.
Q: What happens in Replicate on a delete?
A: The delete will remove the record from the target. We do have a way to do a soft delete that will keep the record and mark it as deleted. Check out this article: Filter Deletes in Replicate
Q: The options available for tuning LOB handling when we use Log Stream as source as opposed to native application type source endpoint, are limited. So is there any way to explicitly pass the config options in task JSON configuration?
A:The LOB limitations on the LOG stream are by design and cannot be overridden.