Thanks for the like, @ChrisNZ . Here are the details on what is migrated: Concepts: MIGRATE Procedure . For data sets,
PROC MIGRATE retains alternate collating sequence, compression, created and modified datetimes, deleted observations, encryption, extended attributes, indexes, integrity constraints, and passwords. See the link for more details.
There is a tricky scenario that tends to affect customers with DBCS data - If you are changing to a different character encoding that uses more bytes to represent the characters, you might need to use the CVP engine as part of the copy or migration process, to avoid truncation. This works fine with PROC COPY, but CVP is not currently supported by PROC MIGRATE. We like PROC MIGRATE better than PROC COPY for migration, so we came up with a workaround. It's a little complicated but we recommend a two-step process where you (1) COPY with the CVP engine on the source environment to avoid CEDA. Then (2) MIGRATE on the target to change the encoding and data representation. If the library has formats catalogs, you can use a two step process with PROC FORMAT to expand the length and avoid truncation.
... View more