Path: utzoo!attcan!uunet!lll-winken!lll-lcc!pyramid!infmx!aland
From: aland@infmx.UUCP (Dr. Scump)
Newsgroups: comp.databases
Subject: Re: File data imported into SQL db's
Summary: some corrections...
Message-ID: <298@infmx.UUCP>
Date: 19 Jul 88 03:33:09 GMT
References: <236@tijc02.UUCP> <11410001@hpsmtc1.HP.COM> <3102@tekgen.BV.TEK.COM> <8190@ncoast.UUCP>
Organization: Informix Software Inc., Menlo Park, CA.
Lines: 53

In article <8190@ncoast.UUCP>, allbery@ncoast.UUCP (Brandon S. Allbery) writes:
> 
>      (discussion about various vendors' ASCII file load utilities)
> 
> Informix-SQL also has LOAD and UNLOAD statements, which derive from Informix
> 3.x's LOAD ASCII / UNLOAD ASCII, plus an external "dbload" program.  But
> these require that you turn on transaction logging even when it's acceptable
> to do a "tar" backup of the database every day.  I consider this a

  This is not true.  Not at present, anyway, and I am unable to find
  any past bug which mandated logging.  (Note also that INFORMIX 3.X 
  had no transaction logging capability anyway, though it did have 
  audit trails).  There is the situation that if you *are* using 
  transaction logging and you are running on a non-system-call-locking
  port, you need to lock the table first or you can run out of 
  record-level locks (normally a good idea anyway).

>                                                  I consider this a
> misfeature, especially since there's no way to turn it off once it's on (I
> once accomplished it by manually updating informix.systables, but it was a
> nightmare).  

  I agree that there should be an straightforward RDSQL statement to 
  turn off logging, but I wouldn't consider the current "workaround"
  a "nightmare" to use.  All you need to do is run this statement:
  (Kids, don't try this at home unless you *really* want to stop
  logging...)  

        DELETE FROM SYSTABLES WHERE TABNAME = "syslog"
  
  If that's your worst nightmare, you must sleep really well :-]

  (Don't get me wrong; I agree fully with your assertion that it
  should be its own command, and this has been submitted as a feature
  request)

  For Turbo, the procedure is different.  To change logging modes
  for one or more databases: 

  1> run an archive from the TBMONITOR menu; (don't exit TBMONITOR
  yet!)  2> go to the Databases option of the Logical Logs menu, move
  the highlight to each desired database, hit CTRL-B, and change status
  as desired (Unbuffered logging / Buffered logging / No logging).

> Brandon S. Allbery			  | "Given its constituency, the only

Hope this helps.  If you were misinformed by someone here regarding the
need for transaction logging, I'm sorry...

-- 
 Alan S. Denney  |  Informix Software, Inc.  |  {pyramid|uunet}!infmx!aland
 Disclaimer: These opinions are mine alone.  If I am caught or killed,
             the secretary will disavow any knowledge of my actions.
 Santos' 4th Law: "Anything worth fighting for is worth fighting *dirty* for"