I want to create a small table on a local system that contains new
records for a much larger table on a remote system. What I'm thinking
of doing is just to open both tables at the same time, and then append
the new records of the local table into the remote table.

This seems feasible, but clumsy. There will be some thousands (1 or 2)
of records transferred each time, so I need something that is fast. Any
recommendations for a more elegant solution?

TIA,
Glynn

--

Glynn


SQL and a transaction

Assuming the two tables have the same structure it should be a doddle eg

INSERT INTO bigtable (SELECT * FROM littletable)


Roy Lambert

Even if they are in to different databases?

One database is local and the other is remote, i dont whink this will do it. Am i wrong?

I would use remoteprocedures, saving the local table into a clientdataset, then saving the
dataset into a memorystrean, then send the memorystream as a blob parameter when
calling the remoteprocedure, then the remote procedure should load a clientdataset from
the stream
and then add all the clientdataset into the target table.

Luis David Cardenas wrote:

> Even if they are in to different databases?
>
> One database is local and the other is remote, i dont whink this will
> do it. Am i wrong?
>
> I would use remoteprocedures, saving the local table into a
> clientdataset, then saving the dataset into a memorystrean, then send
> the memorystream as a blob parameter when calling the
> remoteprocedure, then the remote procedure should load a
> clientdataset from the stream and then add all the clientdataset into
> the target table.

This is essentially what happens now, except that the transport being
used is an Indy TcpIPServer.

Thanks for the tip. I've never used remote procedures with DBISAM, but
they seem like an elegant solution to this problem.

Regards,
Glynn

--

Roy Lambert wrote:

> Glynn
>
>
> SQL and a transaction
>
> Assuming the two tables have the same structure it should be a doddle
> eg
>
> INSERT INTO bigtable (SELECT * FROM littletable)
>
>
> Roy Lambert

Thanks for the thought, but I think this is restricted to tables from
the same database.

Regards,
Glynn
--

RemoteProcedures are easy to implement, the only catch is that you need to code them
in the server, so you need a custom compiled version of the dbisam server, so, you need the
source code of the server. other than that is this forum you can find some working samples.


"Glynn Owen" <glynnMowenREMOVE@hotmail.comDELETE> wrote:

Luis David Cardenas wrote:

> Even if they are in to different databases?
>
> One database is local and the other is remote, i dont whink this will
> do it. Am i wrong?
>
> I would use remoteprocedures, saving the local table into a
> clientdataset, then saving the dataset into a memorystrean, then send
> the memorystream as a blob parameter when calling the
> remoteprocedure, then the remote procedure should load a
> clientdataset from the stream and then add all the clientdataset into
> the target table.

This is essentially what happens now, except that the transport being
used is an Indy TcpIPServer.

Thanks for the tip. I've never used remote procedures with DBISAM, but
they seem like an elegant solution to this problem.

Regards,
Glynn

--

Glynn Owen wrote:

> Roy Lambert wrote:
>
> > Glynn
> >
> >
> > SQL and a transaction
> >
> > Assuming the two tables have the same structure it should be a
> > doddle eg
> >
> > INSERT INTO bigtable (SELECT * FROM littletable)
> >
> >
> > Roy Lambert
>
> Thanks for the thought, but I think this is restricted to tables from
> the same database.
>
> Regards,
> Glynn

If that's true (is it?), then making the "littletable" a memory table
should solve problem.  No mssing around with remote procedures and
source changes to the server + works in C/S and file server modes.
Much more elegant.

--
Jeff Cook
Aspect Systems Ltd
www.aspect.co.nz
+
Joan and Jeff Cook
The Cooks Oasis
www.cookislandsoasis.com

David Cardenas wrote:

> RemoteProcedures are easy to implement, the only catch is that you
> need to code them in the server, so you need a custom compiled
> version of the dbisam server, so, you need the source code of the
> server. other than that is this forum you can find some working
> samples.
>
>
> "Glynn Owen" <glynnMowenREMOVE@hotmail.comDELETE> wrote:
>
> Luis David Cardenas wrote:
>
> > Even if they are in to different databases?
> >
> > One database is local and the other is remote, i dont whink this
> > will do it. Am i wrong?
> >
> > I would use remoteprocedures, saving the local table into a
> > clientdataset, then saving the dataset into a memorystrean, then
> > send the memorystream as a blob parameter when calling the
> > remoteprocedure, then the remote procedure should load a
> > clientdataset from the stream and then add all the clientdataset
> > into the target table.
>
> This is essentially what happens now, except that the transport being
> used is an Indy TcpIPServer.
>
> Thanks for the tip. I've never used remote procedures with DBISAM, but
> they seem like an elegant solution to this problem.
>
> Regards,
> Glynn

Can't I set up a DBISAMEngine component as my server, locate it on the
remote machine, and then address it from other sites? Is that what you
mean by "Access to the Server", or is there more to it than that?

Regards,
Glynn

--

Jeff Cook wrote:

> Glynn Owen wrote:
>
> > Roy Lambert wrote:
> >
> > > Glynn
> > >
> > >
> > > SQL and a transaction
> > >
> > > Assuming the two tables have the same structure it should be a
> > > doddle eg
> > >
> > > INSERT INTO bigtable (SELECT * FROM littletable)
> > >
> > >
> > > Roy Lambert
> >
> > Thanks for the thought, but I think this is restricted to tables
> > from the same database.
> >
> > Regards,
> > Glynn
>
> If that's true (is it?), then making the "littletable" a memory table
> should solve problem.  No mssing around with remote procedures and
> source changes to the server + works in C/S and file server modes.
> Much more elegant.

I can't say for sure, but it seems unlikely to me, since the
"littletable" doesn't exist within the context of the "bigtable". I
have seen SQL that allows for qualifiers to table tokens, but I don't
know if DBISAM can do that.

Also, what do you mean by a "memory table"? Are you referring to a
TClientDataset, or something else?

Thanks,
Glynn

--

>Can't I set up a DBISAMEngine component as my server, locate it on the
>remote machine, and then address it from other sites? Is that what you
>mean by "Access to the Server", or is there more to it than that?

Well, actually you can do it. I prefer messing with a custom dbsrvr