Align SQL table definitions
For successful cloud migration and data upgrade, the on-premises source table objects and the corresponding online table objects must have the same definitions for the following properties:
- Primary keys
- Field names and data types
These properties are indicated by an asterisk *
in the following code snippet:
table id **MyTable
{
fields
{
field(1;*MyField1; *Integer)
{
}
field(2;*MyField2; *Integer)
{
}
}
keys
{
key(*Key1; *MyField1)
{
Clustered = true;
}
key(Key2; MyField2)
{
}
}
Other properties of tables, like the following, are either not required to match or the difference can be handled by table mapping during cloud migration setup.
- Different tables names can be handled by table mapping. In the previous code snippet, the table name is indicated by
**
. - Missing fields or extra fields in tables can be handled by table mapping
- Different IDs aren't relevant and don't affect cloud migration
- Different secondary keys aren't relevant and don't affect cloud migration
Note
These properties must match to upgrade Dynamics NAV to Business Central on-premises.
Next steps
피드백
https://aka.ms/ContentUserFeedback
출시 예정: 2024년 내내 콘텐츠에 대한 피드백 메커니즘으로 GitHub 문제를 단계적으로 폐지하고 이를 새로운 피드백 시스템으로 바꿀 예정입니다. 자세한 내용은 다음을 참조하세요.다음에 대한 사용자 의견 제출 및 보기