If I was to start hosting Dbisam would it be
best to have the one server running the
clients databases or a server for each client?

My thoughts are for the one server with 8
clients.
I cant forsee any reason why the Dbisam
server would need a reboot, but I suppose
someone would find a reason...............

Any thoughts or ideas on what you would like
from a Dbisam hosting plan would be well
received.
Rita

> I cant forsee any reason why the Dbisam
> server would need a reboot, but I suppose
> someone would find a reason...............
Reboot IMO should not be a problem, however,
remote administration would require (for
security reasons) that each hosting account has
its own databases, users and connections.
You will need to write a sophisticated admin
program/web site to manage that database,
because using standard admin would be impossible
becaue of above security problems.

Also, If I to restructure a table, I have to make
sure that no one is connected to my database, so I'd
need to be able to disconnect all clients
connected to my database, but I should not
be able to disrupt work of clients connected
to other databases. The usual way out of it
would be to prohibit table/record locking and
only allow optimistic locks, so I never need to
disconnect anyone. Alas, I'm not sure that
this option exists.

Other then that, one instance should be sufficient,
as they are usually hosting MySQL with one instance
of server. What you really need is a good web
admin, similar to myPhpAdmin. And you should also
disable connection to dbisam from outside of localhost.


Michael

"Michael Baytalsky" <mike@contextsoft.com> wrote in message
news:DC780916-E702-422A-A18F-96A96D9FE7B6@news.elevatesoft.com...
>
>
>> I cant forsee any reason why the Dbisam
>> server would need a reboot, but I suppose
>> someone would find a reason...............
> Reboot IMO should not be a problem, however,
> remote administration would require (for
> security reasons) that each hosting account has
> its own databases, users and connections.
> You will need to write a sophisticated admin
> program/web site to manage that database,
> because using standard admin would be impossible
> becaue of above security problems.
>

I thought the remote admin would be a breeze
as each hosting account has its own admin
over its own database. For instance

/remotedbisamserver/baytalskyDB01/
/remotedbisamserver/baytalskyDB02/
/remotedbisamserver/lambertDB01/
/remotedbisamserver/lambertDB02/

the above would give you and Roy 2 databases
each on the same server, with admin rights only
to your own and not each others databases.

> Also, If I to restructure a table, I have to make
> sure that no one is connected to my database, so I'd
> need to be able to disconnect all clients
> connected to my database, but I should not
> be able to disrupt work of clients connected
> to other databases. The usual way out of it
> would be to prohibit table/record locking and
> only allow optimistic locks, so I never need to
> disconnect anyone. Alas, I'm not sure that
> this option exists.
>

There is noway out I suppose as the www is
a 24hr 7 day shop but I'am pretty sure one database
can be disconnected under Dbisam as is without
disrupting other databases.

> Other then that, one instance should be sufficient,
> as they are usually hosting MySQL with one instance
> of server. What you really need is a good web
> admin, similar to myPhpAdmin. And you should also
> disable connection to dbisam from outside of localhost.
>

Ok then Michael get writing

Rita