27 июн. 2012 г. · Int is the Best type for Id column in a table in SQL Server. If the table eventually has too many records we can change to BigInt.

22 дек. 2009 г. · I personally use INT IDENTITY for most of my primary and clustering keys. You need to keep apart the primary key which is a logical ...

16 мар. 2021 г. · You basically have three choices for an auto-generated id: int (typically 4 bytes); bigint (typically 8 bytes); universal unique identifier ...

23 дек. 2022 г. · 1 Answer 1 · If you have data that is uniquely identified by a short human-readable string then you can use VARCHAR2 or CHAR as a primary key.

31 мая 2009 г. · Any integer type of sufficient size to store anticipated data ranges. Generally 32 bit ints are viewed as too small (rightly or wrongly) for tables with a lot ...

23 янв. 2014 г. · It is always recommended to use int type for id fields in SQL tables - I find some similar answers here, here and here. But in all these questions id field is ...

10 мар. 2021 г. · You can find the code associated with each built-in data type by looking it up in Oracle's built-in data type documentation or by using the DUMP function.

23 янв. 2010 г. · Use the smallest type of INT that really suits your need; if you have 10-20 distinct values to handle - use TINYINT.

16 мая 2016 г. · Decimal would never be a good idea. I would go with bigint for your application. GUID is useful when you don't want ids to be sequential or ...

6 мая 2013 г. · I would go for CHAR(13) with a CHECK constraint (a CLR user-defined data type might also be an option).