Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
dbwilson4
Yak Posting Veteran
50 Posts |
 Posted - 2007-06-14 : 21:10:34
|
| Say a database is CRUDed against over 20 year period.By then, the ID column should be something like 398423948392489234893284 etc. We all know that int datatype can only address a certain amount. Does this mean that we have to change it to bigint when the time comes? |
|
|
Michael Valentine Jones
Yak DBA Kernel (pronounced Colonel)
7020 Posts |
Posted - 2007-06-14 : 21:17:14
|
| Depends on how many rows per day you are inserting. You could insert 190,000 rows a day, 365 days/year for 30 years witout overflowing an INT. If this limit seems too low for your application, then you should start with a BIGINT.CODO ERGO SUM |
 |
|
|
jezemine
Master Smack Fu Yak Hacker
2886 Posts |
Posted - 2007-06-15 : 02:22:51
|
over the last 24hrs I imported 1.5b rows of data. tomorrow the same. and in a couple weeks i'll have another few billion to import. i use a bigint. 
elsasoft.org |
|
|
|
Kristen
Test
22859 Posts |
Posted - 2007-06-15 : 04:09:54
|
| "Say a database is CRUDed against over 20 year period."Well the "D" suggests there will be some deletions! If you get to 398423948392489234893284 rows in your table you are going to have lots of things to worry about, int/bigint will only be one of them!You may need to allow for resetting the ID number at some point in the future, or some other strategy for reusing IDs perhaps?Kristen |
|
|
|
|
|
|
Curious DB questions