EDW License Deduction Criteria

This topic provides information about the license deduction criteria used in LeapLogic to transform your legacy EDW workloads to a modern cloud platform.

License quota is deducted for units when converting EDW workloads such as Teradata, Oracle, etc., to target equivalents, where unit refers to query in the workload. The license deduction logic is determined based on File similarity and Complexity. Here is a detailed explanation of each criterion:

File similarity

File similarity checks whether the source file is related or similar to an already executed file. A higher file similarity value indicates that you already executed a similar file. The license quota deduction depends on whether the file similarity value falls below the predefined threshold. Specifically, if the file similarity value is below the threshold, then the system will deduct the license quota. Conversely, if the file similarity value exceeds the threshold, it won’t incur any license quota deduction, indicating that the file has been processed before. For instance,

If the file similarity value is 70% (below the threshold) and the threshold is 80%, then the system deducts the unit quota.
If the file similarity value is 92% (above the threshold) and the threshold is 80%, then the system will not deduct unit quota.

Complexity

One of the criteria to determine the license quota deduction is based on the complexity of each unit. The unit complexity is categorized into TRIVIAL, SIMPLE, MEDIUM, COMPLEX, V. COMPLEX, and V.V COMPLEX. The complexity weightage for the deductible unit quota is outlined as follows:

If the unit complexity is TRIVIAL or SIMPLE, the deductible unit quota is 1.
If the unit complexity is MEDIUM, the deductible unit quota is 3.
If the unit complexity is COMPLEX, V. COMPLEX, or V.V COMPLEX, the deductible unit quota is 5.

For instance, consider the example provided in the image below for the file TD_TestBed_DML.sql. This file contains a total of 86 units, out of which 85 are successfully transformed. Among these successfully transformed units:

82 units are categorized as Simple complexity with a weightage of 1. Consequently, the deductible unit quota for these units is 82.
2 units are categorized as Medium complexity with a weightage of 3. Consequently, the deductible unit quota for these units is 6.
1 unit is categorized as having Complex complexity with a weightage of 5. Consequently, the deductible unit quota for these units is 5.

So, the total deductible unit quota for TD_TestBed_DML.sql file is 93.

The Summary sheet (refer above image) in Transformation_Report.xlsx file showcases detailed information about the license deductible quota.

File Name: Displays the name of the file.
Auto Conversion Percentage: Displays the auto-conversion percentage of scripts.
File Similarity: Indicates whether the file is similar to the already executed file. If the value is Yes, then the file is similar to an already executed file else No. If the file is similar to the already executed file, then the Deducted Script Quota and Deducted Unit Quota will be zero and will not deduct any quota.
Script Complexity: Displays the complexity of each file.
Total Blocks: Displays the total number of blocks.
Success Blocks: Displays the number of successfully transformed blocks.
Total Units: Displays the total number of units.
Success Units: Displays the number of successfully transformed units.
Deductible Unit Quota: Displays the unit quota that needs to be deducted based on the complexity of each successfully transformed unit.
Deducted Unit Quota: Displays the actual unit quota deducted from license.

The Query Summary sheet provides information about the queries along with the count of total, auto-converted, and manually corrected queries.

Statement: Displays the statement types.
Total Count: Displays the number of queries for each statement type.
Auto-Converted Count: Displays the number of queries that are automatically converted for each statement type.
Manually Converted Count: Displays the number of queries that require manual intervention for each statement type.

The Transformation Report sheet lists all the queries along with its type, auto generated query, status, complexity and more.

File Name: Displays the name of the file.
Procedure Name: Displays the name of the procedure.
Procedure Parameters: Displays the number of parameters in each procedure.
Original Query: Displays the original query.
Query Type: Displays the query type.
Auto Generated Query: Displays the auto-generated query.
Status: Indicates the conversion status of each query. If the value is SUCCESS the query is converted successfully, else FAILED.
Validation Status: Displays the status of query validation.
Complexity: Displays the query complexity.
Deductible Quota: Displays the quota that needs to be deducted based on the complexity of each successfully transformed query.
Deducted Quota: Displays the actual unit quota deducted from the license.
UDF Used: Displays the user-defined functions used in each query.
Script Line: Displays the number of lines present in each query/ procedure.
Script Column: Displays the number of columns that are used in the query.
Error Message: Shows a brief message of auto-conversion or query validation failure.
Error Details: Shows a detailed message of auto-conversion or query validation failure.
Manually Corrected: Indicates whether the query needs manual intervention.
Manual Query: Displays manually updated queries.
Transformation Discrepancy: This indicates whether there is a difference between the source and target query constructs. If the value is Yes, it signifies that there is a discrepancy between the source and target query constructs. For instance, if the source query has one join condition, but the target or converted query has two which highlights a discrepancy. Conversely, if the value is No, it signifies that there is no difference in the query construct between the source and target queries.
Changed Model Applied: Provides information on any applied changes to the model. It is a mapping between source and target tables as well as columns along with a definition of the mapping condition such as Inner Join, etc.
Query Construct: Displays the number of source and target query constructs such as Joins, sub-queries, and conditions.

When you try to convert units that exceed the available license quota, those within the quota will successfully convert. However, any additional units beyond the quota will fail to transform and display an error message indicating “License quota insufficient.”

Let us look at the consolidated license deduction logic.

EDW Script Name	Unit	File Similarity (File Similarity Threshold value = 80%)	Complexity	Number of successfully transformed units	Quota Deduction (Count of Successful Conversions)	Reason
Script 1	Query	70% (below threshold value)	1 complex query, 2 medium queries, 6 simple queries	9 queries	17	Deduct 17 unit quotas as the file similarity is below the threshold and the complexity of the 1 query is complex with a weightage of 5, 2 queries are medium with a weightage of 3, and 6 queries are simple with a weightage of 1
Script 2	Query	91.42% (above threshold value)	2 complex query, 5 medium queries, 11 simple queries	18 queries	0	No quota will be deducted as the file similarity is above the threshold