cross-database dependencies

• 
  Hi Rob,
  
  Thanks for your post.
  
  Can I confirm whereabouts you are looking for this information? The release notes for 1.3 ar ein the below link:
  
  http://www.red-gate.com/supportcenter/C ... SQLDoc.htm
  
  Either way, the tool will pull in external dependencies, i.e. where a sproc is retrieving data from a table in a different DB. This is something that the tool will document, but it will not implement it for you. Further information on setting up linked servers is available from the below link:
  
  http://msdn.microsoft.com/en-us/library ... 80%29.aspx
  
  HTH!
  
  Pete

  peter.peart October 27, 2010 09:14

  - 0 +
• 
  Pete,
  
  I found the information at the bottom of the following page (Version 1.3 release notes, I think):
  http://www.red-gate.com/messageboard/viewtopic.php?p=26487#26487.
  
  My question is not with linked servers or stored procs, but the ability to note that, for example, a key/code field in a table in one database is actually a foreign key to a lookup table that is in a different database. I don't believe there is a way to denote this in the SQL schema itself; I was hoping (when I saw the 1.3 release notes) that there could be a way for me to note this in the documentation.
  
  I suppose I could just put it into the extended_property Description field as part of the field documentation, but I was hoping for something a little more sophisticated.

  RobSchripsema October 27, 2010 18:09

  - 0 +
• 
  Hi Rob,
  
  You could note this by altering the extended properties on objects within the DB if you wanted, and this would be classed as a schema update as you would be altering the MS_Description of an object.
  
  Would that suit your needs?
  
  Pete

  peter.peart November 05, 2010 13:16

  - 0 +

Add comment

Please sign in to leave a comment.