title: using bigint as non clustered key and guid/UNIQUEIDENTIFIER as primary key non clustered
body: <p>Having read many blogs, I have decided to create tables that have a guid/UNIQUEIDENTIFIER as primary key, however using a non clustered index and a bigint as clustered key.</p>
  
  <p>First of all what would be the correct DDL syntax in this scenario. Also, I would think that using the bigints as foreign keys would be the correct choice. Is this correct?</p>
  
  <p>Here is a starter for ten:</p>
  
  <pre><code>IF OBJECT_ID('dbo.Table1', 'U') IS NOT NULL
    DROP TABLE dbo.Table1; 
  
  CREATE TABLE dbo.Table1
  (
      [Table1Id] [BIGINT] IDENTITY(1,1) NOT NULL,
      [Table1Guid] [UNIQUEIDENTIFIER] NOT NULL,
      [PayLoad] NVARCHAR(200) NULL
  PRIMARY KEY CLUSTERED 
  (
      [Table1Id] ASC
  )WITH (PAD_INDEX = OFF, STATISTICS_NORECOMPUTE = OFF, IGNORE_DUP_KEY = OFF, ALLOW_ROW_LOCKS = ON, ALLOW_PAGE_LOCKS = ON) 
  ) 
  
  CREATE NONCLUSTERED INDEX IX_Table1_Table1Guid
      ON dbo.Table1 (Table1Guid); 
  GO
  </code></pre>