> I have a customer with have an DB that supports 20 clients.
> 15 of those clients connects through an ADSL line to a terminal
> server in the head office.
> Here they run our program which connects to a DB on another server.
>
> Since marts 2002 and until december 2002 it ran perfectly.
>
> Then our customer moved the head office location.
> When this happened the Internetline at the head office of course
> changed.
> They got a ZyXEL Router instead of a Cisco i.e.

I presume that you did not make ANY changes to the database
at the same time!

> Now the clients keep falling of every once in a while.
> And the system has dropped considerable.
>
> First I assummed, that I had created to many index' on to many tables.
> So laft week i drop a lot of index' on the DB.
> Now every table contains no more than 8 index'.
> Most of the tables only contains 4 index'
>
> Those 4 are always created as 2 asc and 2 desc (on two different
> fields).

I presume that this was what was working fine last year?

> We have been pinging the clients router at the new location, and
> every once in a while the respons time from the router is not
> available.

Either the router is faulty, or the capacity of the line is
simply unable to cope with all the users.

> I Think thats why the are being trown off.

Sounds familiar - I had it the other way round. FrameRelay
had not been set up properly by British Telecom so every now
and again packets were taking seconds rather than
milliseconds. I spent 6 months trying to fix my end, but
once we had got BT to admit it was their problem and correct
it everything started working fine. Now we are not using
enough bandwidth to register a 1% uasage each week, because
of all the extra stuff to fix other peoples problems.

> Now my theori goes on this:
>
> 1 clients is about to do an update, and therefor starts an
> transaction.
> The connection to the terminal server goes down.
> After a few seconds the session is terminated, by both server and
> client.
> And after another few seconds the firebird DB realizes that the
> connecton has been lost and rollbacks whatever transactions are
> active (Does anyone know how long time there will go) ?
>
> Until this happens, all other clients that wants to update / insert
> on the same tables must wait (they get a Deadload on no wait
> transaction).

Sounds about right.

> So I think that the poor quality of the internet line causes this.
> Is that likely to be the case ?
>
> Or Could it be anything else ?
> Still to many index (which I find very unlikly since we here in our
> own house havn't the same problems with the same software / DB).

And I presume that this was working fine with the previous
internet connection.

> Other things ?

First thing is to establish if it is simply a faulty router,
or that the comms supplier at the new location simply does
not have enough bandwidth to cope with all the users are are
supplying. I don't think you problem is in your software.

Perhaps you could use another site as a temporary server
just to prove the point?

--
Lester Caine
-----------------------------
L.S.Caine Electronic Services