View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0002399 | MMW v4 | DB/FileMonitor | public | 2006-02-28 14:56 | 2006-06-15 17:47 |
| Reporter | rusty | Assigned To | |||
| Priority | urgent | Severity | feature | Reproducibility | always |
| Status | resolved | Resolution | fixed | ||
| Fixed in Version | 3.0 | ||||
| Summary | 0002399: Improve Database Performance and Reliability | ||||
| Description | There are numerous DB related issues that we need to improve upon: 1) The DB slows down for very large collections (e.g. 165,000 tracks) 2) Access mdb files have reliability problems (related to configuration of the subsystem/engine and to corruption that occasionally occurs) These issues should be tackled in a future MM release, possibly via the use of sqlite (see discussion below), though it is still unclear whether this is the best approach. | ||||
| Additional Information | I kind of agree with what you wrote, and was wondering if we should also consider 1) and 2) below in addition to 3): 1) Prevent this from occurring by switching DB engines: a) Use sql express. Pro: reliable Con: Not cross platform, may not be faster http://www.microsoft.com/sql/editions/express/upgrade.mspx (see: http://www.microsoft.com/sql/solutions/ssm/access/whenmigrate.mspx ) b) Use an open source embedded db such as sqlite http://www.sqlite.org/ & http://www.kexi-project.org/about.html I'm not sure how either of these approaches would affect scripts or whether they would solve the problem. Need your comments. 2) If 1) isn't feasible, then minimize the likelihood of irrecoverable problems by: a) Having MM automatically backup the db according to some schedule b) Allowing user to somehow use one of the backup versions previously created in the event of a db problem 3) In addition to 2) we can try the approaches that you've suggested: a) Embed this functionality (I can check with the vendors), but I suspect that you're right--it'll be too expensive b) Buy one for ourselves that I can use. This could be a good short term solution, though it'll waste some time. Regards, Russell If you're bananas about music... http://www.mediamonkey.com -----Original Message----- From: Jiri Hajek [mailto:jh@mediamonkey.com] Sent: Monday, February 27, 2006 11:00 AM To: 'Russell Samuels' Subject: RE: Database problem: logs included Rusty, The database is physically damaged, it isn't even possible to Compact it in Access 2003 (it freezes). The only way to fix it (except for starting with a new database) is to use some low-level Access DB repair utility, see the list at http://www.timelyweb.com/downloads/10728/ . The demo of the first one listed there seems to be able to do the process. Now question is what should we do: - Try to license the code for such low-level fix and include it in MM. I'm afraid it would be expensive... - Buy at least one of copy of such an app in order to help users in such cases? - Anything else? | ||||
| Tags | No tags attached. | ||||
| Fixed in build | 1000 | ||||
