Skip to main content

MySQL Table Partitioning over cloud (Google & AWS)

AWS documentation also says horizontal physical partitioning of large table data is best practices instead keeping all in one physical file.


There are advantages and disadvantages to using InnoDB file-per-table tablespaces, depending on your application. To determine the best approach for your application, go to InnoDB File-Per-Table Mode in the MySQL documentation. We don't recommend allowing tables to grow to the maximum file size. In general, a better practice is to partition data into smaller tables, which can improve performance and recovery times.

One option that you can use for breaking a large table up into smaller tables is partitioning. Partitioning distributes portions of your large table into separate files based on rules that you specify. For example, if you store transactions by date, you can create partitioning rules that distribute older transactions into separate files using partitioning. Then periodically, you can archive the historical transaction data that doesn't need to be readily available to your application.

CREATE TABLE trb3 (id INT, name VARCHAR(50), purchased DATE) ;

ALTER TABLE trb3 PARTITION BY RANGE( YEAR(purchased) ) (
PARTITION p0 VALUES LESS THAN (1990),
PARTITION p1 VALUES LESS THAN (1995),
PARTITION p2 VALUES LESS THAN (2000),
PARTITION p3 VALUES LESS THAN (2005)
);

SELECT table_name, partition_name,table_rows,data_length FROM INFORMATION_SCHEMA.PARTITIONS WHERE TABLE_NAME='trb3' AND TABLE_SCHEMA='sumandb';
+------------+----------------+------------+-------------+
| table_name | partition_name | table_rows | data_length |
+------------+----------------+------------+-------------+
| trb3       | p0             |          0 |       16384 |
| trb3       | p1             |          0 |       16384 |
| trb3       | p2             |          0 |       16384 |
| trb3       | p3             |          0 |       16384 |
+------------+----------------+------------+-------------+
4 rows in set (0.19 sec)

insert into trb3 values (1,'sdfsdfs','1989-06-06');
insert into trb3 values (2,'sdfsdfs','1989-06-06');
insert into trb3 values (3,'sdfsdfs','1990-06-06');
insert into trb3 values (4,'sdfsdfs','1990-06-06');
insert into trb3 values (5,'sdfsdfs','1990-06-06');
insert into trb3 values (6,'sdfsdfs','1997-06-06');
insert into trb3 values (7,'sdfsdfs','1997-06-06');

MySQL [sumandb]> select * from trb3;
+------+---------+------------+
| id   | name    | purchased  |
+------+---------+------------+
|    1 | sdfsdfs | 1989-06-06 |
|    2 | sdfsdfs | 1989-06-06 |
|    3 | sdfsdfs | 1990-06-06 |
|    4 | sdfsdfs | 1990-06-06 |
|    5 | sdfsdfs | 1990-06-06 |
|    6 | sdfsdfs | 1997-06-06 |
|    7 | sdfsdfs | 1997-06-06 |
+------+---------+------------+
7 rows in set (0.19 sec)

MySQL [sumandb]> SELECT table_name, partition_name,table_rows,data_length FROM INFORMATION_SCHEMA.PARTITIONS WHERE TABLE_NAME='trb3' AND TABLE_SCHEMA='sumandb';

+------------+----------------+------------+-------------+
| table_name | partition_name | table_rows | data_length |
+------------+----------------+------------+-------------+
| trb3       | p0             |          2 |       16384 |
| trb3       | p1             |          3 |       16384 |
| trb3       | p2             |          2 |       16384 |
| trb3       | p3             |          0 |       16384 |
+------------+----------------+------------+-------------+
4 rows in set (0.19 sec)



Thanks for reading
Plz dont forget to like Facebook Page..
https://www.facebook.com/pages/Sql-DBAcoin/523110684456757

Comments

Post a Comment

Plz dont forget to like Facebook Page..
https://www.facebook.com/pages/Sql-DBAcoin/523110684456757

Popular posts from this blog

mongoDB error : aborting after fassert() failure

What to do when facing errors on mongoDB “aborting after fassert() failure”

I like errors, in mongoDB this is the first error I faced and luckily many times. This error i faced during restoring name-space on local and restarting db system. I am still searching the exact root cause of this issue but i am able to resolve the current problem through below steps.

Remove all relevant namespace files from data-file route path..Now repair mongo instance using mongod process.mongod --repair ////////// execute command from bin folder path Then start server using mongd process, if started server successfully then ..mongod  ////////// execute command from bin folder path Restore last backups as normal process.Now check database by connecting mongo shell. Thanks for reading, 
Please comment your experience if you faced and also share knowledge if you have better steps to resolve...


https://www.facebook.com/pages/Sql-DBAcoin/523110684456757

SQL71562: external references are not supported when creating a package from this platform

Last week I got this error from one of developer who was trying to deploy his project from Testing server to SQL Azure QA server. He was using “Deploy Database to SQL Azure” option from SSMS Tool-Task option.

After connecting to SQL Azure portal when operation started to deployment below errors occurs.

Validation of the schema model for data package failed. Error SQL71562: Error validating element xx.xxx.xx:function .dbo.xxx has an unresolved refrence to object xx.dbo.xxxx external refrences are not supported when creating a package from this platform.



Reason: The reason of the this error was; some functions of project was dependent on master database and only single database was being deploy to SQL Azure. DACFx must block Export when object definitions (views, procedures, etc.) contain external references, as Azure SQL Database does not allow cross-database external references So, this error was coming.

Solution : I suggested him to create those function to locally on local database what…

How to recover msdb database from suspect mode

It was Monday 9th Jun 47 degr. temperature of Delhi-NCR. Temperature was like boiling me and database. When I reached my office( @ 8.45 am) got an alert from one of Server.
“MSDB is in suspected mode” At the same time comes in my mind, this issue will boil me today.. I just tried to cool my self through cold drink then connected server from my local system using windows authentication mode..