Is there a recommended way to implement individual row-level change tracking? such that when a change is made to more than one row before a save is called, changes that the database doesn't reject move forward, the ones that don't aren't? I have am trying to figure this out for two projects a ticketing database, and an asset management database.

Say the user wants to change one asset from being an asset with no subtype to being a workstation asset. The database would reject this change without the additional required non-nullable workstation information. The user also filled out a completely new asset form which would save just fine. Using direct databinding for the controls. I now have a row which should be able to save its changes, and one that can not. Because of how linq-to-sql works neither change can be saved now.