1 Answer
- Newest
- Most votes
- Most comments
0
this is expected behaviour. During continuous replication or rather CDC DMS will lookup transactions in source tlog. Transactions monitored are DMLS/DDLS pertaining to tables in scope. Please note SQL server wont log the the actual lob column data in tlog as part of the transaction. Thus every insert update delete captured in active tlog by DMS will trigger a lob lookup on source required to be applied to target.
answered 2 years ago
Relevant content
- asked 2 years ago
- Accepted Answerasked 7 years ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 6 months ago
I appreciate the reply, but I'm wondering about the line you have 'SQL Server wont log the actual lob column data in the tlog'? If that actual lob data is not stored in the transaction log, then how can you restore a SQL Server database to a point in time using the transaction log if you are saying that lob data is not stored in the transaction log? I understand if you use the write clause for example in an UPDATE that this a minimally logged but this is only a specific scenario. For example if I have a Table A in my Database A I which has one column of type text. If i perform an insert on that table, it will get written to the log, take a log backup, then delete that row from the table, If I restore the log backup I just took it will contain the text column, if it is not actually stored in the tlog then where would it be able to get this data from? Many Thanks.