How about DME Files, do they have limitations?

Situation

DME files in DATPROF Subset and Privacy are used to exchange metadata models.

DME stands for DATPROF Metadata Export.

You might choose to create your own DME file to quickly define foreign keys in Privacy or Subset.

This can be very convenient, but are there any limitations?

Explanation

Yes, there are some important limitations to keep in mind:

No multi-schema support:

DME files do not support multiple schemas. If your foreign key relationships span across different schemas, they will not be recognized or processed correctly.

Case sensitivity:

All names in DME files are enclosed in double quotes. This means that case matters. If your database tables and columns are in uppercase but your DME file uses lowercase, you may encounter errors or mismatches.

DME keywords must be written in CamelCase. This includes:

• Table

• Column

• ColumnPair

• Relation

• Using incorrect casing for these keywords will cause the file to be invalid or ignored.