I'll agree with Steve on the Clustered indexes. I personally have a rule, rules are made to be broken though, that every table had a clustered index.

Never make the clustered index on a sequential key, at least if there are a large number of transactions inserting at once.

As far as the duplicate index, that is a waste, the optimizer "should" be using Index 1 for searches against Field1, Field1 and 2, or all three fields. So Index 2 is probably rarely used.

KlK, MCSE