When to use ANSI-compliant database

Posted in 2008

VICKY H — Thu, 04 Sep 2008 15:58:44 — source: IIUG Forums & Mailing Lists

Hello Guru's Sorry for a very basic question.. I understand the Buffered and Unbuffered databases but never woked with ANSI compliant database. I am reading about it in the friendly manuals and its comparision with the Non-ANSI compliant databases. I would appreciate if some one pls help me with an example of setup/scenario/environment which would demand the ANSI compliant database OR when should we use a ANSI-compliant database. ( i understand that ANSI-compliant databases run with unbuffered transaction logging and that gurantees the last commited data). Regards Vicky

↪ replying to VICKY H

Richard Kofler — Thu, 04 Sep 2008 17:11:58 — source: IIUG Forums & Mailing Lists

VICKY H schrieb: > Hello Guru's > > Sorry for a very basic question.. > > I understand the Buffered and Unbuffered databases but never woked with ANSI > compliant database. > > I am reading about it in the friendly manuals and its comparision with the > Non-ANSI compliant databases. > > I would appreciate if some one pls help me with an example of > setup/scenario/environment which would demand the ANSI compliant database OR > when should we use a ANSI-compliant database. > ( i understand that ANSI-compliant databases run with unbuffered transaction > logging and that gurantees the last commited data). > > Regards > Vicky > > > ******************************************************************************* > Forum Note: Use "Reply" to post a response in the discussion forum. > > If you want to use XA (aka distributed transactions) IB LOG MODE ANSI is a requirement. At least it was so in version 9.40. If you can avoid it, then avoid ANSI mode. There are easier ways to 'be always in a transction', without issuing the BEGIN WORK statement at start. ANSI mode does consume considerable more logical log space, as there is no log compression. Always all attributes of the full row have to go into the llog, even if you only update 1 of the attributes. Maybe Jonathan can comment a bit more, as he had the chance to collect some deeper know how during an assignment ;). In the days of version 9.21 % 9.40 we had a lot of minor glitches like cursor close eating up memory and the like. Starting with CSDK 2.80 some were fixed, some are not (to my knowledge). If you have to go the ANSI way and if you see the unexpected, check back here & I will try to help, if I can. Good luck! dic_k -- Richard Kofler SOLID STATE EDV Dienstleistungen GmbH Vienna/Austria/Europe

↪ replying to Richard Kofler

Fernando Nunes — Thu, 04 Sep 2008 17:38:00 — source: IIUG Forums & Mailing Lists

You can use X/Open without ANSI databases AFAIK... The only reason I can think of to go for ANSI databases is if you have an application that requires it... There are several practical differences as Richard already mentioned: - You're always on transaction - The schemas are enforced (you need to reference the table schema/owner) meaning you can have tables with the same name if they belong to different schemas - The default isolation level becomes REPEATABLE READ (ouch) Regards. On Thu, Sep 4, 2008 at 6:11 PM, Richard Kofler <richard.kofler@chello.at>wrote: > VICKY H schrieb: > > Hello Guru's > > > > Sorry for a very basic question.. > > > > I understand the Buffered and Unbuffered databases but never woked with > ANSI > > compliant database. > > > > I am reading about it in the friendly manuals and its comparision with > the > > Non-ANSI compliant databases. > > > > I would appreciate if some one pls help me with an example of > > setup/scenario/environment which would demand the ANSI compliant database > OR > > when should we use a ANSI-compliant database. > > ( i understand that ANSI-compliant databases run with unbuffered > transaction > > logging and that gurantees the last commited data). > > > > Regards > > Vicky > > > > > > > > ******************************************************************************* > > Forum Note: Use "Reply" to post a response in the discussion forum. > > > > > > If you want to use XA (aka distributed transactions) IB LOG MODE ANSI > is a requirement. At least it was so in version 9.40. > If you can avoid it, then avoid ANSI mode. > There are easier ways to 'be always in a transction', without issuing the > BEGIN WORK statement at start. > ANSI mode does consume considerable more logical log space, as there is no > log compression. Always all attributes of the full row have to go into the > llog, > even if you only update 1 of the attributes. > Maybe Jonathan can comment a bit more, as he had the chance to collect some > deeper know how during an assignment ;). > In the days of version 9.21 % 9.40 we had a lot of minor glitches like > cursor > close > eating up memory and the like. Starting with CSDK 2.80 some were fixed, > some > are not > (to my knowledge). > > If you have to go the ANSI way and if you see the unexpected, check back > here > & I will try to help, if I can. > > Good luck! > dic_k > > -- > Richard Kofler > SOLID STATE EDV > Dienstleistungen GmbH > Vienna/Austria/Europe > > > > ******************************************************************************* > Forum Note: Use "Reply" to post a response in the discussion forum. > > -- -- Fernando Nunes Portugal http://informix-technology.blogspot.com My email works... but I don't check it frequently...