MySQL table design / architecture, table is too big -
I have a MySQL db that contains a lot of text, I'm in a data gathering from a website and a The table is inserted.
I am using SSD HD (100 GB) for DB and I could not find the place, I think that something in the structure of the table is too big, I can not guess the size For all the columns, I'm using the varchar \ text \ media text for most areas. When I insert all the data to DB, then I monitor the errors and when I see that I am trying to insert a particular field I am increasing the size of the area (like varchar (1000) to Varchar ( 2000)).
By now I have approximately 1.8 M lines, I think I am doing something wrong.
Here is the structure of my table << p> What should I do? I have about 20% of the data (which means that I need 350GB) What is the display of space? Can I split the table into several tables on multiple tables? I am going to use the Sphinx in the index and in the end I am querying the data. All non-item column values stored in an 8KB record (undivided unit of space on your HDD) goes. Text column values are stored in external blocks of data as pointers. These types of structure (very text oriented) are better controlled by the NOSQL (SQL only) MongoDB database. But I suspect there are many things that you can handle and amp; The process of structuring a database (updating in one place - visible everywhere - is called generalization) is to be called normalization to avoid duplicate information and to allow easy updates. If you have structured data such as those large VARCHARs (eg: the inventor's length 1500) as many elements of data (eg: names of different inventors by coma) then You can reorganize your DB, by making an inventory table and referencing the table.
Comments
Post a Comment