Re: Suggestions for table design

[Peter Brawley]

For recency you need timestamps of some sort. If there can be multiple timestamps & statuses for a computerid, you need a table for 'puters and a table for statuses.

To me your model looks a bit sparse, you might want to take a more thporough approach eg https://www.artfulsoftware.com/dbdesignbasics.html

Several approaches for the query pattern you're asking about are discussed under "Within-group aggregates" at https://www.artfulsoftware.com/queries.php