Are there any benefits to be gained (or lost) by running multiple EDBsrvr instances on one box? An instance (that word again) of my application has two (or more) databases. I'm looking for the cleanest way of neatly organising sets of databases so application instances (typically production system and test/training system) are separated.

Charles,

> Are there any benefits to be gained (or lost) by running multiple EDBsrvr instances on one box? An instance (that word again) of my application has two (or more) databases. I'm looking for the cleanest way of neatly organising sets of databases so application instances (typically production system and test/training system) are separated.
>

That will work fine.
You just have to use different ports and different names. Each server
will produce his own ini-file with all settings.

If you install the instances of EDBServer as a service, pay attention to
change the description as well:

From a former thread:

<<
Make sure that you set up an .ini file for both servers, and that the
Server Description in the .ini file is different. Windows wants the
display names of the services to be different, in addition to the core
executable names.
>>

Uli

I've done this a few times.  As mentioned, you'll need to make sure each server has a different port number and make sure the name is different when using as a service.

Lance


Charles Bainbridge wrote:

Are there any benefits to be gained (or lost) by running multiple EDBsrvr instances on one box? An instance (that word again) of my application has two (or more) databases. I'm looking for the cleanest way of neatly organising sets of databases so application instances (typically production system and test/training system) are separated.

Charles,

<< Are there any benefits to be gained (or lost) by running multiple EDBsrvr
instances on one box? An instance (that word again) of my application has
two (or more) databases. I'm looking for the cleanest way of neatly
organising sets of databases so application instances (typically production
system and test/training system) are separated.  >>

Just a quick note - if you do consider doing so, you should wait for EDB
2.09.  It has a new "named server" design that allows you to deploy multiple
servers (even as services) on the same machine in a much easier manner than
you currently can.  Currently, you have to change the .exe name, which is a
PIA.

If you have any other questions, please let me know.

Tim Young
Elevate Software
www.elevatesoft.com