Apache OpenOffice (AOO) Bugzilla – Issue 46264
Accessing Large ODBC Databases
Last modified: 2009-04-22 08:38:40 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
send further to: requirements@openoffice.org
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.
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
'
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
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.
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.
Fixed in cws dbaperf1.
Please verify. Thanks.
reopen
this issue was already fixed with issue 74927 *** This issue has been marked as a duplicate of 74927 ***
close