title: Multiple "ID" columns in SQL Server database?
body: <p>Via <a href="https://stackoverflow.com/questions/713430/clustered-primary-key-on-unique-identifier-id-column-in-sql-server">this</a> link, I know that a GUID is not good as a clustered index, but it can be uniquely created anywhere. It is required for some advanced SQL Server features like replication, etc.</p>
  
  <p>Is it considered bad design if I want to have a GUID column as a typical Primary Key ? Also this assumes a separate int identity column for my clustering ID, and as an added bonus a "user friendly" id?</p>
  
  <p><strong>update</strong></p>
  
  <p>After viewing your feedback, I realise I didn't really word my question right. I understand that a Guid makes a good (even if its overkill) PK, but a bad clustering index (in general). My question more directly asked, is, is it bad to add a second "int identity" column to act as the clustering index?</p>
  
  <p>I was thinking that the Guid would be the PK and use it to build all relationships/joins etc. Then I would instead of using a natural key for the Cluster Index, I would add an additional "ID" that not data-specific. What I'm wondering is that bad? </p>