Re: Please display the table faster in the datagrid
- From: "Dmitriy Antonov" <antonovdima@xxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Mon, 14 Nov 2005 12:40:51 -0500
"cj" <cj@xxxxxxxxxxxxx> wrote in message
news:eGmUVwT6FHA.3804@xxxxxxxxxxxxxxxxxxxxxxx
> Thanks Dmitriy, I did find some 3rd party tools but I'm not ready to
> recommend purchasing them yet. I don't think it'll work for me to try to
> develop this action on my own for all those reason you mention.
>
> I was wondering, if I set up a datatable with the columns the same as the
> VFP table would I be able to use mySQLCommand.ExecuteNonQuery() with a SQL
> command like "Select field1, field2, etc Insert into dt" and it be faster
> that the myFileAdapter.Fill(ds, tableName)? I doubt I have the sql
> command correct but I think you will see what I'm talking about.
>
> It was also mentioned to me to try the odbc drivers instead of the oledb
> drivers.
>
If you are still looking for solution how to retrieve 60 millions records
faster, then forget about it. You definitely can find something, which give
you 10-15% gain in performance in terms of actual data retrieval, but
network traffic and memory usage on workstation will remain the same and it
is not acceptable. You can't populate a grid with 60 million records (which
are, in addition, denormalized version of three tables and thus pretty
wide - with many number of columns) without significant penalty. You will be
even greater penalized, when this application is used by many users
concurrently - you can destabilize entire enterprise with such application.
I don't think ODBC is faster than native OLEDB for SQL server - probably,
just the opposite. As for VFP - I don't know.
If you will implement something that I mention as "virtual" grid - the one
populated on demand, then use of intermediate tables is possible, but hardly
reasonable. You will not be able to avoid those complexities that I
mentioned - all of them remain the same and the need to take care about
intermediate tables is added (you should know when and how to populate them,
when to clear, when to remove, resolve conflicts between users working
concurrently, etc).
Again, I don't know much about .Net. Maybe there is something available
there. But main idea remain the same - you should populate visual elements
with just portion of data (most likely with that portion, which is currently
visible on the screen). Actual implementation depends on functional
requirements and on available tools, and being .Net developer you know these
tools better than me (or ask .Net guys for recommendations).
Dmitriy.
.
- References:
- Re: Please display the table faster in the datagrid
- From: Ralph
- Re: Please display the table faster in the datagrid
- From: vbexp
- Re: Please display the table faster in the datagrid
- From: Dmitriy Antonov
- Re: Please display the table faster in the datagrid
- From: cj
- Re: Please display the table faster in the datagrid
- From: Dmitriy Antonov
- Re: Please display the table faster in the datagrid
- From: cj
- Re: Please display the table faster in the datagrid
- Prev by Date: Re: Please display the table faster in the datagrid
- Next by Date: Re: Couldn't find installable ISAM error from VB 6 / Access 2003
- Previous by thread: Re: Please display the table faster in the datagrid
- Next by thread: Re: Please display the table faster in the datagrid
- Index(es):
Relevant Pages
|