Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
malakai
Starting Member
8 Posts |
 Posted - 2004-06-12 : 15:18:52
|
| Are their any down sides to applying:SET ARITHABORT ONSET CONCAT_NULL_YIELDS_NULL ONSET QUOTED_IDENTIFIER ONSET ANSI_NULLS ONSET ANSI_PADDING ONSET ANSI_WARNINGS ONSET NUMERIC_ROUNDABORT OFFat a Server level? (default connection options)?What about at my data access layer, prefixing every SQL statement with the settings? It seems Indexed Views are severely hindered w/o these, and that these settings only help SQL in it's query analysis. So what's the down side?-frank o'connor |
|
|
derrickleggett
Pointy Haired Yak DBA
4184 Posts |
Posted - 2004-06-12 : 23:21:30
|
| Most of these should be enforced in your standards for releasing stored procedures and code releases for the very fact that you cannot use indexed views and computed columns without these set correctly.Depending how your environment is set up, you might also want to limit the use of counts with the SET NOCOUNT ON option also.MeanOldDBAderrickleggett@hotmail.comWhen life gives you a lemon, fire the DBA. |
 |
|
|
malakai
Starting Member
8 Posts |
Posted - 2004-06-12 : 23:40:52
|
| Sounds good. I've always seen Enterprise manager script pre-pend this, I guess SQL Server doesn't use it as a default Connection option for backwards compatability. I'm going to start testing these settings on by default and make sure we're not acidentally dependent on one not being set. |
|
|
|
|
|
|
Session settings, Global change or not?