I've done this myself, but within a vb.net program that also generates vb code to treat it as a model. I believe later versions of Visual Studio provide this functionality.

However, something I also did was have the update stored proc only modify the row if something was actually different between the new data and old. Most update procs blindly update, even though there are no changes. With my version, no update takes place, and so the transaction log doesn't get modified. This was a very specific application where I had a large amount of data with minimal differences.