sql server programming: Several of these settings are 'connection' level settings. And, unless
specifically set otherwise, they will use the connection settings
established as the 'default' server connection settings. (See Server
Properties.) If you want to always use the same set of settings, you might
consider changing the server connection properties.

Usually, the same connection settings as used for stored procedures are
useful for views, functions, and triggers.

--
Arnie Rowland, Ph.D.
Westwood Consulting, Inc

Most good judgment comes from experience.
Most experience comes from bad judgment.
- Anonymous


[quoted text, click to view]

I've been running the following prior to creating stored procedures (on the
advice of folks in this newsgroup):

set ARITHABORT, CONCAT_NULL_YIELDS_NULL, QUOTED_IDENTIFIER, ANSI_NULLS,
ANSI_PADDING, ANSI_WARNINGS On
go
set NUMERIC_ROUNDABORT Off
go

In general, should the same be run before creating views, UDF's or triggers?
If not, should anything similar be run? (or something differnt for each obj
type?)

Thanks,

Keith

Thanks Arnie. I do make the same settings during the connection process from
the client application so I'm covered there. But it sounds like from what
you're saying that it would be a good idea to create views, triggers and
functions with the same settings that I'm using when creating stored
procedures.

Thanks for the info,

Keith