transaction in WS

[Ken]

hi

I have an Async WS updating my SQLserver DB
80 clients are connecting to the WS all day updating the DB
I have only ONE UPDATE instruction in the WS

I dont want to have conflicts with the data and I realy need to take care
of this

my question:

Should I include the SQL into a transaction, is it needed?

Ken

[Christoph Schittko [MVP]]

Ken,

Transactions are needed only if you want to coordinate more than one
operations, i.e. if you need all INSERTs, UPDATEs or DELETEs grouped
into a transaction to succeed or fail as a whole.

If you only ever have one database operation -- the UPDATE that you
mention -- then you don't need a transaction. In fact, you shouldn't
start a transaction because it's causing unnecessary overhead.

HTH,
Christoph Schittko
MS MVP XML
http://weblogs.asp.net/cschittko

-----Original Message-----
From: Ken [mailto:Ke*@discussions.microsoft.com]
Posted At: Monday, November 15, 2004 2:29 PM
Posted To: microsoft.public.dotnet.framework.webservices
Conversation: transaction in WS
Subject: transaction in WS

hi

I have an Async WS updating my SQLserver DB
80 clients are connecting to the WS all day updating the DB
I have only ONE UPDATE instruction in the WS

I dont want to have conflicts with the data and I realy need to take care of this

my question:

Should I include the SQL into a transaction, is it needed?

Ken