View Revisions: Issue #4168
| Summary | 0004168: SQL-Server capture rows that exceed 4000 characters | ||
|---|---|---|---|
| Revision | 2019-11-27 17:12 by elong | ||
| Description | Add sym_trigger.use_capture_lobs support for SQL-Server create table t1 ( id int not null primary key, f1 nvarchar(100) not null, f2 nvarchar(4000) null, f3 nvarchar(200) null, created datetime2 not null, modified datetime2 null ) https://sourceforge.net/p/symmetricds/discussion/739236/thread/99b3f8d861/ |
||
| Revision | 2019-11-27 17:14 by elong | ||
| Description | Add sym_trigger.use_capture_lobs support for SQL-Server. Convert to LOB with: cast(N'' as nvarchar(max)) + create table t1 ( id int not null primary key, f1 nvarchar(100) not null, f2 nvarchar(4000) null, f3 nvarchar(200) null, created datetime2 not null, modified datetime2 null ) https://sourceforge.net/p/symmetricds/discussion/739236/thread/99b3f8d861/ |
||
| Revision | 2019-11-27 17:12 by elong | ||
| Steps To Reproduce | |||
| Revision | 2022-10-26 20:24 by pmarzullo | ||
| Steps To Reproduce | 1. Create a table in SQL Server with a column that is defined as varchar(4000) at both source and target, and several more columns. 2. Insert a record with 4000 characters in the column. 3. The target staging file will have truncated data and cause a protocol error. |
||