I am currently examining the options available to me for re-designing a database schema. Unfortunately the person that originally designed the database used GUID datatype for the primary keys and the clustered indexes (I'm well aware of the problems that this causes and it is now evident in the performance of the database).

Having read several articles, my intention is to use auto incrementing integer identity columns in each table - these will be used to form the clustered index.

My question is, **are there any dangers in using this column as the primary key?** 

Currently I've carried out tests in which I've used a combination of identity columns for the clustered index and GUIDs for the primary key and there has been a significant performance improvement. However, my understanding is that there will be even more performance improvements if I use the smaller identity column as my primary key too. My main concern is maintaining the integrity of identity values in relation to mirroring, etc - but perhaps I'm worrying about nothing.

We plan to eventually host the database on Azure 

Thanks