Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
Home
Discussion Groups
Database Servers
DB2InformixIngresMS SQLOraclePervasive.SQLPostgreSQLProgressSybase
Desktop Databases
FileMakerFoxProMS AccessParadox
General
General DB TopicsDatabase Theory
Related Topics
Java Development.NET DevelopmentVB DevelopmentMore Topics ...

Database Forum / General DB Topics / General DB Topics / February 2005

Tip: Looking for answers? Try searching our database.

Designing large databases

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
manhquynh@catdang.com - 18 Feb 2005 04:52 GMT
Hi,

I don't know how to formulate this question, so I try this and see
where it ends.
I want to create a database that will probably grow very big. How
should I do? My database is a Mysql DB and it will store free text
where you can search in it.

//M
Ed Prochak - 18 Feb 2005 17:59 GMT
The phrase:
a database that will probably grow very big
is essentially meaningless. What is very big?

is bigness defined by total database size?
is 1megabyte very big? 1gigabyte? 1terabyte?

or
is bigness defined by total rows in the largest tab?
is 1million rows very big? 1billion rows? 1trillion rows?

or
is bigness defined by response time?
is 1 second too slow? is one minute? one hour?

Now if you want to search free text why even use a database? free text
stored in files might be just as easily searched.

Seems to me you haven't defined your real problem yet.
  Ed
--CELKO-- - 24 Feb 2005 17:51 GMT
>> My database is a Mysql DB and it will store free text where you can
search in it. <<

Wrong product.  Look up Zyindex or other document management/textbase
systems.
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2009 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.