D
Don
What is the best approach?
I've created a .NET 2.0 windows service which queries & updates data in SQL
using Stored Procedures.
Note, this windows service spawns a few worker threads which query/update
the database - thus ending up with multiple simultaneous database connections
(queries/updates).
Currently I've implemented transactions in the SQL SP (also using
XACT_ABORT, etc...), as WELL as the ADO.NET layer.
However, I've been told that its best to implement it just at the ADO.NET
layer.
The more I think of this, the more sense it makes.
Surely there's a best pratice for this!
I've created a .NET 2.0 windows service which queries & updates data in SQL
using Stored Procedures.
Note, this windows service spawns a few worker threads which query/update
the database - thus ending up with multiple simultaneous database connections
(queries/updates).
Currently I've implemented transactions in the SQL SP (also using
XACT_ABORT, etc...), as WELL as the ADO.NET layer.
However, I've been told that its best to implement it just at the ADO.NET
layer.
The more I think of this, the more sense it makes.
Surely there's a best pratice for this!