They want us to store changes that a Patient makes to their information...Addressing...Allergies...Diseases...
So the Allergy changes and Disease changes imply a one-to-many relationship.
The Patient updates will come over via an API. We have been asked to log those changes and report on them. The client is proposing GUIDs as IDs. So we would capture the Patient Updates by a GUID that we have passed them upon enrollment. They would then pass us back the update via the API.
The client is proposing GUIDs for all of these IDs. I know GUIDs are not great for a clustered index.
So I was just looking for the Pros and Cons of using GUIDs as opposed to like an IDENTITY column.
I did find this web site...
[https://www.sqlshack.com/understanding-the-guid-data-type-in-sql-server/
Which kind of explains the whole GUID concept
Just looking for more content and opinion regarding this is all.