Re: Database History
Date: Wed, 12 Mar 2003 12:40:45 -0600
Message-ID: <Xns933C76CF0131Cpingottpingottbah_at_216.166.71.233>
"Lieut_Data" <lIeuT_dAtaREMOVEME_at_yahOO.com> wrote in news:b4nt9j01n68 _at_enews2.newsguy.com:
>> > Do I delete the entry from the table? Then what happens to the trouble
>> > ticket referring to it -- its stored keys now refers to a non-existent
>> > user/hardware.
>> >
>> > Or should I hard-code the information into each ticket regarding the
>> > user (I.e. dont use primary keys, but store "John" "Billcox" "IS/IT",
>> > etc..)
>> >
>> > Or should I not delete users/hardware at all? Just mark them
>> > "inactive", preventing them from showing up in the main list, where
>> > they are not used. But what if we want to use a username again, for a
>> > new employee?
>>> inventory, but you may wish to transfer the maintenance record
>> When equipment is retired it should be removed from the
>> to a service history table so that you can run a statistical
>> analysis on failures and the required fixes.
>
> This, too, makes sense -- thanks for the insight!
I wouldn't move the data because it makes reporting tougher for the end-user: they need to pull from the active and the history tables. The DBMS can handle millions of rows in a table with no issue and report writers aren't cheap (compared to a DBMS! :)
Thx!
-- Pablo Sanchez, High-Performance Database Engineering http://www.hpdbe.comReceived on Wed Mar 12 2003 - 19:40:45 CET