Re: Why use transactions in SE?

Bryan, You bring up many valid points for not using transaction logging. My company on the other hand has recently begun migrating to Informix. We figured that we would start with SE and in a department that doesn't have alot of user (get into the hang of Informix). We have about 20 users curerently using this system doing OLTP. All programs written in 4gl. If the system is connected to a network in which the transaction log can be copied to another machine transaction logging should be a must in case of a system failure. We copy our log about every 20 minutes. Also if the programs are written to check for locks, it really helps to keep 'old data' from overwritting the 'new data' but you already mentioned that. I would recommend the transaction log if there is a reliable way of implementing a recovery procedure. This is just my opinion. -- Joseph Cullipher |E-mail: joseph@cannonexpress.com PO Box 364 |opinions express are those of my own and Springdale, AR 72764 USA |don't necessarily reflect those of my company