digdave7 (9/27/2010)

---

Hi Grant or(Anyone else) :),

Thanks for the reply; you're comments helped. I did want to ask (if you dont mind) for more feedback on the "migrate the keys" suggestion..? The end goal here is to shift the clustered index from the GUID to the BigInt column, if we can avoid dropping the indexes and migrate them, as you say that would be ideal. Is there a change index option rather then a drop and recreate..?

I didnt design the schema and picked up on this problem early on, but the research and valdiation took some time. Because of the qty of records I am looking at all options to balance this change with downtime.

For example:

TableID "Objects"

Index: PK_Objects on Object_ID (clustered, unique, primary key located on PRIMARY)

---I want to change it to TableID BigInt as the cluster, obviously there are other tables in question.