Re: sqlturbo processes don't go away
Posted in 1996
Topics: Stored Procedures & SPL, Connectivity: ESQL/C, 4GL & Embedded SQL
> "The database engine process is active for the duration of the > connection. You terminate the sqlexec or sqlturbo process when you > finish running your application or when you issue a CLOSE DATABASE > statement. Each request from a client receives its own database > engine process." --- Snip ---- > DATABASE TEST > MAIN > CLOSE DATABASE > WHILE TRUE > DISPLAY "HELLO WORLD" > SLEEP 1 ? END WHILE > END MAIN > Does anyone know what would cause this? Do I really have a problem or > am I missing something? > > Thanks in advance > Rob Scott Rob, A connection is made to the Informix database engine upon the execution of the first DATABASE statement, by forking a child sqlturbo process from the 4GL process. This connection remains until the end of the 4GL program; which is a fair method for achieving and maintaining the database connection, as it is a fairly expensive thing to do in terms of computer resource and time. An aside which may be of interest is that one has to be careful in the treatment of the sqlturbo process, as killing it could potentially bring the entire database engine down. If an orphaned sqlturbo process does occur (it happens from time to time) you need to follow the steps given in the Online manual to decide whether to leave it, kill it, or bring the engine down before the sqlturbo process does it on your behalf. Hope this is useful, Telik.