executenonquery vs transaction sqlclient/sql server

[Chance Hopkins]

When using the sqlclient dotnet class and sql server.

is it faster when doing a single (not multiple) insert to:

1- just do a simple connection and command object, then execute a nonquery

2-use a transaction, connection and command object to execute a nonquery and
then commit the transaction

Thanks

 

[Sahil Malik]

AFAIK, Adding a transaction to your T-Sql will introduce extra overhead -
if you don't need it, don't use it. The same rule applies to ADO.NET
SqlCommand object.

- Sahil Malik
http://dotnetjunkies.com/weblog/sahilmalik
http://blogs.apress.com/authors.php?author=Sahil Malik

 

[Scott Allen]

It is always faster to not use a transaction, but the answer really
depends on what your command does. If the query contains a single
UPDATE, INSERT, or DELETE statement, then the command is already
atomic and will have an implicit transaction.

If there are multiple statements inside, and you need them to behave
atomically (if one fails - everything inside the transaction fails and
changes rollback), then you'll need a transaction no matter what the
performance hit.

 

[Sahil Malik]

DC in Da Houze MAAAN !!

- Sahil Malik
http://dotnetjunkies.com/weblog/sahilmalik

 

[Scott Allen]

Woot! Woot!

 

[Patrick Olurotimi Ige]

Sahil and Scott

What is DC in Da Houze MAAAN !! and Woot Woot!
Code huh..Let it flow!
Patrick

 

[Sahil Malik]

When 2 geeks get together - you can't help but go crazy .. sorry for the
diversion man

- Sahil Malik
http://dotnetjunkies.com/weblog/sahilmalik

 

[Patrick Olurotimi Ige]

hehaha Sahil...
Hope i could be the third GEEK!
Patrick

 

[Chance Hopkins]

thanks everybody for the clarification

Have a good one

 

[Sahil Malik]

Ok you're the honorary geek.

- Sahil Malik
http://dotnetjunkies.com/weblog/sahilmalik