|
|
|||||||||
|
|||||||||
| |||||||||
|
|
|
| |||||||||
![]() |
|
|
«
Previous Thread
|
Next Thread
»
|
Thread Tools | Search this Thread | Rate Thread | Display Modes |
|
#1
|
|||
|
|||
|
Large Access DB Performance
Well then, consider this:
an access97 db used by an app through JET 3.51 does the time to execute a simple select query (max 50 results) get higher then 1 second when there are more than 30 000 records? the application needs to monitor the stats of plates handeled by a machine, but becomes useless if it would take longer than 1 sec to select a number. i usually make sure there never are 15 000 + records, but its really needed to be able to report the latest 20 weeks, which means.... 20 times 1500 records Cheers, Unkie |
|
#2
|
||||
|
||||
|
well, the access time really depends on the structure and organization of the database. If you have a complex structure, then yes... it would take longer as your table sizes grow - especially in Access. Have you thought about switching to another DBMS? Microsoft offers a free version of SQLLite (MSDE) at the MS website. You'll have to get the MMC plugin for it (Enterprise Manager), but it should function like a small version of SQLServer.
__________________
Fisherman "Any intelligent fool can make things bigger, more complex, and more violent. It takes a touch of genius -- and a lot of courage -- to move in the opposite direction." - A.Einstein |
|
#3
|
|||
|
|||
|
the structure is about 1 table ^^
might expand to 2 someday not soon |
|
#4
|
||||
|
||||
|
well, I'm not so concerned with the structure of the entire database as I am the structure of the table itself. How it is laid out, how it is organized. One of the advantages to SQLServer is the ability to physically organize data on the disk using indexes/clustered indexes. It makes adding and modifying data a little slower, but access time (on the whole) is usually accelerated a bit. How much db experience do you have? The reason I ask is I'm wondering how much the table has been normalized.
|
|
#5
|
||||
|
||||
|
as a follow-up.. if you're using a data warehouse approach (just capturing all data for reporting, not really concerned with relationships with other processes) then ignore that last comment and question.
|
|
#6
|
|||
|
|||
|
You should have no problems if your table is indexed properly. 30000 records is not really many.
|
![]() |
| Viewing: Dev Shed Forums > Programming Languages - More > Visual Basic Programming > Large Access DB Performance |
| Thread Tools | Search this Thread |
| Display Modes | Rate This Thread |
|
|
|
|