Home : Products : Gossamer Links : Discussions :

Products: Gossamer Links: Discussions: Re: [Alex] Multiple database usage in same Links SQL? - Suggestion: Edit Log

Here is the list of edits for this post
Re: [Alex] Multiple database usage in same Links SQL? - Suggestion
I just want to bring this topic up again because I'm still highly interested in a multiple database solution, too.

What I need is not having all LSQL-tables in every database.
I want to use multiple databases to store multiple LSQL-Link tables.

Coming to the point:

I'm importing lots of product datafeeds of different online-shops into my LSQL-db.

I want to have a Links-Database for each shop but all the rest in the main db.
While building the directory all data should be merged into one single directory
(all Links-tables should have the same structure).

I need this in reason of speeding up the directory and reducing the size of the links-table(s).
Actually I am limited in importing all datafeeds because of the reasons mentioned above.

If I would import all my datafeeds, my actual links-table would have more than 10 million rows.
So I think it's clear to everyone, that dealing with multiple db's with just 150.000 to 500.000 rows (a db for each datafeed) would be much better.

Regards,
Manu

Shopping Portal Shop-Netz.de® | Partnerprogramme | Flugreisen & Billigflüge | KESTERMEDIA e.K. | European Affiliate Marketing Forum.

Last edited by:

ManuGermany: Dec 1, 2005, 12:36 AM

Edit Log: