Pricing for DSS
Documentation: Pricing for DSS
Pricing Plan
This section briefly describes the pricing plan for Data Source Solutions DSS and explains the most recent pricing updates.
Our pricing model is based on consumption (usage). You are charged based on the amount of data replicated or consumed by a target (destination). Data Source Solutions calculates your consumption (usage) based on the number of Monthly Active Rows (MAR) across all source and target locations within your DSS Hub System(s). MAR is the number of distinct primary keys synced or replicated from a source location to a target location in a given calendar month. For more information, see our pricing documentation.
Data Source Solutions offers a single pricing plan for DSS - Business Critical. In this plan, Data Source Solutions automatically manages consumption tracking and license renewal.
To explore current pricing and available features, see the Data Source Solutions Pricing page.
Pricing Plan Updates
Data Source Solutions has made the following pricing updates:
- Introduced an enhanced re-sync detection mechanism that more precisely determines data changes. For more information, see Improved Re-sync Detection.
- Moved away from account-level tiering to channel-level usage tiers. The cost of DSS per monthly active row decreases for a single channel as your usage grows for that particular channel. Previously, usage was calculated on an account level.
- Introduced discounts for annual contracts based on commitment levels. Once you have upgraded your DSS Hub and Agent to version 6.2.0/14 or newer and we have one month of usage data, see the Pricing Estimator for an estimate of your annual discount. The discount applies once you renew your contract.
- Deprecated the Private Deployment pricing plan. All DSS accounts on the Private Deployment plan must transition to the Business Critical or other plans upon contract renewal.
Improved Re-sync Detection
The enhanced re-sync detection mechanism more accurately identifies data changes, eliminating the need for free refreshes within the five-day troubleshooting window. You are charged only for changed rows, regardless of when the change occurs.
To enable re-sync detection on your account:
- Renew your annual contract
- Upgrade your DSS Hub and DSS Agent to the version applicable to your current release:
- If you are using 6.1.0, upgrade to 6.1.0/76 or newer.
- If you are using 6.2.0, upgrade to 6.2.0/14 or newer.
- If you are using 6.2.5, upgrade to 6.2.5/5 or newer.
You must complete both actions to benefit from re-sync detection.
You can transition to the updated pricing without upgrading your Hub and Agent, but the improved re-sync detection mechanism won't be enabled. Without re-sync detection, you will have to rely on the five-day troubleshooting window for free refreshes.
If you have an active contract, you can upgrade your DSS Hub and Agent without transitioning to the updated pricing. After the upgrade, once Data Source Solutions has collected one month of usage data, our Pricing Estimator shows your estimated usage with re-sync detection, helping you make an informed renewal decision.
Re-sync detection stores up to 50 MB of sample data per replicated table on the system hosting the DSS Hub System. Samples are stored in the DSS_CONFIG/metering directory for every channel containing the table, per source/target location pair.
Re-sync detection is not available for DSS when using SAP HANA as the Source.
Business Critical
The Business Critical plan allows DSS to be deployed on-premise. In this plan, the DSS Hub System must be registered with a Data Source Solutions account and connected to the Data Source Solutions server to automatically send the consumption data and receive licenses. Once registered, DSS automatically transmits encrypted consumption data to Data Source Solutions, where it is securely stored on AWS S3.
If the Data Source Solutions account registration is deleted from a hub system, DSS immediately stops sending consumption data to Data Source Solutions, and the automatic license renewal stops (the license expires after seven days).
Each month, your consumption/usage is calculated based on the number of MAR across all source (connector) and target (destination) locations in your account. The consumption data (metadata) used to calculate MAR for your DSS Hub System(s) is sent to Data Source Solutions in two files:
DSS sends the MAR Data file to Data Source Solutions hourly for usage tracking, and Data Source Solutions returns a new seven-day license key each day. In addition, DSS sends the Hub Snapshot file every 30 days.
The MAR data or snapshot file sent to Data Source Solutions does not contain any data from replicated tables or any confidential or secret data.
Prerequisites
For the Business Critical plan, you must:
- Enable outbound access from the web browser that you will use to register the DSS Hub System to the IP address 35.236.237.87 (datasourcesolutions.ai).
- Enable outbound access from the system running the DSS Hub Server to the following IP addresses on port 443 (required for sending consumption data to the Data Source Solutions server):
- 34.110.137.135
- 34.120.211.189
- Register your DSS Hub System. You must create a Data Source Solutions account or log in to datasourcesolutions.ai with an account Administrator role.
- If you are using proxy server to connect DSS Hub System with Data Source Solutions, then ensure to configure the proxy server setup.
If you have multiple DSS Hub Systems, you must register each hub system individually.
MAR Data
The MAR data that DSS sends to Data Source Solutions contains information such as Hub Name, Hub ID, Hub Description, Hub Server URL, Channel Name, Location Name, Location Description, Location Type, Table Name, Base Name, Refresh Events (including the timestamp and metadata), hashes of primary keys changed, and HLL records for Integrate and Refresh jobs.
| Column in MAR File | Description |
|---|---|
| month | Month and year for which the MAR data is applicable. |
| hub_name | Name of the hub. |
| hub_id | Unique identifier of the DSS Hub System. |
| chn_name | Name of the channel. |
| src_loc_name | Name of the source location. |
| tgt_loc_name | Name of the target location. |
| mar | Total sum of MAR for the month. |
| mar_daily | List of incremental MAR values per day. |
| src_loc_type | Type (e.g. Oracle, SQL Server) of source location. |
| tgt_loc_type | Type (e.g. Oracle, SQL Server) of target location. |
| table_count_estimate | Estimate of the number of tables seen per source-target connection in a channel. The estimate has the same error rate as regular MAR, so usually +- 2%. |
| integ_mar_signature | Serialized form of the raw internal HLL structure which is used to track MAR data. |
| refr_mar_signature | Serialized form of the raw internal HLL structure which is used to track MAR data. |
Storage Requirements for MAR
DSS stores MAR data locally on the Hub machine in hourly buckets per table before sending it to Data Source Solutions. These files use a data structure called HyperLogLog (HLL) to track MAR. DSS uses hash values from primary keys to update these structures, which are retained for up to one month.
Original primary keys cannot be retrieved from the HLL data structure. DSS does not store the primary keys directly, but instead uses their hashes to update this structure. The hashes are irreversible and can not be retrieved.
Each data structure is approximately 2 KB. The amount of data stored daily is 24 (hours) * 2 (KB) * number of active tables, so the disk space needed per day is 48 (KB) * number of active tables. The total storage required for MAR data depends on the number of active tables being replicated.
We recommend allocating about a week's worth of storage capacity on the DSS Hub machine for storing MAR data. Typically, only one or two days of data is stored because DSS automatically purges MAR data one day after transmission. If required, you can disable automatic purging using the repository property Metering_Purge_Frequency.
Viewing MAR Data
To view the hourly MAR data sent to Data Source Solutions:
-
Execute the dsslicense command in the CLI:
dsslicense -m <em>marfilename</em> -B now-1h -
Open the file in a text editor to view the data.
Hub Snapshot
The hub snapshot includes information about the system configuration or usage such as Channel definitions, Events, Statistics, and Job state.
DSS encrypts and sends a usage snapshot for each hub to Data Source Solutions every 30 days. Before transmission, the snapshot file is temporarily stored on the disk of the hub machine. DSS automatically purges it a day after it is sent to Data Source Solutions.
The hub snapshot file includes:
- one week of events
- one week of statistics
- channel definitions
- job state
The snapshot does not contain log files, history, or transaction files.
To manually generate a hub snapshot (in ZIP file format), use the dsssnapshotsave command in the CLI:
dsssnapshotsave -r "Usage snapshot for account_id <em>my_account_id</em>" -e now-1w -s now-1w -l none -t none -V redact <em>hub_name</em> <em>snapshot_filename</em>.zip