ExecuteNonQuery vs OR in Entity Framework

Sanjay Sharma

Friends,

What is precise way in EF to achieve below scenario?

I have SP - [UpdateUnitStatement] @BatchRunId varchar(10)- The execution of this statement takes some time.

So below code using EF, does not wait till SP execution completed and moves to next statement.

entity. UpdateUnitStatement (BatchRunId);

//Next Statement

Alternatively, I achived this using standard SQLCommand.ExecuteNonQuery

int result = SQLCommand.ExecuteNonQuery("Exec UpdateUnitStatement @BatchRunId = " + BatchRunIds, null);

3 Replies

Know the answer? Post it — somebody with the same question will find it here.

Vincent Maverick Durano8y ago
Accepted answer
If you are more concered about peformance, then go for ADO.NET implementation with ExecuteNonQuery. Otherwise, if you want to work with conceptual models/classes rather than deailing with hardcoded sql queries, then go for EF. Choice is yours.

Keep in mind that EF is built at the top of ADO.NET, so it can't be faster. But it makes development much faster, neat, and improves maintainability of your code.
Jignesh Kumar8y ago
Hi Sanjay,

We can call procedure like this as well.

context.Database.SqlQuery("exec UpdateUnitStatement @BatchRunId ", BatchRunIds).ToList()
Jenith Thakkar8y ago
Entity framework is the good way because it will save your few time also easy to maintain if any error occurs and reduce few line of code like sql command and sql data adapter