This content has been marked as final. Show 2 replies
If your database release/platform is supported by DMU, the best way is to run a DMU scan on your source instance to discover any potential data issues for migrating to AL32UTF8. You can then use DMU to cleanse the data exceptions and decide whether to migrate the database in-place with DMU or move to a separate instance depending on your requirements. Any reason why you want to change the NCHAR character set to UTF8?