Re: ANSI Standards
- From: "Arnie Rowland" <arnie@xxxxxxxx>
- Date: Thu, 24 Aug 2006 20:18:28 -0700
Unfortunately, the FIPS_FLAGGER setting is only useful when creating SQL
Objects -it operates at Parse-time.
--
Arnie Rowland, Ph.D.
Westwood Consulting, Inc
Most good judgment comes from experience.
Most experience comes from bad judgment.
- Anonymous
"Erland Sommarskog" <esquel@xxxxxxxxxxxxx> wrote in message
news:Xns98297C35643Yazorman@xxxxxxxxxxxx
Loren Z (anonymous@xxxxxxxxxxxxxxxxxxxxxxxxx) writes:
We are in the process of migrating our MS SQL Server 2000 databases to MS
SQL Server 2005.
We have using the MS Upgrade Advisor to flag problems in our databases
so they can be fixed. Does there exist a tool from which we can get a
report on which databases contain components (tables, columns, stored
procedures) that do not meet ANSI standards?
The only I know of is the SET FIPS_FLAGGER command. I have not used it
myself. See Books Online for details.
--
Erland Sommarskog, SQL Server MVP, esquel@xxxxxxxxxxxxx
Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/prodtechnol/sql/2005/downloads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodinfo/previousversions/books.mspx
.
- Follow-Ups:
- Re: ANSI Standards
- From: Sue Hoegemeier
- Re: ANSI Standards
- References:
- ANSI Standards
- From: Loren Z
- Re: ANSI Standards
- From: Erland Sommarskog
- ANSI Standards
- Prev by Date: ANN: Context Database Designer & Extensions v.2.10 is now available!
- Next by Date: Management Studio & Views containing unions
- Previous by thread: Re: ANSI Standards
- Next by thread: Re: ANSI Standards
- Index(es):
Relevant Pages
|
Loading