Help Center/ Database and Application Migration UGO/ FAQs/ Evaluation Project/ What Is Native Compatibility, Conversion Compatibility, Partial Compatibility, or Incompatibility?

Updated on 2024-11-07 GMT+08:00

View PDF

What Is Native Compatibility, Conversion Compatibility, Partial Compatibility, or Incompatibility?

What is native compatibility, conversion compatibility, partial compatibility, or incompatibility?

Native compatibility: The object syntax of the source database is fully compatible with that of the target database.
Conversion compatibility: UGO can convert the object syntax of source database to be compatible with the target database.
Partial compatibility: UGO can convert the object syntax of the source database to be compatible with the target database, but there may be some performance or functional differences after conversion. Before performing syntax conversion, you can select a new conversion configuration that meets the customer's service requirements.
Incompatibility: UGO cannot convert the object syntax of the source database to be compatible with the target database.

Native compatible objects, conversion compatible objects, and partial compatible objects collectively referred to as UGO-supported objects.

Parent topic: Evaluation Project

Feedback

Was this page helpful?

Helpful Not helpful

Provide feedback

Thank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.

The system is busy. Please try again later.

Which of the following issues have you encountered?

Content is inconsistent with the product UI

Unclear descriptions

Lack of examples or code

Incorrect steps

Can't find what I need

Lack of best practices

Feedback (optional)

0/500

Select at least one type of issue, and enter your comments or suggestions.

Enter a maximum of 500 characters.

Submit Cancel

For any further questions, feel free to contact us through the chatbot.

Chatbot