Timeline for Determining whether column in view can only contain unique values
Current License: CC BY-SA 3.0
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Nov 20, 2012 at 20:42 | vote | accept | Bernard | ||
| Nov 20, 2012 at 1:02 | history | tweeted | twitter.com/#!/StackDBAs/status/270693721719328769 | ||
| Nov 20, 2012 at 0:28 | answer | added | Kevin Feasel | timeline score: 3 | |
| Nov 19, 2012 at 23:28 | comment | added | mrdenny | No, querying the data using the query like you've shown is your only option. | |
| Nov 19, 2012 at 23:26 | comment | added | Aaron Bertrand | I really doubt it. If you haven't been able to declare a specific column or combination of columns as unique, and there aren't any duplicates there now, how is SQL Server going to tell the future, and know whether you might stuff a duplicate in there tomorrow? | |
| Nov 19, 2012 at 23:23 | review | First posts | |||
| Nov 20, 2012 at 10:31 | |||||
| Nov 19, 2012 at 23:08 | history | asked | Bernard | CC BY-SA 3.0 |