I want to know that whether synthetic keys degrade front end performance or not , I know if they are present at the back end they will tale more loading time , but I am not sure whether they will degrade front as well.
How you are seeing synthetic keys in Front-End. Because, Synthetic keys happened only in Back end i assume. So, synthetic keys are not good the reason is data model looks like references. So, It may kills the model as neat and clean.
Best Anil, When applicable please mark the correct/appropriate replies as "solution" (you can mark up to 3 "solutions". Please LIKE threads if the provided solution is helpful
A synthetic key is simply a compound key made up of two or more columns associating one or more tables. If this is what your data model requires, then leave them in. They will perform no better and no worse than a compound key built in your load script.
Having said that, the issue with synthetic keys is that they often arise in a poorly designed data models or after an error such as forgetting to drop a temporary table. This can result in a whole cohort of associated or partially associated synthetic keys which will degrade performance and possibly mangle the results of your metrics, as well as leading to partially decoupled tables because of logical loops.
Logic will get you from a to b. Imagination will take you everywhere. - A Einstein
