Currently 3 customizable option settings are available for Dependency Analysis. Two for File Analysis and one for Database analysis:
For information about the available buttons in the Wizard step above click here.
|
FAQ: Will my Options settings be saved?
Options and settings are specific to just one single project, so each project has its own set of options and settings. When you create a new project, the default settings for a project will be used.
|
Ignore Trigger Reference to Parent Table: The triggers are unique in that they reference the table they are created on but they are not really an external reference. Dropping the table will automatically drop the triggers created on it, so this option allows the user to ignore the triggers for the purpose of tracking a table's references and eliminating trigger references as true parent references. By default this option is disabled.
Search for SQL Objects is Case Sensitive: Checking this option instructs ApexSQL Clean to search for dependencies in a case-sensitive manner.
|
FAQ: I would like my searches for objects in source code files to be case sensitive. How can I do that?
ApexSQL Clean features several options that affect the way searches can be performed. In the project wizard dialog go to search options page and check/un-check the appropriate search settings you would like to be performed.
Tech Tip: This only affects search within client application source code files, searches within SQL Server are NOT affected by these settings.
|
Example:
We have a table named "Address" in our database. Searching through our code files we found three files with references to that object.
When viewing the file (double click on its name) we distinctly see matching object name:
After that we made several changes to our code, including changing upper case to lowercase in "Address", making it now "address" in one of our source files.
Searching for files with same settings, now shows only two matching files:
Remembering we had more files, we disabled the option that checks case sensitive and again we found three files matching. A quick view of the code shows that ApexSQL Clean has made a match regardless of the case we used.
Match Whole Word Only: Matches whole words only when creating dependency relationships and ignores matches on partial word fragments. By default this option is enabled.
Example:
We have a table named "Contact" in our database. In one of our source tables we have a class named "ContactNew" specially created for other our table "ContactNew".
If we disable the Match Whole Word Only option to match the whole word, we get a successful match as it's shown in the picture above and in the figure below:
If we include the Match Whole Word Only option, no reference to that file is found:
Depending of how this option is set, ApexSQL Clean will either find the dependencies or not.
Copyright © 2008 ApexSQL LLC. All Rights Reserved.
