Re: Newbie question on table design.


"paul c" <toledobythesea@xxxxxxxx> wrote in message
news:dwaYh.131520$DE1.106984@xxxxxxxxxxxx
Cimode wrote:

... Historising tables in any form of shape is a hack. If a
DBMS requires so much operations to historize information what's the
point using it in the first place?
...

Not entirely sure I understand this, but I suspect I agree. I think
keeping history involves a "separate" database, even though I don't have a
simple definition of what "separate" means in practice, only that
operations on separate db's mightn't always give the same results given
the same values.


Why would you need a "separate" database? I was under the impression that
all you need to do is to add a time dimension to each relation for which you
need to keep history. The additional dimension can be implemented as an
attribute with an interval data type.

p


.

Relevant Pages

  • Re: Design for historical data
    ... > types of visits are really that, 3 separate types of visits, which store ... billion rows of page delivery history in a system I helped build (I know ... Good design is important, decent, well balanced hardware (disk, ... Pro SQL Server 2000 Database Design - ...
    (microsoft.public.sqlserver.programming)
  • Re: Waid and Kitson seem to be gone
    ... universe, but a lot of losses as well. ... GA history AND most of the Silver Age history - each one had evolved ... Inc. stories that took place in a separate timeline, ... Teen Titans - or maybe Titans West. ...
    (rec.arts.comics.dc.universe)
  • Re: Design for historical data
    ... types of visits are really that, 3 separate types of visits, which store ... is going to be poor table design and poor indexing. ... All prior history must be ... > patient - this would result in largest number of records in one table ...
    (microsoft.public.sqlserver.programming)
  • Re: 365 databases a year
    ... It is generally good to separate the two. ... history table as well with a current date of today... ... putting ALL of the history into a separate database from the current info ... I assume you mean storing a timestamp in every applicable ...
    (microsoft.public.sqlserver.server)
  • Re: Newbie question on table design.
    ... I think keeping history involves a "separate" database, even though I don't have a simple definition of what "separate" means in practice, only that operations on separate db's mightn't always give the same results given the same values. ... I was under the impression that all you need to do is to add a time dimension to each relation for which you need to keep history. ... The additional dimension can be implemented as an attribute with an interval data type. ...
    (comp.databases.theory)