This may be one for the gurus, or it could be big standard. Don't know.
I'm looking for some help in designing a database. The problem I have is related to data aging on Oracle instances. I can't find any help on it.
The problem I have is that I've got 3 categories of data, which is new/warm/old. Essentially, new is data which is 1 hour old. Warm is data which is kept for 24 hours, old is kept for 6-8 weeks.
So the data needs to age. I think obviously the mechanics of it, Is that I need to partition the data in 1 hour range perhaps, and have a pl/sql package to run every hour, that moves partitions about from new to old, like a sliding window mechanism.
Thanks for your help.
By rrjii2000 in forum .NET
Last Post: 03-26-2010, 02:34 PM
By helme_syahiemie in forum VB Classic
Last Post: 04-06-2006, 09:39 PM
Last Post: 01-13-2001, 03:15 PM
By sb in forum VB Classic
Last Post: 07-22-2000, 05:07 AM
By William Gaddam in forum VB Classic
Last Post: 05-02-2000, 10:19 PM
Tags for this Thread
Top DevX Stories
Easy Web Services with SQL Server 2005 HTTP Endpoints
JavaOne 2005: Java Platform Roadmap Focuses on Ease of Development, Sun Focuses on the "Free" in F.O.S.S.
Wed Yourself to UML with the Power of Associations
Microsoft to Add AJAX Capabilities to ASP.NET
IBM's Cloudscape Versus MySQL