sql - Table Partitioning -

How beneficial is the use of the division of tables compared to the general perspective?

Sample case or detailed comparative analysis which can be statistical (I know that this is a word very strong, but it really helps if it is illustrated by some numbers) emphasis on the usefulness of the process Gives Partitioning is extremely powerful, and in fact a table is dividing the data into several smaller tables - then uniting them using a single scene. For example, 'ipnumbers' can be divided into tables 'ipnumbers_1', 'ipnumbers_2' and 'ipnumbers_3', where the first table contains obstacles, so only 0.0.0.0 - 50.0.0.0 are stored, and the second table There are barriers to allowing only a range of 50.0.0.1 to 100.0.0.0. Etc. A view can be added which adds the partitioned table to one:

  SELECT * Select all from the Ipnumbers_1 union * Select all from ipnumbers_2 * from ipnumbers_3  
  SELECT * FROM Ipnumberview where ipno = 60.0.0.1  
 
 .. The SQL Server query optimizer will know that only the 'ipnumbers_2' table should be checked, and you can thus get a huge speed improvement in this way. 
 
 In addition to inserting schemabound ideas (can automatically insert data into the correct destination table), and tables can be placed on a separate server (although it is a bit difficult to setup) , And you can also add indexes for scenes 
 
 Have fun!