Hi Tim,

Is there a recommended maximum size for the server log file? I ask because recently a DBISAM server installation has been needing more than one
attempt to start the DBISAM server. An application event is logged stating that the the DBISAM server log file cannot be found or created. The server log
file did exist and was around 700MB. I renamed the existing log file while the server was stopped and allowed it to create a new log file on restarting the
server. Does the server have problems accessing the log file when it grows large?

In any case it doesn't seem possible to open a 700MB log file for inspection in SRVAdmin so it seems that the log file should be maintained at a smaller
size. So, is there any recommended maximum size?

Thanks, Tony.

Tony,

<< Is there a recommended maximum size for the server log file? >>

I wouldn't let it get much bigger than 128MB.   Anything larger than that
and, as you note, it will become somewhat unusable in terms of loading it or
examining it.

<< I ask because recently a DBISAM server installation has been needing more
than one attempt to start the DBISAM server. An application event is logged
stating that the the DBISAM server log file cannot be found or created. The
server log file did exist and was around 700MB. I renamed the existing log
file while the server was stopped and allowed it to create a new log file on
restarting the server. Does the server have problems accessing the log file
when it grows large? >>

It shouldn't, no.  I suspect that the problem was that the database server
had an issue renaming the file to a backup extension due to some issue
related to the size.

Do you still have the 700MB log file ?  If so, then can you tell me how big
it is zipped up ?  If it is small enough, I can take a look at it here and
see what the issue is.

--
Tim Young
Elevate Software
www.elevatesoft.com