The reason I used partitioned tables is because I worked at a financial institution that deals with a *huge* number of transactions each day. We have to keep different levels of transaction information for different amounts of time. So we used partitioning to help manage the volume of data. A brief description follows, to give an illustration of how and why to use partitioned tables:
- We need complete transaction details for 35 days. (Actual req was for 30 days, we kept five additional days for simplifying the monthly summary and leave a bit of elbow room for error recovery.)
- We need transaction summaries for 18 months
- Database needs to be online 24/7
- We had several indexes on the data that take a good amount of time to rebuild
- ...others not mentioned here...
Because of these requirements, we had two tables TxnDtls and TxnSumHist for the details and summaries. We partitioned both tables based on the date. For TxnDtls, we used the day (YYYYMMDD), and for TxnSumHist, we used the month (YYYYMM). (In the remainder of the post, think of YYYYMM and YYYYMMDD as stand-ins for the actual dates.) Our process consisted of roughly:
- Create table TxnDtls_YYYYMMDD
select top 0 * into TxnDtls_YYYYMMDD from TxnDtls
- Bulk load the transaction details into the table (using BCP)
- Build the indexes.
- Update the partition function to eliminate the 35-day-old TxnDtls_YYYYMMDD table and add the new table.
- If it's the first day of the month, then:
- Create the new TxnSumHist_YYYYMM table, summarizing the data
select -- Key fields
D.Merchant_ID, 'YYYYMM' as Billing_Period, D.TxnType, ...
-- Statistics fields
sum(D.Amount) as TxnTotal, count(*) as TxnCount,
into TxnSumHist_YYYYMM S
from TxnDtls D
where D.TxnDate between ... and ...
group by D.Merchant_ID, D.TxnType, ...
- Build the indexes
- Update the partition function to eliminate the 19-month-old TxnSumHist_YYYYMM table and add the new one.
- Drop the old TxnSumHist_YYYYMM table
- Drop the old TxnDtls_YYYYMMDD table
By carefully distributing the table and index partitions among your storage systems, you can get surprisingly good performance. (Assuming you have the I/O capacity and enough storage devices to distribute the load to. Towards the end of the project, we used a couple fiber optic cards to connect to a massive storage system that distributed 1.6TB of data over numerous 20GB drives. The performance was stunning!)
If anyone has any specific questions about the system, just ask, and I'll answer as best as I can. But the system was decommissioned about six months ago, and I work at a different company now, so some of the finer details are still leaking away from my memory... ;^)
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
Read Where should I post X? if you're not absolutely sure you're posting in the right place.
Please read these before you post! —
Posts may use any of the Perl Monks Approved HTML tags:
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.
| & || & |
| < || < |
| > || > |
| [ || [ |
| ] || ] ||