Sql-server – Partition Function Question – DatetimeOffset

partitioningsql server

I am planning to partition a large table on [datetimeoffset]. I thought the data in that column were all yyyy-mm-dd hh:mm:ss -08:00, but there are multiple offsets in that column such as -07:00 and -06:00.

My question is what should my partition function use? This is what I'm currently using…

CREATE PARTITION FUNCTION [PF_table_DatetimeOffset0] (DATETIMEOFFSET(0))
AS
RANGE RIGHT FOR VALUES (
    '20120101 00:00:00.000 -08:00', 
    '20130101 00:00:00.000 -08:00',  
    '20140101 00:00:00.000 -08:00',
    '20150101 00:00:00.000 -08:00',
    '20150201 00:00:00.000 -08:00',
    '20150301 00:00:00.000 -08:00',
    '20150401 00:00:00.000 -08:00',
    '20150501 00:00:00.000 -08:00',
    '20150601 00:00:00.000 -08:00',
    '20150701 00:00:00.000 -08:00',
    '20150801 00:00:00.000 -08:00',  
    '20150901 00:00:00.000 -08:00',  
    '20151001 00:00:00.000 -08:00',  
    '20151101 00:00:00.000 -08:00',  
    '20151201 00:00:00.000 -08:00',  
    '20160101 00:00:00.000 -08:00'
);

Thank you!

Best Answer

Be aware of the implications in regions that have the nasty habit of changing their clocks twice a year and Check this Link

Related Solutions

Sql-server – Best practices for creating partition schemes and functions

If you have a single schema and function and you alter that to move data around all the tables will be moved in a single shot instead of having to change all of them.

Mysql – Partition by year and sub-partition by month thesql

I had to do the same thing and solved slightly differently. Basically as far as I understand by reading the docs MySQL subpartitioning does not support partition types besides HASH and KEY.

In MySQL 5.6, it is possible to subpartition tables that are partitioned by RANGE or LIST. Subpartitions may use either HASH or KEY partitioning. This is also known as composite partitioning.

This means that we can't determine in what subpartition a record will end up. It's up to MySQL. So I don't think it's wise giving such names to your subpartitions (i.e. january) because no way you're going to know if stuff created on that month will end up there. This because you can't subpartition by MONTH(nav_date) but only by HASH(MONTH(nav_date)) or KEY(MONTH(nav_date)).

So to solve the problem I decided to create a new month column in my table and then I added an index to it. Then I subpartioned by KEY(month) without caring about the subpartition names. This way in MySQL 5.6 I could select the main partition from the FROM clause and the subpartition by specifying the month in the WHERE clause.

Follows the full example:

CREATE TABLE `my_example` (
    `id` int(10) unsigned NOT NULL AUTO_INCREMENT,
    `value` double DEFAULT NULL,
    `is_deleted` tinyint(1) NOT NULL DEFAULT '0',
    `timestamp` datetime NOT NULL,
    `last_modified` datetime NOT NULL,
    `month` tinyint(1) NOT NULL,
    PRIMARY KEY (`id`,`timestamp`, `month`),
    KEY `in_is_deleted` (`is_deleted`),
    KEY `in_last_modified` (`last_modified`),
    KEY `in_timestamp` (`timestamp`),
    KEY `in_month` (`month`)
) ENGINE=InnoDB DEFAULT CHARSET=utf8 COLLATE=utf8_unicode_ci
PARTITION BY RANGE (YEAR(`timestamp`))
SUBPARTITION BY KEY (`month`) 
SUBPARTITIONS 12 (
    PARTITION p2011 VALUES LESS THAN (2012),
    PARTITION p2012 VALUES LESS THAN (2013),
    PARTITION p2013 VALUES LESS THAN (2014),
    PARTITION p2014 VALUES LESS THAN (2015),
    PARTITION p2015 VALUES LESS THAN (2016),
    PARTITION p2016 VALUES LESS THAN (2017),
    PARTITION p2017 VALUES LESS THAN (2018),
    PARTITION pmax VALUES LESS THAN MAXVALUE
);

EXPLAIN PARTITIONS SELECT * FROM my_example PARTITION (p2015); -- will go through all twelve subpartitions
EXPLAIN PARTITIONS SELECT * FROM my_example PARTITION (p2015) WHERE month = 9; -- will look only into one subpartition

Best Answer

Related Solutions

Sql-server – Best practices for creating partition schemes and functions

Mysql – Partition by year and sub-partition by month thesql

Related Question