. NET CLient SET Options

• curious_sqldba

  SSC-Dedicated

  Points: 36502

  More actions

  April 13, 2011 at 12:18 pm

  #248861

  Please dont delete this post, i have another post with similar but couldn't get what i am looking for so posted with more details. All i want to know is does SET options from a .NET client override SET options inside a stored proc? In my stored proc we are using "isoaltion level read uncommitted" but from the .net client i see the set option to be "isolation level read committed". I need to know which one takes in effect? I have read this "http://msdn.microsoft.com/en-us/library/ms190356%28v=SQL.90%29.aspx" but couldn't find what i am looking for. I am guessing SET options from a .NET client is over writing set option in our proc because i see this is causing a block even though it is just selecting data. Any suggestion would be highly appreciated. Thanks

• curious_sqldba

  SSC-Dedicated

  Points: 36502

  More actions

  April 14, 2011 at 12:28 pm

  #1311787

  ANy help?

• mister.magoo

  SSC-Forever

  Points: 47174

  More actions

  April 14, 2011 at 12:46 pm

  #1311802

  I don't know the answer, but suggest capturing the query plan using sql profiler, then checking the properties of the SELECT object - it shows the SET options in force.

  Check this wonderful blog post for help with that : http://sqlinthewild.co.za/index.php/2011/01/04/capturing-the-execution-plan/

  MM
  

  ---

  
  select geometry::STGeomFromWKB(0x0106000000020000000103000000010000000B0000001000000000000840000000000000003DD8CCCCCCCCCC0840000000000000003DD8CCCCCCCCCC08408014AE47E17AFC3F040000000000104000CDCCCCCCCCEC3F9C999999999913408014AE47E17AFC3F9C99999999991340000000000000003D0000000000001440000000000000003D000000000000144000000000000000400400000000001040000000000000F03F100000000000084000000000000000401000000000000840000000000000003D0103000000010000000B000000000000000000143D000000000000003D009E99999999B93F000000000000003D009E99999999B93F8014AE47E17AFC3F400000000000F03F00CDCCCCCCCCEC3FA06666666666FE3F8014AE47E17AFC3FA06666666666FE3F000000000000003D1800000000000040000000000000003D18000000000000400000000000000040400000000000F03F000000000000F03F000000000000143D0000000000000040000000000000143D000000000000003D, 0);

• Forum Etiquette: How to post Reporting Services problems
[/url]
• Forum Etiquette: How to post data/code on a forum to get the best help - by Jeff Moden
[/url]
• How to Post Performance Problems - by Gail Shaw
[/url]