How do you control the "SET" statements emitted by Linq to SQL

Question

Hi -

Is there any way to control the "SET" statements that Linq to SQL emits? I see these SET options coming from Linq to SQL in the SQL profiler and it turns out that "set arithabort off" is causing one of our procs to take 45 seconds as opposed to < 1 second.

-- network protocol: TCP/IP
set quoted_identifier on
set arithabort off
set numeric_roundabort off
set ansi_warnings on
set ansi_padding on
set ansi_nulls on
set concat_null_yields_null on
set cursor_close_on_commit off
set implicit_transactions off
set language us_english
set dateformat mdy
set datefirst 7
set transaction isolation level read committed

Thanks, Jon

Answer 1

Rather than using the default constructor or passing a connection string, create your own IDbConnection, set whatever options you need, then pass that to your DataContext's constructor.