Pricing

pricing_icon_free_2x pricing_icon_yacht_2x pricing_icon_glossary_ferry_2x pricing_icon_glossary_cruise_liner_2x
features / tier
Free trial
Yacht
Ferry
Cruise Liner
MANTA Flow for all supported technologies and platforms
Unlimited instances, revisions and users
Native visualization
Limited metadata export from GUI
Available on premise or in the cloud
Conditional data lineage?
Unlimited export/import, including custom data flows, business metadata and additional properties
3rd party platform integrations
Customizations available? (paid separately)
Environment size? (number of scripts) 1,00010k 1,00010k 5,00050k 20,000200k
Price(annual in USD) Get free trial free $20,000/year20k $40,000/year40k $90,000/year90k
Extra script package(annual in USD) - 1,000 scripts for $3,000/year3k 2,000 scripts for $3,000/year3k 5,000 scripts for $3,000/year3k

Glossary

unlimited tier

We call it the “Fleet Tier” and it makes MANTA available without any script limit for your whole company in a specific region or on the whole planet. Shoot us an email on manta@getmanta.com to get your estimate.

pricing_icon_glossary_cruise_liner_2x

customizations available

We are offering MANTA Flow as a stand-alone product, yet in some rare cases it needs a few additional customizations to our customer’s needs. The typical case is when our customer has a specific single sign-on system and needs to have MANTA Flow included in it.

pricing_icon_glossary_yacht_2x
pricing_icon_glossary_ferry_2x
pricing_icon_glossary_cruise_liner_2x

conditional data lineage

Conditional data lineage is usually found in huge data warehouses that use very general physical models including several big tables like PARTY, BALANCE, ORDER and others. These tables contain data obtained from various source systems, and there are a lot of data marts and reports built on top of them. These tables make things difficult during the impact analysis because data lineage from almost every report goes through them to all sources making the result worthless.

Read more about it in a specific article dedicated to so-called “predicates”.

pricing_icon_glossary_free_2x
pricing_icon_glossary_yacht_2x
pricing_icon_glossary_ferry_2x
pricing_icon_glossary_cruise_liner_2x

environment size

For the purpose of pricing MANTA, “scripts” are all unique code elements such as stored procedures, views, functions, ad-hoc statements, etc. and ETL session instances. MANTA Flow counts all scripts for which metadata is stored in its repository and/or scripts analyzed in the previous 30 days.

Teradata – MANTA Flow supports data dictionary, SQL, BTEQ, stored procedures, macros, TPT, database query log.

How to count your number of scripts?

Views, macros, stored procedures and any SQL, BTEQ or TPT scripts count as “scripts”. BTEQ and TPT scripts should be counted as number of BTEQ and TPT files on filesystem. And use this command to count in-database objects:

SELECT d.DatabaseName, t.TableKind, count(1)
FROM dbc.TVM as t JOIN dbc.DBase as d on t.DatabaseId = d.DatabaseId
WHERE t.TableKind in (‘V’,’M’,’P’)
GROUP BY d.DatabaseName, t.TableKind
;

Informatica – MANTA Flow supports workflows, mappings, sessions, SQL overrides, repository, parameter files.

How to count your number of scripts?

PowerCenter session instances count as “scripts”. Indicative session count from Informatica repository:

SELECT SUBJECT_AREA, COUNT(1) FROM INFA.REP_SESSION_INSTANCES GROUP BY SUBJECT_AREA;

Oracle – MANTA Flow supports data dictionary, SQL, PL/SQL, stored procedures, packages, functions, triggers.

How to count your number of scripts?

Procedures, packages, triggers, functions, views, types and any SQL or PL/SQL scripts count as “scripts”. And this is the command to count in-database objects:

select owner, count(1)
from dba_objects
where object_name not like ‘SYS_PLSQL_%’
and (
(
object_type in (‘PROCEDURE’,’PACKAGE BODY’,’TRIGGER’,’VIEW’,’FUNCTION’,’TYPE BODY’)
and status = ‘VALID’
) or (
object_type = ‘MATERIALIZED VIEW’
)
)
group by owner;

Microsoft SQL Server – MANTA Flow supports Microsoft PDW, Azure SQL Database and Azure SQL Data Warehouse. Among those it supports data dictionary, SQL, T-SQL, stored procedures, functions, triggers, packages.

How to count your number of scripts?

Procedures, triggers, functions, views, and any SQL or T-SQL scripts count as “scripts”. This the command to count global objects (run the query once per each included SQL Server instance):

select count(1) from sys.server_triggers WHERE type = ‘TR’

And this is the command to count database-bound objects (run the query in every included database):

select
(select count(1) from INFORMATION_SCHEMA.ROUTINES where ROUTINE_TYPE in (‘PROCEDURE’, ‘FUNCTION’)) +
(select count(1) from INFORMATION_SCHEMA.VIEWS) +
(select count(1) from sys.triggers WHERE type = ‘TR’)

In Microsoft SSIS (Server Integration Services) are tasks count as scripts. To count the number of tasks, unzip all project files (if using project deployment), find all package (*.dtsx) files and count the sum of occurrences of “</DTS:Executable>” inside these files, minus 1 for each package file.

SAP ASE (Sybase) – MANTA Flow supports data dictionary, SQL, T-SQL, stored procedures, functions, triggers, packages. Please note that we do not support SAP IQ yet.

How to count your number of scripts?

Procedures, triggers, functions, views, and any SQL or T-SQL scripts count as “scripts”. This command can be used to count database-bound objects (run the query in every included database):

select count(1) from sysobjects WHERE type in (‘V’, ‘P’, ‘TR’)

Hive – MANTA Flow supports data dictionary, HiveQL.

How to count your number of scripts?

Views and any SQL or Hive QL scripts count as “scripts”. To list views in Hive (2.3.0+):

SHOW VIEWS [in/from <dbName>]

To count views directly in underlying Metastore database:

select count(1) from tbls where tbl_type = ‘VIRTUAL_VIEW’

IBM Netezza – MANTA Flow supports NZPLSQL scripts, stored procedures and more from IBM Netezza.

How to count your number of scripts?

Procedures, views and any SQL or NZPLSQL scripts count as “scripts”. This it the command to count in-database objects (run the query in every included database):

select (
(select count(distinct procedure) from _v_procedure where UPPER(OBJTYPE) = ‘PROCEDURE’ and BUILTIN = false) +
(select count(1) from _v_view where UPPER(OBJTYPE) in (‘VIEW’, ‘MATERIALIZED VIEW’))
)

IBM DB2 – MANTA Flow supports data dictionary, scripts, stored procedures, SQL, modules, functions, triggers, also support for Oracle compatibility mode.

How to count your number of scripts?

Procedures, functions (stand-alone as well as module- and type-bound methods), packages, triggers, views and any SQL or PL/SQL scripts count as “scripts”. This is the command to count in-database objects:

values (
(select count(1) from SYSCAT.ROUTINES where ORIGIN <> ‘S’ and OWNERTYPE <> ‘S’) +
(select count(1) from SYSCAT.TRIGGERS where OWNERTYPE <> ‘S’) +
(select count(1) from SYSCAT.TABLES where TYPE IN (‘V’, ‘W’) AND OWNERTYPE <> ‘S’) +
(select count(1) from SYSCAT.MODULES where OWNERTYPE <> ‘S’ and MODULETYPE = ‘P’)
)

 

 

 

We cherish your privacy.

By using this site, you agree with using our cookies.