*nod* the client is mapping to the server machine. the server machine
actually is the one doing all the work, i found this one out the hard way as
i said, i put a .gdb on a mapped drive, and it complained about no server
found until i actually installed interbase on the server machine. I did a
speed test comparison today too, with interbase and paradox of the same
application. to add 170 records to a 3rd level detail table (with
miscellaneous reads) to each of the following supports my findings. (paradox
server works ala access reading the files as if they were local).

ib local: 3mins 20sec.
ib server: 4mins 35sec.
pdx local: 7mins 20sec.
pdx server: 35 records in 10 minutes with lock file too large crash at 38
records.

-----Original Message-----
From: Adam Clarke [mailto:Adam.Clarke@...]
Sent: Wednesday, 9 August 2000 12:15 AM
To: IB-Architect@egroups.com
Subject: Re: [IB-Architect] Re: Is it _really_ necessary to expose the
location of the database file?


So the map S: is on the client not a server running Interbase? If so I see
what you mean and cool. If not my original concern stands.

Cheers
Adam

----- Original Message -----
From: "Bill King" <ungod@...>
To: <IB-Architect@egroups.com>
Sent: Wednesday, August 09, 2000 12:05 AM
Subject: RE: [IB-Architect] Re: Is it _really_ necessary to expose the
location of the database file?


> actually no, as it forwards database requests, not accesses to the server
> interbase (exactly like ibclient) would to the server machine. so the
server
> interbase serves the query's etc exactly like it would if you were to
> connect to the server and specify a path. so no chance of corruption, as
the
> server interbase is serving the data, and exactly the same amount of
> bandwidth, as once again, the server interbase is processing the requests
> for data etc.
>
> -----Original Message-----
> From: Adam Clarke [mailto:Adam.Clarke@...]
> Sent: Tuesday, 8 August 2000 11:55 PM
> To: IB-Architect@egroups.com
> Subject: Re: [IB-Architect] Re: Is it _really_ necessary to expose the
> location of the database file?
>
>
> Unfortunately this is not a very good idea in terms of network bandwidth
and
> (because they are related) performance. Now all file accesses from the
> engine are flying across the network. You've just converted a high
> performance client server database into MS Access.
>
> IK wouldn't be surprised if this increased the chance of corruption also
but
> that's just a gut feeling at this stage.
>
> Cheers
> Adam
>
> ----- Original Message -----
> From: "Bill King" <ungod@...>
> To: <IB-Architect@egroups.com>
>
> > you can get this functionality at the moment using windows networking.
> > interbase is kind enough to detect that the file is residing on another
> > machine, and redirects all requests for that database through to the
> correct
> > server. (i found this one out the hard way).
> > so if you map \\server\servershare to s: for example. then connecting to
> > s:\test.gdb will actually connect to the server's interbase server! path
> > hiding.....+full security if the share is sitting on an NT box.
>
>
>
>
>
> To unsubscribe from this group, send an email to:
> IB-Architect-unsubscribe@onelist.com
>
>
>
>
>
>
>
> To unsubscribe from this group, send an email to:
> IB-Architect-unsubscribe@onelist.com
>
>
>
>




To unsubscribe from this group, send an email to:
IB-Architect-unsubscribe@onelist.com