I'd be looking to make sure that the DB Server itself isn't the bottleneck here 
- quick and easy test, run the SQL select statement through Query Analyser 
(yuck!) and see what sort of response time you get.  Alternatively, (and 
shameless plug) download a copy of DBOptimizer from our website, point it at 
your server, and then get your application to hit the server and see where the 
bottleneck is.  DBOptimizer can also show you network issues if it's that, and 
can also highlight if your client is spamming a slow down message while it 
tries to digest the resultset.  The trial edition will give you all the results 
(it's evaluation time limited, not feature limited)

Peter Joint
Embarcadero Technologies, Inc. | 
www.embarcadero.com<http://www.embarcadero.com/>
peter.jo...@embarcadero.com<mailto:peter.jo...@embarcadero.com>
Office:  +61 (3) 9018-7752 | Fax: +61 (2) 8296-5831 | Mobile: +61 (404) 646 486
Linked in: http://www.linkedin.com/in/peterjoint

From: delphi-boun...@delphi.org.nz [mailto:delphi-boun...@delphi.org.nz] On 
Behalf Of Jeremy Coulter
Sent: Tuesday, 19 January 2010 7:57 PM
To: 'NZ Borland Developers Group - Delphi List'
Subject: Re: [DUG] MSSQL with D2007

OR.....your DB server is just really slow :)
We use the TADO controls, but were possible, or where I am not being lazy, use 
non DB bound controls.
However I have heard the SDAC controls are meant to be pretty good as Kyley 
seems to back up. Just a bit expensive from Memory.

jeremy

From: delphi-boun...@delphi.org.nz [mailto:delphi-boun...@delphi.org.nz] On 
Behalf Of David Brennan
Sent: Tuesday, 19 January 2010 21:19
To: 'NZ Borland Developers Group - Delphi List'
Subject: Re: [DUG] MSSQL with D2007

I should say there is something wrong with your ADO setup if it is taking that 
long for 7000 records, unless they are VERY big records.

7000 records of 2-4000 bytes each should be only a second or so (don't want to 
be more accurate in my estimate without testing, been a while since I paid much 
attention to data transfer times be honest!)

David.

From: delphi-boun...@delphi.org.nz [mailto:delphi-boun...@delphi.org.nz] On 
Behalf Of John Bird
Sent: Tuesday, 19 January 2010 8:05 p.m.
To: NZ Borland Developers Group - Delphi List
Subject: [DUG] MSSQL with D2007

Been trying to connect to MSSQL 2005 with DB Express (TSQLConnection and 
TSQLQuery), but cannot get it to work, we are getting an access violation at 
address 017E0913  in DBXMSS30.DLL  read of address 01820000

Using instead ADO (TADOConnection and TADOQuery) works fine, but is slow - 7000 
records takes 30-40 seconds to load.

The rest of the components the same  (ie TDatasetProvider, TCLientDataSet, 
TDatasource)  ie have been pointing the Datasetprovider at either the TADOQuery 
or the TSQLQuery

Also tried the TSimpleDataSet, has the same error as the first sentence.
All the queries allow me at design time to set active to true successfully, but 
still crash when the dataset is set to open....

Does anyone have any idea what could be going wrong?

And any recommendations of best combinations you prefer for MSSQL with D2007.   
I am new to connecting D2007 to MSSQL so willing to do it whichever way works 
best.

John

CONFIDENTIALITY NOTICE: This email message is for the sole use of the intended 
recipient(s) and may contain confidential and privileged information. Any 
unauthorized review, use, disclosure or distribution is prohibited. If you are 
not the intended recipient, please contact the sender by reply email and 
destroy all copies of the original message.

_______________________________________________
NZ Borland Developers Group - Delphi mailing list
Post: delphi@delphi.org.nz
Admin: http://delphi.org.nz/mailman/listinfo/delphi
Unsubscribe: send an email to delphi-requ...@delphi.org.nz with Subject: 
unsubscribe

Reply via email to