Re: Export fast, my code slow =[

Yes, linked tables make it very easy. But, as Rich pointed out, there might
be some performance hits. But I think if your query is pretty
straightforward, you should get pretty good performance.

Neil

<eselk@xxxxxxxxxxxx> wrote in message
news:1183148617.357481.79810@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
On Jun 29, 11:36 am, "Neil" <nos...@xxxxxxxxxx> wrote:
Yes, that is correct: your code is taking much longer because it's
appending
the records one at a time, instead of in batch. Use Insert Into to insert
your tables in batch into the target table. In its simplest incarnation,
it
would be:

INSERT INTO Table2 ( FieldSomething )
SELECT Table1.FieldWhatever
FROM Table1

You can also add a Where statement, or append multiple fields, or
whatever
you need.

Neil

Thanks. I was thinking that would only work if both tables where on
the server, and my problem is getting the data up to the server in the
first place... but I guess that might also work using linked tables.

Also, thanks to all others who replied. Now I have lots of options to
explore! =]



.

Relevant Pages

  • Re: SMTP Virtual Server Quit problem
    ... PIPELINING verb fixed that....on our external facing mail server (which is ... noticed any performance hits, but you can always filp it during a time you ... is an older version of the IpSwitch IMail smtp engine). ... > As for Helo rather than Ehlo, doesn't the server revert back to helo if ...
    (microsoft.public.exchange.connectivity)
  • Re: Network printer
    ... The method Lanwench gave you. ... :> There is no reason, IMHO, to add performance hits to your server to ... separate print server should be used anyway. ...
    (microsoft.public.windows.server.general)