Greetings one and all.
I am two or three days away from purchasing Links SQL because I much prefer the database approach. The question I have is about system resources.
Several ISP's forbid the use of Links (non-SQL) stating the "enormous resource usage" of the system. My current links DB is about 300k itself, so I certainly understand their concerns.
One of the primary reasons I want to move to a SQL version is to allow for MUCH greater customization and usage of the data (top 10 lists and such) across the entire site.
Will moving to the SQL version solve, help, or make the problem of resource usage worse?
Sincerely,
------------------
Wayne Hunt
Amiga.org
http://www.amiga.org
I am two or three days away from purchasing Links SQL because I much prefer the database approach. The question I have is about system resources.
Several ISP's forbid the use of Links (non-SQL) stating the "enormous resource usage" of the system. My current links DB is about 300k itself, so I certainly understand their concerns.
One of the primary reasons I want to move to a SQL version is to allow for MUCH greater customization and usage of the data (top 10 lists and such) across the entire site.
Will moving to the SQL version solve, help, or make the problem of resource usage worse?
Sincerely,
------------------
Wayne Hunt
Amiga.org
http://www.amiga.org