The suggested workaround will allow you to have both Varchar and NVarchar fields in your final Physical Model. Let me illustrate it a little better:
- An entity has two attributes. We want Attribute1 to be NVarchar in the Physical model and we also want Attribute2 to stay as Varchar after the conversion.
- Let’s assign the Attribute2 a Domain. The Domain will be of Varchar type.
- Now change the Data Type Conversion Settings according to the image (and depending on your target database platform)
- Convert the model. As expected, all Varchar attributes have changed into NVarchar. But the Domain Varchar type has changed as well.
- No problem, just simply change it back to Varchar. Now all of your attributes that have Domain assigned will be Varchar again.
- And you’re done. The Domain only serves as a helpful tool to change data type or parameters of multiple attributes at once (you can read more about Domains here). When you try to generate SQL code, this is the result:
Another way is to create a Physical model
for SQL Server
and then convert it to an Oracle model
(or the other way around). See the Data Type Conversion Settings
for Microsoft SQL Server -> Oracle to see if this works for you.
I’m afraid we won’t be adding any more data types to the Universal Model, since it would go against its original purpose.
I’m not sure if I understand your problem with VarcharGraphic correctly, but if it converts to NVarchar, check the Data Type Conversion Settings and possibly change the destination data type to something else.