cross-database dependencies

Documents SQL Server 2005 and 2008 databases.

Moderators: JonathanWatts, David Atkinson, Michelle Taylor

cross-database dependencies

Postby RobSchripsema » Mon Oct 25, 2010 10:35 pm

I'm not a customer yet -- just working with my 14-day trial.

Question: the release notes (for 1.3) and the product sheet state that SQL Doc "Includes all cross-database dependencies". What exactly is this referring to? Is this something that can be created/documented within the SQLDoc tool, or is it something that is set up in the database(s) and SQLDoc documents it? If the latter, how does one set up such dependencies?
Rob Schripsema
RobSchripsema
 
Posts: 4
Joined: Thu Feb 11, 2010 9:34 pm
Location: USA, Washington state

Postby peter.peart » Wed Oct 27, 2010 2:14 pm

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
Red Gate Software Ltd
+44 (0)870 160 0037 ext. 8569
1 866 RED GATE ext. 8569
peter.peart
Site Admin
 
Posts: 362
Joined: Tue Sep 02, 2008 9:58 am
Location: Top floor, RG towers with the cool kids

Postby RobSchripsema » Wed Oct 27, 2010 11:09 pm

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.
Rob Schripsema
RobSchripsema
 
Posts: 4
Joined: Thu Feb 11, 2010 9:34 pm
Location: USA, Washington state

Postby peter.peart » Fri Nov 05, 2010 6:16 pm

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
Red Gate Software Ltd
+44 (0)870 160 0037 ext. 8569
1 866 RED GATE ext. 8569
peter.peart
Site Admin
 
Posts: 362
Joined: Tue Sep 02, 2008 9:58 am
Location: Top floor, RG towers with the cool kids


Return to SQL Doc 2

Who is online

Users browsing this forum: No registered users and 0 guests