Re: Help optimize Dataset copy code
- From: Helmut Woess <user22@xxxxxxxx>
- Date: Fri, 9 May 2008 17:31:27 +0200
Am Fri, 9 May 2008 17:06:47 +0100 schrieb notradamus:
....
I rolled my own function to copy records from one dataset to another, when....
the datasets are in different databases, in my case - SQL Server 2005
(source) and Access 2003 (destination).
I find it too slow, probably due to the repeated Post call.
Is there a way to /speed/ things up? Can I delay the writes or use
TClientDataset or something like that? Any inputs greatly appreciated.
It would be ways faster if you use a "linked server" or OPENROWSET. Look
into the SQL Server Manual how to do this. With your access database as
linked server you can send a TSQL-command like "insert into
access.destinationTable (field1, field2, ..) select fieldA, fieldB, ...
from sqlserver.Sourcetable" to the SQL-Server. And the SQL-Server would
copy the data directly into the access table without the help of your
application. You app has only to send the command :-)
bye,
Helmut
.
- Prev by Date: Re: Wireless ADOConnection
- Next by Date: Re: Help optimize Dataset copy code
- Previous by thread: Wireless ADOConnection
- Next by thread: Re: Help optimize Dataset copy code
- Index(es):
Relevant Pages
|
