June 8, 2007 at 1:13 pm
I've got a bunch of tables that are essentially logs - like open/close. For example say you have a bunch of users, each might have logged multiple open or close events. How do you deal with data like that? Say, group by the user, get each date of each open event, and the date of each close event which might follow it (could be null=never closed, or data error with a second open) Are there some examples, techniques, BOL syntax I've missed, discussions, anything that might help tackle this data?
TIA
June 11, 2007 at 9:49 am
What's the use of the data? Is this storing simply whenever a user opens a screen that pull back data for example?
I would set up some sort of archiving, or deletion if the history is not needed.
June 11, 2007 at 10:14 am
well, I had a nice long reply... but the forum ate it.
June 11, 2007 at 12:29 pm
Basically, what I said was it's historic data and I can't delete it. The only thing it has in common is that, for a given key, each line updates the status. So 'M' on '1/7/2006' becomes 'D' on '1/18/2006'. The trouble is, in order to get a set where status 'M' and date < 3/1/06, I have to select max(date) and join back to get the status and eliminate the row. Or, maybe this is the proper way...
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply