Page tree
Skip to end of metadata
Go to start of metadata
Description

For a TSQL extraction where indexes have the exact same name, only one index is extracted.  The indexed table in each case is different.

Here's an example of the situation from a TSQL query screen:


 

Observed in CAST AIP

  

Release
Yes/No
8.2.x(tick)
8.1.x (tick)
8.0.x (tick)
7.3.x (tick)
Observed on RDBMS
RDBMS
Yes/No
Oracle Server (tick)
Microsoft SQL Server (tick)
CSS2 (tick)
Step by Step Scenario

Below is the step-by-step scenario leading to the problem:

  1. Extract database with  indexes with the same name.
  2. Deliver code.
  3. Perform analysis and snapshot of delivered code.
  4. Notice that indexes are missing in the analysis.
Impact of the Problem

The impact of the problem on the analysis or the dashboard is:

Missing indexes which can affect quality rules such as Avoid SQL queries on XXL tables that no index can support.

Action Plan

To fix the problem, proceed as follows:

  1. Download this file:  NewTSQLCASTDatabase.config
  2. With the TSQL standalone extractor GUI, go to the options tab and for the Configuration file path parameter, navigate to the downloaded file.  Alternatively, for the standalone extractor command line, use the -config <downloaded_file_and_path> option in the command line to provide the value for the Configuration file path parameter
    1. If you do not have a standalone extractor,  contact CAST support for more information. 

This is planned to be fixed in CAST 8.0.4.

  

Notes/comments
Ticket # 5543
Related Pages

 

  • No labels