|
|
|
SSC Journeyman
      
Group: General Forum Members
Last Login: Today @ 9:52 AM
Points: 80,
Visits: 847
|
|
|
|
|
|
Hall of Fame
       
Group: General Forum Members
Last Login: Friday, March 15, 2013 2:43 PM
Points: 3,924,
Visits: 1,554
|
|
Great article, Adam. I will save it in my briefcase for future reference.
SQL DBA.
|
|
|
|
|
SSC Journeyman
      
Group: General Forum Members
Last Login: Today @ 9:52 AM
Points: 80,
Visits: 847
|
|
Thanks Sanjay, I hope that the series proves useful.
Adam
|
|
|
|
|
SSC-Addicted
      
Group: General Forum Members
Last Login: Friday, November 09, 2012 2:48 PM
Points: 493,
Visits: 636
|
|
Thanks for the article Adam. It is well thought out, and well presented and written. I have used a exists then update or add methodology. I've only ever added extended properties for databases, tables, and stored procedures because I encourage naming to be as self explanatory as possible. However, if the database schema was controlled by a third party, and/or the column names and paramter names were criptic then I could definitely see benefit to describing them with extended properties. One of the potential uses of extended properties is the ability to build a data dictionary which I am hoping you will have a script for in the next article of the series. I have a decent script for doing this in case you don't already have one built. It's not in my coding style so I didn't write it, and regretfully I don't have a comment at the top to give the author proper credit.
|
|
|
|
|
SSC Journeyman
      
Group: General Forum Members
Last Login: Today @ 9:52 AM
Points: 80,
Visits: 847
|
|
Hi Toby, The next (and final) article does indeed contain scripts to document a data dictionary, using the database metadata - let me know if you like it once it appears. Regards, Adam
|
|
|
|