Using the Sisense ElastiCube connector (EC2EC) to retire a data source while reusing existing ElastiCube data [Linux]
Introduction:
Retiring a data source but need to keep its data live in Sisense? Use the ElastiCube connector (EC2EC) to make your existing cube the source for new models — reuse finalized data across new cubes without re-importing from the original system.
Step-by-step guide:
Scenario: The original data source (database, warehouse, or file source) is being decommissioned. The data already loaded into your existing ElastiCube is final — no further ingestion is required — and you want to keep using that data as the basis for one or more new models.
The ElastiCube connector, commonly called EC2EC (ElastiCube-to-ElastiCube), lets one ElastiCube read from another already-built ElastiCube as if it were a normal data source. This means the built cube becomes your system of record, and the original source can be safely retired.
Confirm the source cube is built and available.
The cube you want to reuse must be in a built state and running. EC2EC reads from a built ElastiCube, so if the cube is stopped or unbuilt, the tables will not be selectable.
Create (or open) the new ElastiCube that will consume the data.
Go to Data → + ElastiCube (or open the existing target model).
Add a new data connection and choose the Sisense ElastiCube connector.
In + Data → connector list, select Sisense ElastiCube (this is the EC2EC connector).
Authenticate.
Provide the credentials the connector requires. Use a service/shared account rather than a personal one — EC2EC connections break if the underlying user is deactivated (see the referenced password/off-boarding article).
Select the source ElastiCube and import the required tables.
Pick the built cube from step 1, then select the tables/columns you need in the new model.
Model and build the new ElastiCube.
Add relationships, custom columns, or filters as needed, then build. The new cube now holds its own copy of the data sourced from the original cube.Repeat for additional cubes if needed.
The same source cube can feed multiple downstream models — build each new cube from the EC2EC connection.Decommission the original data source.
Once every dependent cube builds successfully from the EC2EC source, the original external data source is no longer referenced and can be retired.
Configuration note: If you use the Stop when idle option in Data Groups, be aware it interacts with EC2EC. A source cube that has spun down when idle will not be reachable by dependent cubes at build time. Keep the source cube's Data Group configured so it is available whenever downstream builds run (see the referenced Data Group article for the exact configuration).
Alternative worth knowing: If you do not need an ongoing, queryable source — just a one-time move — exporting the cube as an .sdata file also lets you rebuild the ElastiCube in another environment without re-importing from the original source, because .sdata contains both the model schema and the data. EC2EC is the better fit when you want a living source cube that can feed multiple new models over time; .sdata is the better fit for a static snapshot/migration.
Ps: It is important to make sure that the farm folder of your source cube should never be deleted.
Conclusion:
When a data source is being decommissioned but its data is final, you do not have to keep the original source alive or re-ingest anything. Point new ElastiCubes at your existing built cube using the Sisense ElastiCube connector (EC2EC), and that cube becomes the reusable source of record. Keep the source cube built and available (mind the "Stop when idle" Data Group setting) and use durable credentials so the connection survives personnel changes. For one-off migrations without an ongoing source, an .sdata export is a simpler alternative.
References / related content
Data Group configuration for EC2EC connections [Linux] — https://community.sisense.com/forum/troubleshooting-39/topic/data-group-configuration-for-ec2ec-connections-linux-4306/
Resolving Issues with Updating EC2EC Passwords in Elasticube Connections — https://community.sisense.com/forum/troubleshooting-39/topic/resolving-issues-with-updating-ec2ec-passwords-in-elasticube-connections-4156/
How to export .ecdata/.sdata and .dash files — https://community.sisense.com/forum/knowledge-base-docs-7/topic/how-to-export-ecdatasdata-and-dash-files-5406/
Disclaimer: This post outlines a potential custom workaround for a specific use case or provides instructions regarding a specific task. The solution may not work in all scenarios or Sisense versions, so we strongly recommend testing it in your environment before deployment. If you need further assistance with this, please let us know.
