Was reading one of the articles posted on Sql-server-performance.com and had quick question.... Our developers have started putting all basic CRUD into store procedures and I've noticed, that, particularly with Update SP's, that they've also included an update on the FK columns in the table even though the data, most likely hasn't changed.(GoodNews: They're not updating the PK's in these generic SP's) In monitoring SHOWCONTIG on these tables, it appears that the indexes on these FK columns, at least from a Scan Density perspective, are deteriorating rapidly. I guess my question is do you have any good articles/information on whether or not its good practice to update FK columns even when the data hasn't changed. From what I've found so far, it appears that it's not best practice, and for the most part, FK's rarely change and most applications don't touch them after they've been inserted. Pardon my ignorance, but I'm told that this is the easiest way to leverage the .Net Datasets and use a stored procedure to do the related work. Do you know of any work arounds, either on the .Net side or on the SQL server side, without having to deviate too far from basic CRUD, where Updates statements only update the columns that have really changed.