View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0002558 | SymmetricDS | Bug | public | 2016-04-11 13:48 | 2020-07-22 17:56 |
Reporter | gilles.riand | Assigned To | |||
Priority | normal | ||||
Status | closed | Resolution | no change required | ||
Product Version | 3.7.32 | ||||
Summary | 0002558: MSQLSERVER nvarchar field is scramble (???) at target | ||||
Description | Try to replic a TABLE with SQLServer 2014 with a Field for exemple 'NAME' in nvarchar(50) if you put this text : 'ជំរាបសួរ' in the field.... you will get '?????' in the remote node Because the field sym_data is typed as text and not in ntext ! | ||||
Tags | character encoding, dialect: sql-server | ||||
|
Try setting this property in your engine properties file: mssql.use.ntypes.for.sync=true |
|
i tried mssql.use.ntypes.for.sync=true but the unicode data sent to destination node still error |
|
After you change parameter to mssql.use.ntypes.for.sync=true, you need to restart SymmetricDS. It should alter sym_data to use ntext type for row_data, old_data, and pk_data fields. Also, force the triggers to rebuild so they handle character data with nvarchar by running "symadmin sync-triggers -f". |
Date Modified | Username | Field | Change |
---|---|---|---|
2016-04-11 13:48 | gilles.riand | New Issue | |
2016-04-15 19:58 | elong | Note Added: 0000783 | |
2019-04-24 12:36 | elong | Tag Attached: data sync | |
2019-04-24 12:36 | elong | Tag Attached: dialect: mssql | |
2019-04-24 12:50 | admin | Tag Renamed | dialect: mssql => dialect: sql-server |
2019-04-26 13:31 | elong | Tag Attached: character encoding | |
2019-04-26 13:31 | elong | Tag Detached: data sync | |
2019-05-09 15:08 | elong | Assigned To | => elong |
2019-05-09 15:08 | elong | Status | new => feedback |
2019-05-09 15:09 | elong | Assigned To | elong => |
2019-05-09 15:10 | elong | Summary | MSQLSERVER et UTF8 => MSQLSERVER nvarchar field is scramble (???) at target |
2019-09-21 15:08 | toilv | Note Added: 0001604 | |
2020-05-20 18:12 | elong | Relationship added | related to 0001766 |
2020-05-20 18:15 | elong | Note Added: 0001717 | |
2020-07-22 17:56 | elong | Status | feedback => closed |
2020-07-22 17:56 | elong | Resolution | open => no change required |