Quantcast
Channel: SCN: Message List
Viewing all articles
Browse latest Browse all 8667

Re: Table partition thoughts

$
0
0

Justin Molenaur wrote:

 

http://help.sap.com/hana/SAP_HANA_Administration_Guide_en.pdf

 

Take a good read through the above document at page 133, it should help you in your partitioning quest.

 

Keep in mind - you can always change the partitioning methods on the fly and put the partitions back together into one piece, so you are not setting anything in stone. Of course, this can take some time with large tables, but it's still possible. At current client in a stage in environment, a 1.6b record table was merged and repartitioned in about 10 hours.

 

Regards,

Justin

 

Sorry Justin,

 

But partitioning task requires exclusive lock(only selects are allowed)

by the "SAP_HANA_Administration_Guide_en.pdf" at page 171.

I've experienced it by myself.

 

See belows.

 

Cheers,

 

Reference2.6.10.5 Partitioning Operations

How a table is partitioned can be determined on creation or at a later point in time. You can change how a table is partitioned in several ways.

You can change partitioning in the following ways:

●Change a non-partitioned table into a partitioned table by merging all of its partitions

●Partition a non-partitioned table

●Re-partition an already-partitioned table, for example:

  ○Change the partitioning specification, for example, from hash to round-robin

  ○Change the partitioning column

  ○Increase or decrease the number of partitions

Performing a partitioning operation on a table in the above ways can be costly for the following reasons:

●It takes a long time to run, up to several hours for huge tables.

●It has relatively high memory consumption.

●It requires an exclusive lock (only selects are allowed).

●It performs a delta merge in advance.

●It writes everything to the log (required for backup and recovery).


Viewing all articles
Browse latest Browse all 8667

Trending Articles