title: Unique identifier (guid) as primary key in database design
body: <p>Our data resides in a SQL Server 2008 database, there will be a lot queries and joinings between tables. We have this argument inside the team, some are arguing use of integer identity is better for performance, some are arguing use of guid (unique identifier). </p>
  
  <p>Does the performance really suffer that badly using a GUID as a primary key?</p>