Replication Server supports two Unicode datatypes, unichar and univarchar. Unicode allows you to mix different languages from different language groups in the same data server.
The unichar and univarchar datatypes behave exactly like the char and varchar datatypes, except that unichar and univarchar are Unicode datatypes and UTF-16 encoded.
unichar and univarchar values are always stored in UTF-16, regardless of Replication Server’s default character set. unichar is equivalent to char with respect to syntax and semantics; it is a fixed-width, non-nullable datatype. univarchar is equivalent to varchar; it is a variable-width, nullable datatype.
You can:
Replicate unichar and univarchar columns to replicate and standby databases
Use unichar and univarchar columns in the primary key of a replication definition
Use unichar and univarchar columns as searchable columns in a replication definition and in the where clauses of associated subscriptions and articles
Use unichar and univarchar columns as searchable columns in a function replication definition and in the where clauses of associated subscriptions and articles
Use unichar and univarchar columns when replicating to or from heterogeneous data servers
Replication Server supports unichar and univarchar data even when Replication Server’s default character set is not UTF-8. For example, Replication Server supports a scenario in which the default character set of the primary and replicate databases is UTF-8, and Replication Server’s default character set is ISO-1. However, such a scenario may restrict the use of non-ASCII characters in the replication definition’s where clause. If the Replication Server default character set is not UTF-8, Replication Server can replicate only unichar and univarchar characters in the ASCII-7 code range.
Adaptive Server supports Unicode datatypes only when
the server’s default character set is UTF-8. If you are
using non-Sybase data servers, see your server’s documentation
for Unicode requirements.
