Session1: Local server
Session2: Remote server

Not possible to INSERT INTO session1.db.table1 SELECT * FROM session2.db.table1?

Jeff,

<< Not possible to INSERT INTO session1.db.table1 SELECT * FROM
session2.db.table1? >>

No, you cannot mix and match local and remote tables in queries.  That would
involve possibly transferring an entire table over the wire, and that's a
recipe for disaster in terms of performance.

--
Tim Young
Elevate Software
www.elevatesoft.com

I know you're being quite serious as incredulous as I am at the response. It is no more a recipe for disaster than SELECT * from
remote.db.customer in the first place. Consider this a feature request then.

Jeff


SELECT * from remote.db.customer will simply open the table (possibly unless I think you force a non-sensitive result set, but I'm not sure about that) and the way ElevateDB then works is only enough data is transferred to satisfy the needs of the visual component / operation you're carrying out needs.

INSERT INTO session1.db.table1 SELECT * FROM session2.db.table1 would require the whole of session2.db.table1 to be transferred across the network.

From DBISAM there were a number of threads about streaming a whole table across the network (often into memory tables) so that might be the way you want to go.

Is this just a generic "I think I'd like to do this" or is there a specific need. If the latter can you share it?

Roy Lambert [Team Elevate]

Jeff,

<< I know you're being quite serious as incredulous as I am at the response.
It is no more a recipe for disaster than SELECT * from remote.db.customer in
the first place. Consider this a feature request then. >>

Why are you incredulous at my response ?  If something is a performance
non-starter, then why would we waste time on implementing it ?  If you want
to get server tables down the client-side for querying purposes, etc.  then
you can do so.  But, in such a case you can control when and where this is
done so that it is optimized for your purposes.  EDB would have to pull down
the table every time a row had changed, at the very least.

--
Tim Young
Elevate Software
www.elevatesoft.com