Database setting

. The BPA recommend that the model database setting for the items below be set to on. I can accomplish this task through the query analyzer and run the set command. (Set ANSI_NULLS on). The response is positive but when I re-run the report the setting are back off.

Why?

QUOTED_IDENTIFIER
ANSI_NULLS
ANSI_WARNINGS
ANSI_PADDING
ANSI_NULL_DFLT_ON
CONCAT_NULL_YIELDS_NULLDon't the setting only last for the scope of the session?

That's why they have to be coded inside the sporcs?

I'll have to look a more defenitive answer...but I'll just be fgetting from BOL|||Garry,

Those settings are only taking effect for that single session i.e. within Query Analyzer.

To make any permanent changes to the model database, you need to right click it in Query Analyzer and check the options under properties. You should save a copy of the database first in case you should find that you need to return to the default settings.

Please note carefully this article in case you need to reattach your model database:

http://support.microsoft.com/?id=224071

We would advise leaving the model database at default settings.

Use the following from Query Analyzer to check the settings:
Sp_helpdb
And also check for databaseproperty in Books Online
Syntax
DATABASEPROPERTY( database , property )

USE master

SELECT DATABASEPROPERTY('model', 'IsANSINullDEFAULT')|||Well its up to you, but most people would leave the model database alone. It depends on your particular needs more than anything else. Remember the model database is only a template used to create new databases, so if you are bringing databases to this machine from another server, then the model database settings will have no effect.

Any conflict here is due to ANSI compatibility levels. SQL Server does not always default to the ANSI compatible levels.

Please review this article for a note on the various database settings and their effects:-

http://msdn.microsoft.com/library/default.asp?url=/library/en-us/createdb/cm_8_des_03_6ohf.asp

These two commands give you information on your current connection details, and on the database settings that may be configured respectively:-

sp_dboption

dbcc useroptions|||why did you post the question if you already had the answer?|||Perhaps it was a rhetorical question?

Read the top of his posts. He was just copying information from MicroCoughed.sql

Database Releases

I'm looking for documentation templates to specify releases or promotions of
items from Dev to QA to Prod. Has anyone got any recommendations or
references to some that already exist?
Thanks - Craig.Hi
If you have a bug tracking system and version control this can be done
process that combines labelling fixes and extracting the appropriate version
from the repository. Exactly how depends on what systems you are using. There
may be some white papers on the web sites for these sort of products such as
Serena (formally Merant PVCS).
John
"Craig" wrote:
> I'm looking for documentation templates to specify releases or promotions of
> items from Dev to QA to Prod. Has anyone got any recommendations or
> references to some that already exist?
> Thanks - Craig.|||Thanks for the reply. I was hoping to locate a MS Word template that might
aid in this effort.
- Craig
"John Bell" wrote:
> Hi
> If you have a bug tracking system and version control this can be done
> process that combines labelling fixes and extracting the appropriate version
> from the repository. Exactly how depends on what systems you are using. There
> may be some white papers on the web sites for these sort of products such as
> Serena (formally Merant PVCS).
> John
>
> "Craig" wrote:
> > I'm looking for documentation templates to specify releases or promotions of
> > items from Dev to QA to Prod. Has anyone got any recommendations or
> > references to some that already exist?
> >
> > Thanks - Craig.|||Hi
Sorry I didn't read "template"!
If you are looking for a process then it will depend on the systems and
configurations that you are using, therefore I would not really expect it to
fit a generic template.
I would assume that you already have some form of process that you can then
reverse engineer and then formalise/improve?
John
"Craig" wrote:
> Thanks for the reply. I was hoping to locate a MS Word template that might
> aid in this effort.
> - Craig
>
> "John Bell" wrote:
> > Hi
> >
> > If you have a bug tracking system and version control this can be done
> > process that combines labelling fixes and extracting the appropriate version
> > from the repository. Exactly how depends on what systems you are using. There
> > may be some white papers on the web sites for these sort of products such as
> > Serena (formally Merant PVCS).
> >
> > John
> >
> >
> > "Craig" wrote:
> >
> > > I'm looking for documentation templates to specify releases or promotions of
> > > items from Dev to QA to Prod. Has anyone got any recommendations or
> > > references to some that already exist?
> > >
> > > Thanks - Craig.