Page tree

Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

When an Add Linked Objects operation retrieves objects that are currently not in the Object Browser window and you add such an object to the graph without adding its project to the browser (Cancel in the Add Project message box), selecting the Show Full Name check-box will cause all objects to disappear from the Preview list in the Add Linked Objects dialog except for the selected object.

Impact Analysis

FGIA only (Oracle)

...

Column Level

...

Impact Analysis

...

The FGIA ignores all dynamically constructed queries. For example:On a function f1 containing the following code:

Code Block
nopaneltrue
columnName varchar2(32) := 'C';open myCursor for 'select ' || columnName || ' from theTable';

The FGIA on C will not return the function f1()

...

FGIA (Oracle) & CLIA (SQL-Server)

  • Sometimes objects with a different impact level (IMPLEVL) are drawn on the same line (level) on the view. This can occur for an object with two impact levels (e.g. 1 and 2); in this case the object is drawn on the line for level 1. This can also occur when a parameter is impacted; the impact analysis engine counts an impact on a parameter as a separate level, but Enlighten does not display the parameter as an object by itself and the object containing the parameter is drawn on the "wrong" level.
  • Carrying out a CLIA/FGIA on light imported tables may not return accurate results.
  • Neither the CLIA (when using a Microsoft SQL Server) nor the FGIA (when using an Oracle Server) takes into account indexes:

No CLIA/FGIA results will be issued about indexes containing a modified column (whether this column is a table column or a view column). In addition, in scripte of procedures, triggers, functions or views, no CLIA results will be issued about names of indexes containing a modified column. For example, on a Microsoft SQL Server, where the CLIA job is the simulation of the removal of "T.C1", no impact will be reported about I or P, despite the fact that in this latter case the index hint « WITH( INDEX( I ) ) » becomes obsolete.

...

The functionality known in previous releases of CAST AIP as the Column Level Impact Analysis (CLIA) for participating Microsoft SQL Server or Sybase ASE databases is no longer available (and has not been since CAST AIP 7.2.x). Since the SQL analyzer generated objects for columns, you can use the following workaround to obtain CLIA-like results:

  • For Column Level Impact Analysis when performing a column modification/deletion: you can put the selected column into a CAST Enlighten view and use the "show linked objects" function.
  • For Column Level Impact Analysis when performing a column addition: you can put the table to which you want to add the column into a CAST Enlighten view and use the "show linked objects" function.

Fine Grain Impact Analysis

The functionality known in previous releases of CAST AIP as the Fine Grain Impact Analysis (FGIA) for participating Oracle schemas is no longer available (and has not been since CAST AIP 7.2.x). There is no workaround for this feature.

Info
Note that this feature has never been available in CAST Enlighten when hosting your CAST schemas on a CAST Storage Service.

Object Browser

  • When an object is shared by multiple analyses and appears more than once in the Object Browser window, the Find in Browser feature finds only one object.
  • Enlighten configures itself at startup to support all programming languages for which objects are present in the Knowledge Base. If you analyze a language not yet present while Enlighten is running, you cannot display the resulting objects unless you close and reopen a new view. In some cases it is even necessary to restart Enlighten.
  • Selecting the option Display Parameters in the Object Browser configuration tab (Tools > Options > Browser) may cause the Object Browser window to take some time to refresh - particularly if you have a large Knowledge Base that contains a lot of information.
  • The number of projects you can load into the Object Browser is limited to 50 projects. Enlighten can close unexpectedly if you exceed this limit. 50 projects is an approximate value. The exact limit depends on the number of objects and their hierarchy structure inside the projects. You load projects into the Object Browser either during Initial Scope Selection, when adding linked objects to the view and the objects' project is not loaded already, or through the command Load Project into Object Browser.
  • After analyzing a new .NET job with two csproj - Project1 and Project2 - and Project2 depends on Project1, and the analysis order was Project2 before Project1, then the Namespaces folder in the Object Browser under Project2 contains both, source code objects and external objects.

...