Big databases

[Leopold Palomo Avellaneda]

Hi,

I'm trying to make some king of collection with all the files from some cds 
that I have of backups, collections of several files, etc. The idea is to 
have some kind of register of all the files that I have. When I need I file, 
search in the database, show me the volume (a cd/dvd) and the path and then, 
taking it.

The import function works very well, not as one year ago. The problem is that 
tellico (or sqllite ...) has problems managing >40K registers. I have to 
admit that I don't have a box cutting the edge, it's just a amd64 3200 with 
1Gb of RAM running a debian amd64 distro. :-)

This then makes me think in one reflexion about this problem. Probably, 
although the migration to a sql server with improve it, there's some problem 
in the manage of the database in the tellico structure. I think that tellico 
has to minimize the access to the data, because in a large database is not 
practical. To manage a little collection will not be a problem because I 
think that the database is in memory, but it's better to have a screen in a 
minimal information about the whole database and the complete of one register 
and all the other makings queries to the database (sqllite or server). I 
think that is not practical have a complete list of all the register because 
then the manage of the database became impractical eating all the resources 
of the box.

Well, this is my 2 cent.

Regards,

Leo







-- 
--
Linux User 152692
PGP: 0xF944807E
Catalonia
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
Url : http://forge.novell.com/pipermail/tellico-users/attachments/20070303/29fd357e/attachment.pgp