Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>You have hit upon one of the major "holy wars" of database design. The debate you're referring to is the "surrogate vs. natural key" argument that's been raging for as long as there have been RDBMSs (as nearly as I can tell).</p> <p>The debate essentially boils down to whether a representative key (surrogate, for example an IDENTITY column) should be used versus using the actual data that uniquely describes a record (natural key).</p> <p>I will say that there is no "right" answer. Performance measures are an artifact of the platform, and should be assessed by experimentation, but performance is not likely to be the major concern.</p> <p>What I consider to be the primary argument for surrogate keys is the immutability of primary keys. If you choose to use a natural key, you give up the option of altering that key after it is established. You also give up the possibility that it may become non-unique at some point in the future. For those reasons, I typically (not always) use surrogate keys for most of my tables.</p> <p>However, as I mentioned, there is a very long-standing debate filled with discussions of indexing strategies and normal-form adherance to be read if you are so inclined.</p> <p>I would Google "surrogate vs. natural keys". Here are a few links to get you started:</p> <p><a href="http://decipherinfosys.wordpress.com/2007/02/01/surrogate-keys-vs-natural-keys-for-primary-key/" rel="nofollow noreferrer">Systems Engineering and RDBMS</a></p> <p><a href="https://web.archive.org/web/1/http://articles.techrepublic%2ecom%2ecom/5100-10878_11-1045050.html" rel="nofollow noreferrer">Techrepublic</a></p> <p><a href="http://sqlblogcasts.com/blogs/tonyrogerson/archive/2006/05/11/427.aspx" rel="nofollow noreferrer">Tony Rogerson's blog</a></p> <p>Hope this helps.</p>
    singulars
    1. This table or related slice is empty.
    1. POWill SQL Server 2005 penalize me for using an nvarchar(50) as a primary key, instead of an integer?
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USCommunity
    1. USJared
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POWill SQL Server 2005 penalize me for using an nvarchar(50) as a primary key, instead of an integer?
      singulars
      1. PTQuestion
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. This table or related slice is empty.
 

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.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload