Comments (2)
  • Add a Comment
  • Edit
  • More Actions v
  • Quarantine this Entry

1 localhost commented Permalink

Seems to me rolling partitions in DB2 based on dates or timestamps should have a well documented best practices approach. We have a case where we add 5 million rows a week and purge last weeks rows at the end of the second week. This is a very terse discription of theproblem, but any thoughts you'd have on the design and maintenance of soon to be old unused partitions and yet to be used future partitions all based on dates or timestamp columns wouldbe greatly appreciated. md m

2 localhost commented Permalink

<p>Actually now my Mum has started using email she probably will one day navigate to that throw away comment. :-)</p> <p>On the rolling partitions question: I'm sorry I don't have useful input on that.</p>