Deferred constraint checking?
Another discussion we've had on the local mailing lists lately has been around whether or not the ability to defer constraint checking (at least foreign key constraints) until the end of a transaction would be useful in SQL Server.
I see a lot of convoluted update code from things like ADO.NET datasets that would be greatly simplified if you could say:
a) start a transaction
b) send all the updates in any order
c) commit the transaction (and check the RI constraints at this point)
I'd love to hear your thoughts. Oracle has had it for a long time. Would you find it useful? If so, vote for it here: http://lab.msdn.microsoft.com/productfeedback/viewfeedback.aspx?feedbackid=8830bd75-ec68-4e8f-a4e5-3ab293a979db