Primary Keys are important to uniquely identify values in a table. A standard integer based primary key is fine for most databases.
Sometimes more than one unique identifier is implemented in a database table. This second unique identifier may be used to reconstruct records or be passed down to child tables.
In the event you do plan to implement two unique keys using an MSSQL database it can be done using triggers.
That means every time you add a new row record a GUID (e.g. 14E89334-05D0-4D1B-B85D-BFF7251AE41A ) gets created and inserted by the database to the table field automatically.
This value is set to NULL in the create table script, so you are not forced to enter a GUID as the new row is added via ANM10.
e.g. <GUIDField>] [uniqueidentifier] NULL,
In ANM10 you can leave the "required" checkbox empty based on the "NULL" setting not requiring data to be entered on row insert..
In ANM10 you can deselect the "Add" checkbox so the empty field is not visible when you Add/Insert the new record
In ANM10 you can Select the "Edit | Read Only" checkbox to ensure the GUID does NOT get modified during editing.
In ANM10 DO NOT select the GUID as the 2nd Primary Key in the Table properties checkbox.
A sample MSSQL trigger to do this is shown below;
CREATE TRIGGER <Table>_GUID_Trigger ON [Schema].[Table] AFTER INSERT AS BEGIN
UPDATE [Schema].[Table] SET [<GUIDField>] = NEWID() FROM INSERTED