Issue 46264 - Accessing Large ODBC Databases
Summary: Accessing Large ODBC Databases
Status: CLOSED DUPLICATE of issue 74927
Alias: None
Product: Base
Classification: Application
Component: code (show other issues)
Version: OOo 2.0 Beta
Hardware: PC Windows 2000
: P2 Trivial with 3 votes (vote)
Target Milestone: OOo 3.2
Assignee: marc.neumann
QA Contact: issues@dba
URL:
Keywords: performance
Depends on:
Blocks:
 
Reported: 2005-03-30 07:39 UTC by goodwinm
Modified: 2009-04-22 08:38 UTC (History)
3 users (show)

See Also:
Issue Type: ENHANCEMENT
Latest Confirmation in: ---
Developer Difficulty: ---


Attachments

Note You need to log in before you can comment on or make changes to this issue.
Description goodwinm 2005-03-30 07:39:11 UTC
At work I have to work with a large SQL database based on MS SQL Server. One 
table of this database contains appr. 49000 rows. I need to be able to apply a 
filter to select the rows I need to work with. But the filter apparently only 
applies to the appr. 200 rows of data, which are currently loaded into the 
window. Actually the filter should be applied to the complete table. I do the 
same thing from MS Access and don't have any problem there.

The other point is the time it takes to jump from the first row to the last row 
of the table. This takes much too long (Almost one minute).

Since the database is company confidential, I'm afraid I can't share it with 
you for research of the problem.

Kind regards,

GoodwinM
Comment 1 christoph.lukasiak 2005-04-25 13:39:45 UTC
send further to: requirements@openoffice.org
Comment 2 patrick_headley 2005-08-07 19:20:27 UTC
I too see that loading records from a SQL Server data source is significantly 
slower than accessing the same data using MS Access. Besides the data just 
loading slower I believe the biggest problem is that when you move from the 
first to the last record Base loads the entire recordset instead of jumping to 
the last record.

For me to suggest to my clients that they use OpenOffice over other products 
speed is going to have to be addresses as I wouldn't want my clients to feel 
that the move was in the wrong direction.

Patrick.
Comment 3 gypsymauro 2007-02-28 11:14:07 UTC
I agree, openoffice base it's so slow accesing tables with many rows,
resolving this isssue is a MUST to gain migration from MS office
Comment 4 gypsymauro 2007-02-28 11:14:38 UTC
I agree, openoffice base it's so slow accesing tables with many rows,
resolving this isssue is a MUST to gain migration from MS office
Comment 5 drewjensen.inbox 2007-10-13 05:42:50 UTC
'
Comment 6 Mechtilde 2007-10-13 10:02:31 UTC
Do you use the filter of a form?

do you try a query instead of a filter. Where is the database server? On
localhost? In the intranet? Or in the Internet
Comment 7 Frank Schönheit 2009-02-18 13:01:53 UTC
fs->oj: I suppose this is fixed with your latest performance fixes. Please
provide the link to the Wiki page which explains the performance you gained in
traveling large result sets. Thanks.
Comment 8 ocke.janssen 2009-02-20 09:59:03 UTC
This one seems to be fixed with issue 74927. The fix is available in a version
>= DEV300 m38 or >= OOO310 m1.

Could someone verify that this one is fixed? I accessed a MySQL table with 10K
rows and it took 1 s to jump to the last row.
Comment 9 ocke.janssen 2009-02-25 12:08:30 UTC
Fixed in cws dbaperf1.
Comment 10 ocke.janssen 2009-03-06 13:56:07 UTC
Please verify. Thanks.
Comment 11 marc.neumann 2009-04-22 08:32:42 UTC
reopen
Comment 12 marc.neumann 2009-04-22 08:34:52 UTC
this issue was already fixed with issue 74927

*** This issue has been marked as a duplicate of 74927 ***
Comment 13 marc.neumann 2009-04-22 08:38:40 UTC
close