Timeline for SQL query for finding a set of columns that create a unique key for a table
Current License: CC BY-SA 3.0
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jul 31, 2016 at 7:51 | history | edited | Tom V |
RDBMS tag
|
|
| Jul 30, 2016 at 4:26 | comment | added | Peter Vandivier | When I see a production table without a PK, I often find that the uniqueness of the PK has already been violated. A code-based solution may get you candidates for a unique column set, but the only way to really know what the proper purpose ( and PK ) of the table should be is to talk to people who use it and the application that fronts it. | |
| Jul 29, 2016 at 18:24 | vote | accept | YonkeyDonk64 | ||
| Jul 29, 2016 at 16:56 | answer | added | Lennart - Slava Ukraini | timeline score: 5 | |
| Jul 29, 2016 at 16:49 | comment | added | Jonathan Fite | Do you not have any guesses as to what would be a good unique key? I would start there. As for how to tell, SELECT DISTINCT Col1, Col2, etc FROM table and compare the row counts to the raw table. | |
| Jul 29, 2016 at 16:11 | review | First posts | |||
| Jul 31, 2016 at 7:51 | |||||
| Jul 29, 2016 at 16:06 | history | asked | YonkeyDonk64 | CC BY-SA 3.0 |