As you know synthetic key is related to the way you associate your tables. Which means the naming of your fields should be carefully througt of. If you have tables that are associated using more than one field , it will cause the synthetic key phenomena.
1) drop field name: It can either mean to explicitly remove the field from you script or use the drop command to drop it if it is not needed
2) commenting field name this means use the double forward slash to comment the field which really means the same as explicitly removing the field from your script.
3) renaming field name rename the field using an alias. this is done by using the AS in your script. example
Month as specialMonth
4) using qualify keyword: When using qualify QV will prefix the field with the table name. SO when you look at the
table through table view, column names will be something like table name.column_name. Example
If you are having this issue, I suggest removing all fields that are redundant and apart of the issue.
Very specified to use to remove the syn key(if want to rename the field names at a time)
I hope you knew about synkey
Qualify- can be used to change the all the field names at a time
suppose we product table and field names
If we use qualify statement to product table then the result would be
Unqualify-it can be used to prevent the qualify statement for the specified fields in the same table and if we are not using unqualify statement at the end of the table, then its automatically applicable to use qualify statement for below table tables with respected table names
Below exp would helps you
Initially we have 3tables(suppliers,products,categories) but if you need to use qualify statement for 1st table(supliers) except some specified fields(suplrid,comp_name) in the same table as like below
//then the result would be in the data-model in the table we can view with field names
//If we are not using unqualify then the resullt would be