this may sound silly - but could someone tell me the consequences of
either not having constraints (keys) in tables while doing the DB
design, or during the design - dropping the constraints?
We have a couple of tables that are keyed on the first column which is an
IDENTITY column e.g. process ID. When we try and insert into the table.
There are no triggers involved or SELECT INTOs which are listed as known
problems in early 6.5 releases.
INSERT INTO (col2, col3, ....)
values (col2value, col3value, ....)
On more than one occasion, a key violation has occurred (on more than one
of the tables).
Does anyone know how we can rectify this and its cause?
I seem to vaguely remember seeing a bug listed on this but now can't find it
on the Microsoft support site.