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 |
|
TorreyKite
Starting Member
40 Posts |
 Posted - 2005-12-31 : 10:43:05
|
| I have a table which the record Id field "DetailID" is an integer data type. This field increments automaticly.The problem is that it has become maxed out with more than 32k records and growing. I know that I need to change the datatype to something with more capacity.I was planning on changing it to Numeric.My questions:1)is this a good choice? or is there a better option that will still be a numerical ID (i'd rather stay away from the alpha numeric types like Uniqueidentifyer).2)Are there any pitfalls that I should be aware of when changing the datatype? Will existing data convert automaticly or need special attention?Thanks for your input!Regards,TKps this is using SQL Server 7.0 and interfaces with a VB app(ado) via Stored procedures. |
|
|
cshah1
Constraint Violating Yak Guru
347 Posts |
Posted - 2005-12-31 : 11:50:09
|
| if you are using integer data type for identity then it can handle more than 32KFROM BOL*****integer or int Has a length of 4 bytes, and stores numbers from -2,147,483,648 through 2,147,483,647.******if you think you might be need more than that use bigint |
 |
|
|
TorreyKite
Starting Member
40 Posts |
Posted - 2006-01-03 : 07:59:53
|
| I guess my limitation is only on the application side.Thanks. This helps a bunch.Regards,TK :) |
|
|
|
|
|
|
Data type conversion