4 replaced http://stackoverflow.com/ with https://stackoverflow.com/
source | link

You can't guarantee contiguous or consecutive identity values in SQL Server

Also:

  • Loading a temp table doesn't guarantee consecutive values. Saying that, this is harder to prove, and works in practice (as many folk rely on it), but be warned...

You have to adapt to gaps in your numbering, however generated.

You can't guarantee contiguous or consecutive identity values in SQL Server

Also:

  • Loading a temp table doesn't guarantee consecutive values. Saying that, this is harder to prove, and works in practice (as many folk rely on it), but be warned...

You have to adapt to gaps in your numbering, however generated.

You can't guarantee contiguous or consecutive identity values in SQL Server

Also:

  • Loading a temp table doesn't guarantee consecutive values. Saying that, this is harder to prove, and works in practice (as many folk rely on it), but be warned...

You have to adapt to gaps in your numbering, however generated.

3 typo fixes
source | link

You can't guarantee contiguous or consecutive identity values in SQL Server

Also:

  • Loading a temp table doesn't guarantee consecutive values. Saying that, this is harder to prove, and works in practice (as maynmany folk rely on it), but be warned...

You have to adapt to gaps in your numbering, however generated.

You can't guarantee contiguous or consecutive identity values in SQL Server

Also:

  • Loading a temp table doesn't guarantee. Saying that, this is harder to prove, and works in practice (as mayn folk rely on it), but be warned...

You have to adapt to gaps in your numbering, however generated

You can't guarantee contiguous or consecutive identity values in SQL Server

Also:

  • Loading a temp table doesn't guarantee consecutive values. Saying that, this is harder to prove, and works in practice (as many folk rely on it), but be warned...

You have to adapt to gaps in your numbering, however generated.

2 added 60 characters in body
source | link

You can't guarantee contiguous or consecutive identity values in SQL Server

Also:

  • Loading a temp table doesn't guarantee (harder. Saying that, this is harder to prove, and works in practice (as mayn folk rely on it), but be warned)...

You have to adapt to gaps in your numbering, however generated

You can't guarantee contiguous or consecutive identity values in SQL Server

  • An insert of multiple rows won't guarantee this. See Do Inserted Records Always Receive Contiguous Identity Values
  • The current identity value stays incremented on rollback (either explicit ROLLBACK or implicit due to a CONSTRAINT error)
  • Loading a temp table doesn't guarantee (harder to prove, and works in practice, but be warned)

You have to adapt to gaps in your numbering, however generated

You can't guarantee contiguous or consecutive identity values in SQL Server

Also:

  • Loading a temp table doesn't guarantee. Saying that, this is harder to prove, and works in practice (as mayn folk rely on it), but be warned...

You have to adapt to gaps in your numbering, however generated

1
source | link