In E/R Studio Data Architect V10, in a logical model, I created an Alternate Key on a field (actually doing this is many entities), with the intent that, when I generate a physical model, the table would automatically have a unique constraint, but NO index, on the column, because the actual target DBMS (Snowflake, not natively supported in E/R Studio), does not allow user-entered indexes. So far, I have made two attempts; both attempts failed to create the unique constraint. One attempt was to generate to a target physical platform of 'Generic DBMS', and the second was to 'Oracle 12c'. On page 2 of 5 in physical model generation process, I needed to leave the 'Generate Indexes for alt keys' option un-checked, due to the aforementioned characteristic of the target live DBMS.
So, my intent is to create an unique constraint in the logical model, which can be auto-generated in the physical model, so that I can then use the physical model to automatically generate ANSI-compliant DDL.
I believe that I could resolve this by manually creating unique constraints in the E/R Studio Physical Model, and/but...
1. Is that true?
2. Is there a way to get it done in logical, so it auto-generates as a unique key into physical, but without an Index?