Login | Register   
RSS Feed
Download our iPhone app
Browse DevX
Sign up for e-mail newsletters from DevX

By submitting your information, you agree that devx.com may send you DevX offers via email, phone and text message, as well as email offers about other products and services that DevX believes may be of interest to you. DevX will process your information in accordance with the Quinstreet Privacy Policy.

Tip of the Day
Language: SQL
Expertise: Intermediate
Aug 8, 2006



Building the Right Environment to Support AI, Machine Learning and Deep Learning

The Value of Data Archiving

Table(s) holding every day transaction data can grow huge in size over period of time. This not only slows down applications, it also causes database contention leading to maintainence nightmare. A simple table design modification can avoid lots of misery in your production environment.

Instead of designing a single table holding all of the transactional data, create two tables: the actual transaction table and an archive table.

Everyday before the business hours, move the data to the archive table from the actual transaction table. This avoids undesired growth and ensures good production performance.

Note: Your archival logic will depend mainly on your business processes and can be daily, weekly, monthly, or based on some other criteria.

Navin Varma
Comment and Contribute






(Maximum characters: 1200). You have 1200 characters left.



Thanks for your registration, follow us on our social networks to keep up-to-date