Discussion Locked

Implement SQL transactions with ADO.NET

0 helpful
2 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

This week's .NET e-newsletter discusses implementing SQL transactions with ADO.NET. Do you use SQL Server and/or ADO.NET in your development work? Will you use some of the tips in this column? What topics would you like to see Tony Patton cover in future editions of this e-newsletter?

If you aren't subscribed to the free .NET e-newsletter, click the link below to automatically sign up:
http://nl.com.com/MiniFormHandler?brand=builder &subs_channel=bldr_front_door&list_id=e605&tag=fb

2 replies

by mwaser

If you're going to implement transactions, do it within a stored procedure and call the stored procedure from ADO.NET.

Just because you CAN throw yourself in front of a speeding train doesn't mean that you should.

by angelom

I've been working with ADO.NET for a while and I still don?t get the point in forcing the assigning of the transaction object to the command object when this should been done automaticaly the way the oracle (from oracle) provider do. I've been force to encapsulate the hole mechanism inside a group of classes that made the job.

This discussion is closed to new replies.