My server C:\Documents and Settings\All Users\Datos de
programa\Elevate Software\ElevateDB Server\edbsrvr.ini looks this:

[Layout]
Window State=0
Window Top=220
Window Left=241
Window Height=585
Window Width=798

That means all default values: I guess events are logged, and log file
is maintained between server start/stop.

But: "select * from configuration.logevents" always returns an empty
result set.

I'm looking for log in the wrong place?




Tiago Ameller
tiago put_an-a-_in_a_circle sistemasc.net
Sistema, S.C.

Tiago,

<< That means all default values: I guess events are logged, and log file is
maintained between server start/stop. >>

You can check by examining the settings for the current session in the Edit
Session task link.  The log settings are under the Local Configuration tab
for the session.

<< But: "select * from configuration.logevents" always returns an empty
result set. >>

In that case you don't have the logging settings turned on for the session
in the EDB Manager (or elsewhere, if you're using the same configuration
path in an application, etc.).

--
Tim Young
Elevate Software
www.elevatesoft.com

Tim,

>You can check by examining the settings for the current session in the Edit
>Session task link.  The log settings are under the Local Configuration tab
>for the session.

I'm using only remote sessions type. How enable log in a remote
server?

I don't understant why log file is related to sessions. Is there a
server general log (as was in DBISAM server)?

For legal issues, I need a historical log of connections (ok and
failure) in every database.


Tiago Ameller
tiago put_an-a-_in_a_circle sistemasc.net
Sistema, S.C.

Tiago,

<< I'm using only remote sessions type. How enable log in a remote server?
>>

At the server under Edit Server Options/Configuration.

<< I don't understant why log file is related to sessions. Is there a server
general log (as was in DBISAM server)?  >>

It's only related to sessions in the EDB Manager, and only for local
sessions.

<< For legal issues, I need a historical log of connections (ok and failure)
in every database. >>

And that is what you get with the log in EDB.  However, the log is also a
cyclical log that re-uses the same log space after the max log file size
setting has been reached.  This saves you from having to clean out the log
manually every now and then when it gets particularly large.

--
Tim Young
Elevate Software
www.elevatesoft.com

Tim,

>At the server under Edit Server Options/Configuration.
! it's heavily hidden I'm using server with no user interface.
Going to stop it, manually start, and configure.

>It's only related to sessions in the EDB Manager, and only for local
>sessions.
Ok, I understant: you mean  file/server deployments. It's good to have
also a log in such scenario.

>And that is what you get with the log in EDB.  However, the log is also a
>cyclical log that re-uses the same log space after the max log file size
>setting has been reached.  This saves you from having to clean out the log
>manually every now and then when it gets particularly large.
I realized it. I'll create a mechanism for periodically store log with
a time frame.

Thanks, Tim. You have made a lot of work in EDB. I guess it is beyond
DBISAM lines of code

Tiago Ameller
tiago put_an-a-_in_a_circle sistemasc.net
Sistema, S.C.

Tiago,

<< Thanks, Tim. You have made a lot of work in EDB. I guess it is beyond
DBISAM lines of code >>

Yeah, it's a lot larger in scope than DBISAM.

--
Tim Young
Elevate Software
www.elevatesoft.com