title: SSMS renaming Keys also renames Clustered index to same name
body: <p>As the title states really.</p>
  <p>An example of this is;</p>
  <p>I set the primary key for a table which is a composite key made from multiple columns.
  I then rename the key name in the Keys folder to;</p>
  <pre><code>PK_tblname_column1_column2 
  </code></pre>
  <p>I then create a clustered index;</p>
  <pre><code>Create CLUSTERED INDEX C_U_tblname_column1_column2 ON tblname (Column1 ADC, Column2 ASC);
  </code></pre>
  <p>When I go to refresh the database, both of the names change to either PK or C_U so I get;</p>
  <pre><code>Keys - 
        PK_tblname_Column1_Column2
  Indexes -
        PK_tblname_Column1_Column2 (Clustered)
  </code></pre>
  <p>OR</p>
  <pre><code>Keys - 
        C_U_tblname_Column1_Column2
  Indexes -
        C_U_tblname_Column1_Column2 (Clustered)
  </code></pre>
  <p>Then, when I go to rename the Keys property back to <code>PK_tblname_Column1_Column2</code>, it automatically changes the Index property to <code>PK_tblname_Column1_Column2 (Clustered)</code> too.</p>
  <p>If I then proceed to rename the Index property back to <code>C_U_tblname_Column1_Column2 (Clustered)</code>. It saves. However, when I refresh the database again, it reverses back to either being named PK for both or C_U for both.</p>
  <p>Anyone know why this happens? Most of my clustered indexes just use the primary key columns as the clustered index but this also occurs on indexes that have more than the primary key columns included.</p>