Re: ADO and SQL2K5 and Speed
- From: "Bill Todd" <no@xxxxxx>
- Date: 22 Dec 2007 19:50:16 -0700
Kendrick wrote:
I am iterating a TClientdataset and then checking a destination table
for a matching record using Tdataset.Locate with the values of a
unique index and then editing if true or appending if not. I am
comparing the process between Advantage Data Server via their
TAdsTable component and a MSSQL2K5 via ADO. 440 records of moderate
size takes less than one second for Advantage and 40 seconds for
MSSQL. Any hints for improvement? (my first ADO endeavor and first
MSSQL).
More details please.
Are you calling Locate on the TClientDataSet or some other dataset
component. If another component what component?
Which ADO components are you using to access SQL Server? If you are
using anything other than TADODataSet, TADOCommand and TADOConnection
you may need to change. In particular, do not use TADOTable.
How are you inserting the records in SQL Server? A TADOCommand with a
parameterized INSERT statment would be fastest.
Are you also using a TClientDataSet with Advantage?
These are just a few of the questions that we need answers to. To
summarize we need a clear description of what components you are using
with which database and exactly how you are inserting the records.
--
Bill Todd (TeamB)
.
- References:
- ADO and SQL2K5 and Speed
- From: Kendrick
- ADO and SQL2K5 and Speed
- Prev by Date: Re: Querying a MS SQL View...
- Next by Date: ADO and SQL2K5 and Speed
- Previous by thread: ADO and SQL2K5 and Speed
- Index(es):
Relevant Pages
|
