Timeline for How do you keep track of the meaning of your SQL fields?
Current License: CC BY-SA 3.0
8 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Apr 12, 2017 at 7:31 | history | edited | CommunityBot | replaced http://programmers.stackexchange.com/ with https://softwareengineering.stackexchange.com/ | |
| Jun 24, 2014 at 9:19 | history | edited | gnat | CC BY-SA 3.0 | link to referred comment |
| Dec 18, 2013 at 9:59 | vote | accept | Pascal | ||
| Aug 5, 2012 at 4:22 | comment | added | user60909 | The description field is an extended property which is stored within the database. This can be used in a productive way, as an example: A previous environment I worked in used extended properties in conjunction with a CodeSmith generator product that would generate all of our stored procedures for read, inserts and deletes. We also utilized extended properties to build our data dictionaries. | |
| Jul 11, 2012 at 19:25 | comment | added | Pascal | The Description field in management studio is more of a hack... Not usable in any productive way. | |
| Jul 11, 2012 at 15:55 | history | edited | user7519 | CC BY-SA 3.0 | added 65 characters in body; deleted 5 characters in body |
| Jul 11, 2012 at 13:50 | comment | added | programmer | semantically correct naming system that avoids duplication, tautology and abbrevations THIS! Plus with SQL Server you can put descriptions of each field, which are tied to the table itself. | |
| Jul 11, 2012 at 7:51 | history | answered | user7519 | CC BY-SA 3.0 |