Timeline for Why is IDENTITY_INSERT ON only allowed on one table at a time?
Current License: CC BY-SA 3.0
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Feb 23, 2012 at 14:37 | vote | accept | Zelda | ||
| Feb 12, 2012 at 4:18 | comment | added | Aaron Bertrand | I wasn't suggesting the duplicate ID problem was a reason for the hard limit. | |
| Feb 12, 2012 at 0:01 | comment | added | Zelda | @AaronBertrand But again, the duplicate ID risk is exactly the same on any table with IDENTITY INSERT on, why the hard limit? I think the fact that it persists only for the connection makes much more sense as a precaution. | |
| Feb 11, 2012 at 14:46 | comment | added | Aaron Bertrand |
+1 I think your last point about duplicates is missed by a lot. Folks think if they set IDENTITY it also becomes a unique constraint. Very easy to disprove, of course, if they though to try.
|
|
| Feb 10, 2012 at 19:14 | history | answered | JNK | CC BY-SA 3.0 |