With MSSQL there is something called an instance (almost like a folder) and with each installation of MSSQL there can be up to 16 instances...does Elevate have a corresponding architecture?

I am wanting to use my application but essentially have 2 databases with the same structure and same name, one for students and one for employees.   Is it possible to have 2 databases with the same name on the server and the ElevateDB Server/CAS handle it?  It would be too much of a chore to change the name of my database within my application.

jdm77


>With MSSQL there is something called an instance (almost like a folder) and with each installation of MSSQL there can be up to 16 instances...does Elevate have a corresponding architecture?
>
>I am wanting to use my application but essentially have 2 databases with the same structure and same name, one for students and one for employees. Is it possible to have 2 databases with the same name on the server and the ElevateDB Server/CAS handle it? It would be too much of a chore to change the name of my database within my application.

ElevateDB has the structure

Engine
Session
    database
    ...
    database
Session
    database
    ...
    database

What differentiates the databases is the information in the configuration file. Essentially unique name and path.

What you can't do is have two databases with the same name in the same session. That restriction means that you could connect to the employees version or the students but not both withing the same session.

Hope that answers the question.

Roy Lambert

jdm77 wrote:

With MSSQL there is something called an instance (almost like a folder) and with each installation of MSSQL there can be up to 16 instances...does Elevate have a corresponding architecture?

I am wanting to use my application but essentially have 2 databases with the same structure and same name, one for students and one for employees.   Is it possible to have 2 databases with the same name on the server and the ElevateDB Server/CAS handle it?  It would be too much of a chore to change the name of my database within my application.

jdm77,

In addition to what Roy wrote, I would like to add that it is possible indeed (even thought I've not tried it myself…) to have multiple EDB Server instances running in the same machine using a different TCP port, pretty much like MSSQL does it.

Given you scenario, you'll need to setup both EDB Servers (students server and employee server) on different folders with its own edbsrv.ini and change the connection parameters on you application to reflect the new TCP port configuration of each server.

It is important to note that using one single server instance to server both databases is the ideal way to go, (performance, maintenance and integration wise), and if you'll have to invest some effort changing you code to accommodate the TCP port parameter, it would be worthwhile to consider extending such effort to make the database name configurable too.

Regards,
Mario