Re: stored procedure to capture identity values
From: Hassan (fatima_ja_at_hotmail.com)
Date: 08/01/04
- Previous message: David Portas: "Re: stored procedure to capture identity values"
- In reply to: David Portas: "Re: stored procedure to capture identity values"
- Next in thread: David Portas: "Re: stored procedure to capture identity values"
- Reply: David Portas: "Re: stored procedure to capture identity values"
- Messages sorted by: [ date ] [ thread ]
Date: Sat, 31 Jul 2004 23:59:06 -0700
Hmmm.. what about storage of numeric vs int ? Worth a thought.. but some of
our tables are already in the second portion of my initial message.. Had to
reseed and stuff..
"David Portas" <REMOVE_BEFORE_REPLYING_dportas@acm.org> wrote in message
news:j9OdnfHrfcmgEZHcRVn-ig@giganews.com...
> Seems like a lot of trouble to little benefit. Why not just go through and
> select the appropriate datatype for each IDENTITY so that there's no
chance
> of running out of values during the lifetime of the system. NUMERIC can go
> up to 10^38. Surely that's enough for you?
>
> --
> David Portas
> SQL Server MVP
> --
>
>
- Previous message: David Portas: "Re: stored procedure to capture identity values"
- In reply to: David Portas: "Re: stored procedure to capture identity values"
- Next in thread: David Portas: "Re: stored procedure to capture identity values"
- Reply: David Portas: "Re: stored procedure to capture identity values"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|