Re: accessing two database one with logging and without

ogj@tglobe3.tollpost.no ('yvind Gjerstad) wrote: :Nils.Myklebust@idg.no (Nils Myklebust) writes: : :> rcyrus@promarkone.com wrote: :> :> :We have databases on Version 5.03 and version 7.22 online. The 5.03 :> :online instances have NO logging ON (previous DBA!!!). The 7.22 instances :> :have Logging ON. :> : :> :DBACCESS and ISQL and the 4GL code does not allow the access of Non :> :logging and a logging database at the same time. :> : :> :Anybody out there with any workarounds? (we can't turn on logging for the :> :5.x instances!!) We would really appreciate any ideas!! :> : :> :robin cyrus :> :ProMark One :> :Scottsdale AZ :> :> The only thing you can do in 4GL is to use the database statement to :> connect to one database. Select something into local variable. Then :> database again to connect to the other and use the data there. :> Probably not fast. :> :> In dbaccess/ISQL you can only unload to file from one and load from :> file to the other. : :Are you limited to the tools you list? If not, there are probably several :solutions available. DBD::Informix (a perl interface to Informix) can do it. :Nils will probably tell you about a UDBC solution. You allready did :-) I didn't because it doesn't work with any of the tools mentioned. Normally I try to avoide C-based solution (or god forbid C++) that would be the basis of a UDBC solution because I don't want to suggest that anybody should use such languages for database work unless there is no way arround. In this case it may however be a good idea. You should be able to open both databases at the same time from one program and select/update/delete - whatever - to your harts desire in both databases from this one program. You can of course not do a single select with a join between tables in both databases. You can also not do an insert into ... select ... where the insert was in one database and the select in the other. This means all data would have to flow from one database via the program to the other database, or of course select or update in both databases separately. This may be a very good solution. We will soon have a similar problem as we will want to run OLTP applications on a logging database and OLAP and marketing applications on a non loging one. Such a program may be a good idea to enable simple and efficient loading of data from the OLTP system into the OLAP one without having to do unload/load. Nils.Myklebust@idg.no NM Data AS, P.O.Box 9090 Gronland, N-0133 Oslo, Norway My opinions are those of my company The Informix FAQ is at http://www.iiug.org