MySQL Forums
Forum List  »  Partitioning

Re: Partitioning dilemma
Posted by: Philopator Ptolemy
Date: July 21, 2010 01:47PM

First of all thanks for the reply.

Below are the answers:
* Access - 99% of time OLTP part of the app adds/accesses very latest sessions/transactions by id (i.e. access on one end). Backoffice accesses latest month of data 95% of time.
* session tables are keyed with GUID but we're considering to change it to auto-inc, transaction table is keyed by auto-inc INT.
*deleting is done only for archiving data older than 6 month
*sessions typically last few hours
*we're trying to use InnoDB for transactional semantics on financial data.

There is one complication though: our system can receive transactions (not db trx) from external systems. We provide idempotent interface meaning that if they post the same trx twice we always return the same result. This means that we need to find their trx or make sure that it's absent. This means that we might need to scan ALL trx table indexed on external_trx_id.

Options: ReplyQuote

Written By
July 20, 2010 08:51AM
July 21, 2010 11:58AM
Re: Partitioning dilemma
July 21, 2010 01:47PM
July 26, 2010 11:15PM
July 27, 2010 09:02AM
July 27, 2010 08:06PM

Sorry, you can't reply to this topic. It has been closed.

Content reproduced on this site is the property of the respective copyright holders. It is not reviewed in advance by Oracle and does not necessarily represent the opinion of Oracle or any other party.