This might be a total noob question, but are there situations where you would not use UNIQUEID()? Or maybe not necessary to? Or is it just best practice to always use UNIQUEID() for future-proofing?
For example, I have this table to list all the Daylight Savings Times, and I know that for this small app, there will be no other table using years as a key. Would creating a UNIQUEID() key for it be overkill? Using the years as key would at least help readability on the parent table when I need to take a look at the spreadsheet, right?
If a table's substantive data includes a column with reliably unique values, such as Year in your example, IMHO it's fine to use that column as the key.
Yes.
In your case, I would not use UNIQUEID().
User | Count |
---|---|
33 | |
29 | |
29 | |
20 | |
18 |