I have the following fields which were at one time organized every month, then every week, now every day. When it was monthly (which they would send me every 6 months so I could spend a day with eyestrain) it was for 20 employees. It started in Excel and I decided to put it in a DB because it was easier for me that way.
I could give my whine story here but I'll shut up...
Mostly I want to do it right because I want to, not because it's needed and I want to get out of my current phone monkey position. Here are my fields I'm getting in my stats which I get daily:
On every day each employee will or will not have an entry. This is where i'm getting backed up. Since there might be many entries for each day it seems like this should be seperated out or I will end up with something like this:
OK, so I don't think that's right since each day is represented dozens or hundreds of times. The reports that I get won't give me login-logout times but rather just tell me total time logged in daily (LoginTime).
The real db administrator has said that basically he will do nothing more for reports than he's doing now and if I want to give something more useful to the management staff I can figure it out on my own and no, I can't access the main DB to get real numbers.
What other information would help you help me? No, it's not homework, no it's not really important, no i'm not a db administrator.
isn't this the same as your other thread? i'm gonna merge them
Yeah, it is. the other thread said "invalid forum" or some such since I wasn't logged in.
Like I said, don't need to fix the tables to be right but I'd like to do it the right way. If they ever get their act together (incidentally, this is a huge company) I'm hoping I can extend this to a little over 2500 employees. Already some whispers about that.
Guess I can cross that bridge later. I tried a sample table with 2,000,000 entries on a desktop computer and it ran fine with almost no slowdowns so I suppose there is no real rush.