StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

POWhy database designers do not make IDENTITY columns start from the min value rather than 1?
primarykey
Id
12176944
data
AcceptedAnswerId
12177009
AnswerCount
6
ClosedDate
CommentCount
2
CommunityOwnedDate
CreationDate
2012-08-29T11:32:40.600
FavoriteCount
4
LastActivityDate
2013-06-04T14:15:04.013
LastEditDate
2012-08-30T09:53:26.003
LastEditorUserId
182467
OwnerUserId
992406
ParentId
0
PostTypeId
1
Score
40
ViewCount
3225
LastEditorDisplayName
text
Body
As we know, In Sql Server, The <code>IDENTITY (n,m)</code> means that the values will start from <code>n</code>, and the increment value is <code>m</code>, but I noticed that all database designers make Identity columns as <code>IDENTITY(1,1)</code> , without taking advantage of all values of int data type which are from <code>(-2,147,483,648) to (2,147,483,647)</code>, I am planning to make all Identity columns as <code>IDENTITY (-2,147,483,648, 1)</code>, (the identity columns are hidden from the application user). Is that a good idea ?
Tags
<sql><sql-server><database><database-design>
Title
Why database designers do not make IDENTITY columns start from the min value rather than 1?
singulars
PostAcceptedAnswerId
1. PO
 singulars
 PostTypePostTypeId
 PTAnswer
PostParentId
1. This table or related slice is empty.
PostTypePostTypeId
1. PTQuestion
UserLastEditorUserId
1. USAlex Bagnolini
UserOwnerUserId
1. UShoussam
plurals
PostLinksPostIdRelatedPostId
1. PL
 singulars
 LinkTypeLinkTypeId
 LTLinked
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. This table or related slice is empty.
PostsParentIdCreationDate
1. PO
 singulars
 PostTypePostTypeId
 PTAnswer
2. PO
 singulars
 PostTypePostTypeId
 PTAnswer
3. PO
 singulars
 PostTypePostTypeId
 PTAnswer
VotesPostIdCreationDate
1. VO
 singulars
 PostPostId
 POWhy database designers do not make IDENTITY columns start from the min value rather than 1?
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
2. VO
 singulars
 PostPostId
 POWhy database designers do not make IDENTITY columns start from the min value rather than 1?
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
3. VO
 singulars
 PostPostId
 POWhy database designers do not make IDENTITY columns start from the min value rather than 1?
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
CommentsPostId
1. CORelated: http://stackoverflow.com/questions/4451967/why-doesnt-sql-server-support-unsigned-datatype
 singulars
 PostPostId
 POWhy database designers do not make IDENTITY columns start from the min value rather than 1?
 UserUserId
 USJon Egerton
2. CODoesn't SQL Server have an unsigned type?
 singulars
 PostPostId
 POWhy database designers do not make IDENTITY columns start from the min value rather than 1?
 UserUserId
 USBrendan Long

Querying!

Guidance

A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.