>No you wouldn't lose automatic update management.
>Yes it wouldn't check other modified fields.
>IMHO this setting (WhereType=1 KeyFieldsOnly) is what most applications need for most of the tables. I would prefer tracking other users' changes via a timestamp column rather than generating a long where clause (think you've 100 fields table and a where clause checks all of them).
I think that solution (timestamp column) would be specifically for SQL Server? How about local views, or other database servers?
Difference in opinions hath cost many millions of lives: for instance, whether flesh be bread, or bread be flesh; whether whistling be a vice or a virtue; whether it be better to kiss a post, or throw it into the fire... (from Gulliver's Travels)
