By mitchp
via java.dzone.com
Published: Aug 16 2012 / 09:20
Logging tables are usually at the periphery of a design effort, sometimes added as an after-thought. Usually, a logging table has a large number of rows and many optional columns, most containing NULLs. In addition, because ALTER TABLE statements become expensive in a production system, these tables often include some kind of a serialized array (JSON, CSV) for all the optional fields. In otherwise well engineered systems, these logging tables stick out as an embarrassing mess.
-
The Cloud Isn't a Beverly Hills Nose Job at a Tijuana Price
-
UnQLite - An Embeddable NoSQL Database Engine
-
The Right Way to Retinafy Your Websites
-
Final ALM Certification Jumpstarts May 28th and May 29th
-
3 simple steps to boost performance of a PHP web application
-
How to setup a Load Balanced Web Farm of Virtual Machines (Linux or otherwise) on Windows Azure (command line)
Add your comment
