title: Creating a SQL database without defining primary key
body: <p>So in my work environment we don't use a 'primary key' as defined by SQL Server. In other words, we don't right click a column and select "set as primary key".</p>
  
  <p>We do however still have primary keys, we just use a unique ID column. In stored procedures we use these to access the data like you would in any relational database.</p>
  
  <p>My question is, other than the built in functionality that comes with defining a primary key in SQL Server like Entity Framework stuff etc. Is there a good reason to use the 'primary key' functionality over just using a unique ID column and accessing your tables with that in your own stored procedures?</p>
  
  <p>The biggest drawback I see (again other than being able to use Entity Framework and things like that) is that you have to mentally keep track or otherwise keep track of what ID relates to what tables. </p>