InstantForum.NET v2.9.0SQLServerCentralhttp://www.sqlservercentral.com/Forums/notifications@sqlservercentral.comTue, 18 Jun 2013 16:45:52 GMT20http://www.sqlservercentral.com/Forums/Topic1088449-1497-1.aspxVery informative series of articles. What would be helpful to me would be the ability to combine results from more than one database. We typically have a pair of databases for an application (data and code), and we have quite a few pairs. It would be nice if there could be a single instance of each stored procedure that could be executed against any database. Is there a way to do that?Mon, 16 May 2011 12:02:46 GMTxyzmelhttp://www.sqlservercentral.com/Forums/Topic1088449-1497-1.aspxHere is one more [url=http://pragmaticworks.com/Products/Business-Intelligence/BIDocumenter/Overview.aspx]Free Tool to document Sql Server[/url]Mon, 02 May 2011 11:49:14 GMTSSIS Guyhttp://www.sqlservercentral.com/Forums/Topic1088449-1497-1.aspxHi Jonsathan,You have good ideas there - cross-referencing columns with the same name and reusing repeatable descriptions. Thanks for sharing that.AdamSun, 10 Apr 2011 12:52:39 GMTAdam Aspinhttp://www.sqlservercentral.com/Forums/Topic1088449-1497-1.aspxThanks for the great series of articles. I started using the extended properties when I got a tool that would create database documentation based on those properties.I found that I had many columns with the same name and were really the same item in various tables. For example, many tables had the "AccountID" column, and all were copies of the same thing (primary key in the Account table, foreign key in all other tables). When writing the statement that creates the sp_addextendedproperty, I found it helpful to try to locate another field with the same name and use that as the default value. That allowed me to save a lot of retyping. Of course, I had to review each generated statement for accuracy and make changes as necessary, but it was better than having to look up what I created for the previous tables and retype or copy/paste every time. For my defaults, I used the most-frequently-used description for columns with the same name.Again, thanks for the thorough explanation and the helpful examples.Sun, 10 Apr 2011 12:27:33 GMTfahey.jonathanhttp://www.sqlservercentral.com/Forums/Topic1088449-1497-1.aspxThanks for the article. Great content.Tue, 05 Apr 2011 22:21:11 GMTSQLRNNRhttp://www.sqlservercentral.com/Forums/Topic1088449-1497-1.aspxThis free tool uses MS_Description as well...[url=http://www.DBGizmo.net]http://www.DBGizmo.net[/url]Tue, 05 Apr 2011 12:36:15 GMTWingenioushttp://www.sqlservercentral.com/Forums/Topic1088449-1497-1.aspxXDetails plugin uses MS_Description, as it is standard in SSMS.Tue, 05 Apr 2011 09:29:27 GMTVedran Kesegichttp://www.sqlservercentral.com/Forums/Topic1088449-1497-1.aspxHi Charles,I am using "Description" for a couple of reasons - firstly to show that you can classify metadata comments by your own categorisation types (I have used DataLineage, ToolTip as well) and secondly because I have noticed that views in SSMS use the MS_ prefix - and this way I can avoid MS-based data when outputting.I don't know if this is good or bad, approved or not - but it seems to work!Thanks for the feedback!AdamTue, 05 Apr 2011 09:12:48 GMTAdam Aspinhttp://www.sqlservercentral.com/Forums/Topic1088449-1497-1.aspxGreat article and series.I am curious though. You use "Description" and SSMS for columns uses "MS_Description". Is that because you are intending the article to be a teaching tool and want to avoid stepping on things?Tue, 05 Apr 2011 09:02:49 GMTCharles Kincaidhttp://www.sqlservercentral.com/Forums/Topic1088449-1497-1.aspxComments posted to this topic are about the item [B]<A HREF="/articles/Metadata/72610/">Industrial-strength database documentation using Extended Properties</A>[/B]Tue, 05 Apr 2011 00:01:03 GMTAdam Aspin