Tag Info

New answers tagged

0

For the sake of it I'll describe an approach not mentioned above. It is typically used for temporal data. Not sure it will fit your needs, but here it goes. The idea is to have a copy of your original with two additional attributes, begin_time and end_time: create table ... ( ... , begin_time timestamp default now() not null -- MySQL timestamp deviates from ...


0

Deltas The data you are "snapshotting" -- how often does it change? I suggest looking into storing only the "deltas". When some piece of the snapshot does not change at all, the delta is empty, and you can store nothing. For reconstructing a snapshot at some point in the past, the processing is costly -- you need to walk through the versions, applying ...


0

Create a new table, that has all the columns of the existing table, but also a time column, which is set to the value of the time the snapshot was initiated. You're adding a new fact to store about an existing set of facts (each table should store one kind of fact, ideally). The value of the time column identifies each snapshot. If you need to query across ...


0

Database Administrators and Database Architects are similar. In crude terms, I would say that a database administrator approaches problems from a systems level (bottom up), while a relational data architect thinks from the perspective of the application and even user interface (top down). Both of of them share major responsibilities, including but not ...



Top 50 recent answers are included