I setup a DbContext
where I have this code:
base.Database.ExecuteSqlCommand("SET TRANSACTION ISOLATION LEVEL READ UNCOMMITTED;");
in the context constructor. I execute a stored procedure like this:
return base.Database.ExecuteSqlCommand("EXEC mystoredprocedure");
but I'm getting a deadlock because this executes in a read committed connection.
I'm asking is there any reason why the stored procedure would run in a read committed fashion when it is part of the same context that has the read uncommitted connection.