|
dev
newsgroups
|
|||||||||||||||||||||||
|
|||||||||||||||||||||||
ANSI StandardsWe 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? Loren Z (anonym***@discussions.microsoft.com) writes:
> We are in the process of migrating our MS SQL Server 2000 databases to MS The only I know of is the SET FIPS_FLAGGER command. I have not used it> 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? myself. See Books Online for details. -- Erland Sommarskog, SQL Server MVP, esq***@sommarskog.se 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 Unfortunately, the FIPS_FLAGGER setting is only useful when creating SQL
Objects -it operates at Parse-time. -- Show quoteArnie Rowland, Ph.D. Westwood Consulting, Inc Most good judgment comes from experience. Most experience comes from bad judgment. - Anonymous "Erland Sommarskog" <esq***@sommarskog.se> wrote in message news:Xns98297C35643Yazorman@127.0.0.1... > Loren Z (anonym***@discussions.microsoft.com) 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, esq***@sommarskog.se > > 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 But in checking for ANSI issues on an existing database, you
can script out the entire database and all object into one file. Then load that file into QA and at the beginning add the set fips option and then just parse the entire script. I've used it that way before to check for ANSI issues with existing databases. -Sue On Thu, 24 Aug 2006 20:18:28 -0700, "Arnie Rowland" <ar***@1568.com> wrote: Show quote >Unfortunately, the FIPS_FLAGGER setting is only useful when creating SQL >Objects -it operates at Parse-time. Good Idea Sue. Thanks.
-- Show quoteArnie Rowland, Ph.D. Westwood Consulting, Inc Most good judgment comes from experience. Most experience comes from bad judgment. - Anonymous "Sue Hoegemeier" <Sue_H@nomail.please> wrote in message news:4336f2pp381r58b1h086qkk9uedmr44917@4ax.com... > But in checking for ANSI issues on an existing database, you > can script out the entire database and all object into one > file. Then load that file into QA and at the beginning add > the set fips option and then just parse the entire script. > I've used it that way before to check for ANSI issues with > existing databases. > > -Sue > > On Thu, 24 Aug 2006 20:18:28 -0700, "Arnie Rowland" > <ar***@1568.com> wrote: > >>Unfortunately, the FIPS_FLAGGER setting is only useful when creating SQL >>Objects -it operates at Parse-time. > To the best of my knowledge, FIPS_FLAGGER is more of less useless. With 2000, there was a lot of
stuff introduced that FIPS_FLAGGER didn't catch. I don't recall details, but I recall that it seemed like MS didn't bother to up the FIPS_FLAGGER code for 2000. I haven't checked whether same goes for 2005. I prefer to use the SQL validator found at mimer. Not as easy to use, though. .... One thing, for instance, that FIPS_FLAGGER don't warn for is FOR XML. -- Show quoteTibor Karaszi, SQL Server MVP http://www.karaszi.com/sqlserver/default.asp http://www.solidqualitylearning.com/ "Arnie Rowland" <ar***@1568.com> wrote in message news:O62ha9ryGHA.4116@TK2MSFTNGP02.phx.gbl... > Good Idea Sue. Thanks. > > -- > Arnie Rowland, Ph.D. > Westwood Consulting, Inc > > Most good judgment comes from experience. > Most experience comes from bad judgment. > - Anonymous > > > "Sue Hoegemeier" <Sue_H@nomail.please> wrote in message > news:4336f2pp381r58b1h086qkk9uedmr44917@4ax.com... >> But in checking for ANSI issues on an existing database, you >> can script out the entire database and all object into one >> file. Then load that file into QA and at the beginning add >> the set fips option and then just parse the entire script. >> I've used it that way before to check for ANSI issues with >> existing databases. >> >> -Sue >> >> On Thu, 24 Aug 2006 20:18:28 -0700, "Arnie Rowland" >> <ar***@1568.com> wrote: >> >>>Unfortunately, the FIPS_FLAGGER setting is only useful when creating SQL >>>Objects -it operates at Parse-time. >> > >  |
|||||||||||||||||||||||
Other interesting topics