Luis Cazares:

I was thinking more about your post and realized I was unsure whether I had for sure turned back off Identity Insert for each table I recently ported to sql. However, I reviewed the records that have recently been added (since I did the migration in the last couple days) via users in the MS ACCESS front end application. the ID still seems to be incrementing correctly, with seed re-set as expected.

So is this statement (my understanding) correct?:

Failure to turn IDENTITY INSERT off has the following consequence...it would allow someone to execute a sql statement that specifies a value for the identity column. But that's it. It does not mean the incrementing will be turned off, nor that the seed will be anything other than expected.

Basically I'm trying to make sure I understand the full impact of , if I forget to turn it back off. It's basically just leaving it 'open' for explicit value insert, which could, if it occurred, cause what problem - it still wouldn't allow duplicate, would it?