SNIP

>>Second, check the clustered index. For best performance an 4byte autoincremental integer key is best. Since indexes will have a pointer to the clustered key it will keep the indexes as small as possible. The autoincrement will also prevent rows being moved from one page to another when the indexvalue of the clustered index changes.
>
>This is configured as an Active/Passive Microsoft Failover Cluster. SQL Server 2012 is installed on the cluster, which manages the failover process from one node to the other in the event of an issue with the active node. The two servers are configured identically so that one system can handle the load as well as the other upon failure of a node.

I'm talking about the type of index for the primary key on the database. If you make the integer primary key a clustered index, it will save you disk space and I/O for any handling the indexes. It would also avoid records being moved from one page to another as records are added.


I thought you mentioned it currently contains 4 million records. So a 4 byte integer field will be fine are long as you are not reaching 2 billion records.

Walter,