Re: Accessing A Large MS SQL Table Over ADO Components
From: Viatcheslav V. Vassiliev (support_at_oledbdirect.com)
Date: 10/11/04
- Next message: Todd Super Bassist: "NT Service not working with ADO???"
- Previous message: Brian Bushay TeamB: "Re: TADODataSet using outer joins and delete method !!!"
- In reply to: deliMawi: "Accessing A Large MS SQL Table Over ADO Components"
- Next in thread: deliMawi: "Re: Accessing A Large MS SQL Table Over ADO Components"
- Reply: deliMawi: "Re: Accessing A Large MS SQL Table Over ADO Components"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Mon, 11 Oct 2004 10:56:56 +0400
> And I want to know, if I use a standart DB Grid, does the dataset
component
> fetches all the records to client?
Client-side cursor fetches all rows, server-side does not. This does not
depend on DBGrid or other controls.
> What about the cursor location. Setting the cursor to serverside has any
> advantages? Because I had some performance loss when I set it up to Server
> Side?
Server-side cursor does not fetch all rows to client, so if server is on the
same computer, you could try server-side cursor, if server is on LAN - try
and look does it perform good, if server is remote - do not use server-side
cursor for UI. Also, server-side cursor, unlike client-side cursor, holds
resources on server - if many users will open datasets with server-side
cursor, you may have problems on server, especially if some user(s) will go
to lunch and leave cursor open.
> Could you please forward me some links or docs about Delphi + ADO + SQL
> Server Performance issues?
This newsgroup :)
For best performance and access to low-level features you may try OLEDB
Direct (http://www.oledbdirect.com). It works with OLEDB - the same
interfaces that ADO uses on low-level. For example, you will be able to
insert 1 000 000 rows in up to 10 sec.
//------------------------------------------
Regards,
Vassiliev V. V.
http://www.managed-vcl.com - using .Net objects in Delphi for Win32 +
ADO.Net
http://www.oledbdirect.com - The fastest way to access MS SQL Server,
MS Jet (Access) and Interbase (through OLEDB)
<deliMawi> сообщил/сообщила в новостях следующее:
news:4168f71a@newsgroups.borland.com...
> Hi all again,
>
> We will be developing a large database application and currently we are
> working on some base forms and planning the architecthture.
>
> An avarage table will be holding around 1000000 records in our
application.
>
> If we want to display the data on a readonly grid wich component is the
best
> to use, TADODataSet or TADOQuery ?
> What about if the grid is not readonly?
> And I want to know, if I use a standart DB Grid, does the dataset
component
> fetches all the records to client?
> What about the cursor location. Setting the cursor to serverside has any
> advantages? Because I had some performance loss when I set it up to Server
> Side?
> And also ADO Components are a good choice?
>
> Could you please forward me some links or docs about Delphi + ADO + SQL
> Server Performance issues?
>
> Thanks in advance
> deliMawi
>
>
- Next message: Todd Super Bassist: "NT Service not working with ADO???"
- Previous message: Brian Bushay TeamB: "Re: TADODataSet using outer joins and delete method !!!"
- In reply to: deliMawi: "Accessing A Large MS SQL Table Over ADO Components"
- Next in thread: deliMawi: "Re: Accessing A Large MS SQL Table Over ADO Components"
- Reply: deliMawi: "Re: Accessing A Large MS SQL Table Over ADO Components"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|
