Some database designers think that, for consistency, if one table has a surrogate key, all tables in the database should. Others think that such a policy is too rigid. Which position do you support and why? Try to illustrate with an example.
Looking for opinions supporting either position! Just want to wrap my head around each concept's pros and cons.
Thank you!
Surrogate key is a key that can be used to represent an entity or object that are in the database or outside of the database.It is also available or visible for the application and users who use this.It is mainly used with modeled object.It is also a unique key.This key is generated by the system itself.This key value cannot be altered by the user .The used surrogate keys are incremented automatically.It doesn't have a contextual meaning.If a surrogate key is used , it should be null.Always try to reduce the excessive use of surrogate keys.
Some database designers think that, for consistency, if one table has a surrogate key, all tables in the database should. Others think that such a policy is too rigid. Which position do you support an...