Re: Column...
From: José Araujo (josea_at_mcrinc.com)
Date: 08/18/04
- Next message: Charlie Nakagawa: "Re: Foreign Key"
- Previous message: Parag: "Re: Use of case statement in where clause"
- In reply to: Anith Sen: "Re: Column..."
- Next in thread: Anith Sen: "Re: Column..."
- Reply: Anith Sen: "Re: Column..."
- Messages sorted by: [ date ] [ thread ]
Date: Wed, 18 Aug 2004 17:25:30 -0400
Well... I consider that "logically impossible" is not correct.
SQL Server could "scan" the column to look for the max value... it could
just use the identity seed you proposed and let you live with the
consequences.
It might be not possible, but not because it is not logically possible, just
because SQL server doesn't have it implemented (so, it is, indeed,
impossible IN the current SQL version).
BTW: if I knew where in the system tables that information is storage I
would do it...
Thanks, José.
"Anith Sen" <anith@bizdatasolutions.com> wrote in message
news:ekobPYWhEHA.1768@TK2MSFTNGP10.phx.gbl...
> This is logically impossible since SQL Server has no way of knowing if the
> existing values in the column matches the proposed identity seed and/or
> increment.
>
> --
> Anith
>
>
- Next message: Charlie Nakagawa: "Re: Foreign Key"
- Previous message: Parag: "Re: Use of case statement in where clause"
- In reply to: Anith Sen: "Re: Column..."
- Next in thread: Anith Sen: "Re: Column..."
- Reply: Anith Sen: "Re: Column..."
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|