.net - How do I stop default SET statements? -
when run sql profiler , issue queries using ado.net, see these statements in sql profiler:
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
i never wrote of these statements in query. how stop these set statements? sql server create separate request set these set statements?
two questions:
would improve turn off of these set statements? if yes, how can it?
which optimum settings these set? know arithabort should on since gives performance boost in of scenarios.
these beingness set client driver, set on new connections create.
it not improve turn of these off. though these set when connection opened, doesn't mean can't override them executing set sql statement on connection, ones above.
i set arithabort on, set alternative 1 of ones used indexes on computed columns , indexed views. alter dateformat/language if not american, doesn't matter whole deal, , done @ login level. if don't want utilize read_committed isolation, alter this, though fine in cases, hence it's default. rest fine.
.net sql sql-server tsql ado.net
No comments:
Post a Comment