Hi

 

Just to note that information about dependencies between database objects, including Views, is stored in the database itself e.g. that View A references table B., which references table C.

 

This information can be easily accessed in SQL Server Management Studio (and similar is available in SQL Developer/TOAD etc if you’re running on Oracle) via right-clicking the name of a View (or Table) in the Object Explorer, and selecting ‘View Dependencies’. Check the appropriate radio button to see either ‘Objects that depend upon [your View name]’ or ‘Objects on which [your View name] depends’.

 

I think commenting Views, in-line, is good for capturing detailed information about logic and rules etc.

 

Best wishes

Jon

 

Jon Thristan MBCS | Project Consultant

[log in to unmask] | +44 20 7993 8402

GallerySystems | www.gallerysystems.com

 

----

 

 

Join us in L.A. this December for

Collective Imagination 2017

 

The International TMS Users Conference

Workshops:  December 4 – 5, 2017

Conference: December 6 – 8, 2017

 

Get more details here.

 

 

 

Dear colleagues

 

Are any of you creating documentation of your database views within the views themselves – by which I mean not just commented code, but standardised descriptions of the view, any interdependencies, etc. ? If so, do you have an established format you’d be willing to share?

 

Between GS views and our own, we have over 600 views at the National Gallery, and before we start creating any more, I’d like to make it easier for us to see in future why we created them, what they depend on, what depends upon them, etc.

 

With thanks and best wishes

 

Rupert

 

Rupert Shepherd, PhD FSA

Collection Information Manager

[log in to unmask]

Tel: +44 (0)20 7747 5921

 

To unsubscribe, send an email to [log in to unmask] with the following commands in the body of the email:

signoff TMSUSERS

// eoj

You will receive a confirmation that your subscription has been removed.