<a href="http://g.adspeed.net/ad.php?do=clk&zid=15220&wd=468&ht=60&pair=as" target="_blank"><img style="border:0px;" src="http://g.adspeed.net/ad.php?do=img&zid=15220&wd=468&ht=60&pair=as" alt="i" width="468" height="60"/></a>
Log in
::
Register
::
Not logged in
Home
Tags
Articles
Editorials
Stairways
Forums
Scripts
Videos
Blogs
QotD
Books
Ask SSC
SQL Jobs
Training
Authors
About us
Contact us
Newsletters
Write for us
<a href="http://g.adspeed.net/ad.php?do=clk&zid=15491&wd=120&ht=300&pair=as" target="_top"><img style="border:0px;" src="http://g.adspeed.net/ad.php?do=img&zid=15491&wd=120&ht=300&pair=as" alt="i" width="120" height="300"/></a>
Recent Posts
Recent Posts
Popular Topics
Popular Topics
Home
Search
Members
Calendar
Who's On
Home
»
Article Discussions
»
Article Discussions by Author
»
Discuss content posted by E Bond
»
Using Extended Properties To Keep Everyone...
14 posts, Page 2 of 2
««
1
2
Using Extended Properties To Keep Everyone Informed
Rate Topic
Display Mode
Topic Options
Author
Message
Rayven
Rayven
Posted Wednesday, December 01, 2010 1:56 AM
Mr or Mrs. 500
Group: General Forum Members
Last Login: Saturday, May 11, 2013 10:49 AM
Points: 575,
Visits: 344
Great article.
I've been enforcing extended properties on database objects now for two years and it has made an incredible difference.
Tables and procedures are now well documented.
SSRS reports are available to the developers to allow them to see the documentation, and with the aid of ApexSQLDOC I can produce a full data dictionary on request.
Because we hold databases for multiple companies, all with almost the same structure, additional extended properties help identify who the database belongs to, who is responsible for it and contact details.
On top of this some were developed to be used to help in code rollout. Whilst the databases are 90% identical code, occasionally a procedure strays due to a fast hotfix. A quick change to a custom "SYNC" property allows us to alert developers that the code is different to other databases, and to DBAs to review the code ASAP to recode it and bring it back into line. This, with the aid of a few custom scripts, has decreased the rollout time of new projects from hours to a matter of minutes.
It was difficult to persuade other people to use, but now that it is firmly embedded in the culture here it has proved worth its weight in gold. They are definitely an underused and extremely useful recourse.
---------------------------------------
It is by caffeine alone I set my mind in motion.
It is by the Beans of Java that thoughts acquire speed,
the hands acquire shaking, the shaking becomes a warning.
It is by caffeine alone I set my mind in motion.
Post #1028462
david_wendelken
david_wendelken
Posted Friday, December 03, 2010 4:38 PM
SSC-Enthusiastic
Group: General Forum Members
Last Login: Tuesday, July 05, 2011 1:06 PM
Points: 183,
Visits: 478
I use extended properties extensively in my own work as a developer.
I am loath to use them on other developer's work as a dba.
That's because when a script gets run that drops an oblect, the extended properties I added will be lost.
I'm not the only dba on the team, so I can't ensure that the extended properties are saved and restored after the item is created. Nor can I ensure that the developers add them to their source code.
Incidentally, extended properties are not included in the generated create scripts for all objects, i.e., views. That's particularly annoying to me as I like to include column definitions in the views for the data dictionary reports.
Post #1030202
maxvigil2004
maxvigil2004
Posted Saturday, December 04, 2010 3:52 AM
Forum Newbie
Group: General Forum Members
Last Login: Saturday, December 04, 2010 3:47 AM
Points: 1,
Visits: 0
Eric B-295769 (11/29/2010)
Comments posted to this topic are about the item
<A HREF="/articles/Central+Management+Server/71499/">Using Extended Properties To Keep Everyone Informed</A>
Hi,
I am facing the Erron 3709 while i open the Program
Post #1030253
Z1024
Z1024
Posted Wednesday, April 25, 2012 10:25 AM
Grasshopper
Group: General Forum Members
Last Login: Saturday, April 06, 2013 8:07 PM
Points: 12,
Visits: 57
My
web based SQL documentation tool - LiveDoco
addresses (to an extent) some of the concerns raised here:
1) It allows easy access (adding/editing/searching) to any extended properties, including the default MS_Description
2) It can export them to a SQL file that can be used to merge(add new/update existing) them into a db with similar/same structure. This SQL file could be saved somewhere in case something happens to the DB (and/or all your EPs in it).
It can do other things as well, but not directly related to this topic so please see
www.livedoco.com
for more information if interested.
www.livedoco.com - your Live SQL Server database documentation tool
Post #1290093
« Prev Topic
|
Next Topic »
14 posts, Page 2 of 2
««
1
2
Permissions
You
cannot
post new topics.
You
cannot
post topic replies.
You
cannot
post new polls.
You
cannot
post replies to polls.
You
cannot
edit your own topics.
You
cannot
delete your own topics.
You
cannot
edit other topics.
You
cannot
delete other topics.
You
cannot
edit your own posts.
You
cannot
edit other posts.
You
cannot
delete your own posts.
You
cannot
delete other posts.
You
cannot
post events.
You
cannot
edit your own events.
You
cannot
edit other events.
You
cannot
delete your own events.
You
cannot
delete other events.
You
cannot
send private messages.
You
cannot
send emails.
You
may
read topics.
You
cannot
rate topics.
You
cannot
vote within polls.
You
cannot
upload attachments.
You
may
download attachments.
You
cannot
post HTML code.
You
cannot
edit HTML code.
You
cannot
post IFCode.
You
cannot
post JavaScript.
You
cannot
post EmotIcons.
You
cannot
post or upload images.
Copyright © 2002-2013 Simple Talk Publishing. All Rights Reserved.
Privacy Policy.
Terms of Use.
Report Abuse.
