Timeline for Table design with Microsoft SQL Server
Current License: CC BY-SA 3.0
4 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Apr 20, 2018 at 10:34 | comment | added | Robbie Dee | @AdamPlocher Ah, OK - login names should be unique and so are a key of sorts. Just saw the varchar and assumed it was a name of some sort. | |
| Apr 20, 2018 at 10:03 | comment | added | Adam Plocher | Oh, and with regard to the "Modified": I think that's a good idea. I've done it in the past, not sure why I haven't made a habit of it. In fact, some of these tables have an ongoing changelog from a trigger that records all changes to an identical table with "History" appended to the name and 2 additional cols: ChangeType (char(1) = [i]ns,[u]pd,[d]el)/ChangeDate. If I was to pick 1 column, Modified would be more appropriate terminology anyway since it could cover ins, upd, and del. So yeah, I should go with all 3 or just 1 in those cases I guess. Having 2 (ins, del) doesn't make sense... | |
| Apr 20, 2018 at 9:58 | comment | added | Adam Plocher | Thanks Robbie, yeah I didn't make it too clear. There's one small note next to ONE of the "By" columns in my mock schema that mentions they will sometimes be int FK's, too - easy to miss, I should have put that in my column notes. The particular system I'm working with now is an AD-based Windows Client app, so it was a little trickier. I just ended up storing Windows login names, instead of a GUID or SID, but in general (at least on the web), I would have a User table and a UserID stored in those. Thanks for the advice. | |
| Apr 20, 2018 at 9:20 | history | answered | Robbie Dee | CC BY-SA 3.0 |