Dependencies And Schema

From SQLBWiki

The Batch Analysis produces both a "Dependency File" which contains inter-objects cross reference information and a "Schema File" which contains foreign keys information. You can use these files in your own programs if you wish, the structure is quite simple. You can also exploits these files interactively directly in SQLBrowser:

• In the "Dependencies" Window: If dependencies are available, clicking on an object will highlight the callers and dependent objects. For convenience, you may as well double click on a dependent node to get it analyzed:

• In the editor: If the schema is available, you can use a rudimentary completion mechanism:

[edit] How to setup access to the dependencies and schema files

• Understand how batch analysis works. Please refer to Batch Analysis. Setup the output directory as you see fit.
• Make sure that regular and centralized batch analysis are performed. We advise that batch analysis are organized as windows task and ran on a contingency or development server.
• SQLBrowser needs to know the output directory of the batch analysis to pick up the dependency and schema files. You need to spcify this location in the General Preferences, in the "Input Directory or URL" text box. There are two ways of specifiying this location:
  • By a file name, if the output directory is accessible from the machine where SQLBrowser is running. e.g.: D:/temp/SQLBrowserOutputDir
  • By a URL, if the output directory is accessible through a web server running on a different machine e.g.: http://remotehost/remotedir
• SQLBrowser will attempt to open the files named sqlbhtml/<ServerName>/dependencies.txt or sqlbhtml/<ServerName>/schema.xml, rooted from the input directory or URL
• If successful, this will be the dependency file for the server opened
• If not, SQLBrowser will attempt to open dependencies.txt or schema.xml rooted from the "Default Input Directory or URL" location. This is useful to put a dependency or a schema file common to different servers who may differ in content but whose programs are the same.