Version 26.10 introduces a dedicated SQL Editor window directly within the Data Warehouse Manager, enabling technical users to query the Data Warehouse without leaving the application. The SQL Editor provides a native query interface alongside the database browser, allowing users to write and execute SQL, inspect schemas and query results — all within Data Warehouse Manager.
The editor is intended primarily as a development and troubleshooting tool for technical users of the Data Warehouse, reducing the need to rely on external SQL clients for day-to-day warehouse work.
Benefits
Enable technical users to query the Data Warehouse directly from within the Data Warehouse Manager, eliminating the need for separate external SQL tools and reducing context switching.
Save time for database administrators and data engineers by providing a seamlessly integrated development environment inside the familiar SimCorp Dimension application.
Optimize troubleshooting and development workflows by allowing users to validate queries, browse table structures and inspect results without leaving the Data Warehouse Manager.
Caption: SQL Query Editor within the Data Warehouse Manager — the database explorer (left) allows browsing of schemas and tables, while the workspace (right) supports writing and executing SQL queries directly against the warehouse.
Subscription based licensing
Data Warehouse
Sales module dependency
Data Warehouse Manager
Support for Importing Data from WEB API Using Snowpipe
From version 26.10, data can be imported directly into the Data Warehouse via a Web API using Snowpipe Streaming. This capability is available to all snowflake warehouse clients and removes the need to use an Azure Blob Container for loading data into the warehouse.
The integration follows a streamlined five-stage pipeline: the DWH Load Plan pulls data from the Investment Analytics Platform (IAP) Web API, streams it via Snowpipe Streaming as NDJSON rows into Snowflake landing tables, transforms the raw JSON in a DWH Staging table, and finally writes records transactionally to DWH target tables. The flow is scheduled or triggered by DWH load plan execution — no file staging is required at any step.
Benefits
Enable direct import of analytics data from an API into the Data Warehouse using Snowpipe Streaming, removing the dependency on Azure Blob Container and simplifying the overall ingestion architecture.
Save implementation and operational effort for all Snowflake Warehouse clients by providing a file-free, streaming pipeline that reduces infrastructure complexity and the overhead of managing intermediate blob storage.
Optimize data loading performance through Snowpipe Streaming's low-latency, row-level ingest, which appends data directly to Snowflake landing tables without the delays associated with file-based staging.
Caption: Data Warehouse Connections dialog showing the new "Snowpipe Streaming" option in the Snowflake Connection settings — enabling the streaming ingest path for a given connection.
Subscription-based licensing
Data Warehouse
Sales module dependency
Data Warehouse Manager
Entity Scope Loads in DWH
From version 26.10, users can execute Entity Scope Loads in the Data Warehouse, extending the existing suite of scope-based loads — which already supports fund and portfolio scopes — to include entity-level granularity.
Entity cutoff values are stored in the DWH_CUTOFF_VALUES table using the same pattern already in place for Fund and Portfolio Scoped Loads. Entity Scoped loads can be initiated from the Load Monitor using Execute or Enqueue, and are also accessible via the Data Warehouse REST API, supporting automated and event-driven workflows.
Benefits
Enable performance data to be loaded at the entity level, providing organizations with more granular control over Data Warehouse load operations and eliminating unnecessary processing across the full fund or portfolio scope.
Optimize data pipeline efficiency by triggering entity-scoped loads as and when needed as opposed to loading all Entities at once.
Enable entity scope loads to be initiated from the Load Monitor (Execute and Enqueue) as well as via the REST API, offering flexible integration options for both interactive use and automated, event-driven orchestration.
Caption: Load Monitor showing a DWH load with Entity scope — the load instance includes Web API Data Extraction (Snowpipe), staging table validation and target load tasks.
Caption: DWH_CUTOFF_VALUES table showing entity-level cutoff records with ENTITY_IK values and timestamps, stored using the same pattern as Fund and Portfolio Scoped Loads.
Caption: Data Warehouse REST API endpoints for Enqueue and Execute Load Plans — the executeLoadPlan body now supports a businessEntities scope array, enabling entity-scoped loads to be initiated programmatically.
Investments in illiquid alternative assets are long-term oriented. To deal with unexpected developments, investment managers need to assess what happens if certain scenarios materialize. Stress scenarios are an indispensable part of portfolio management to test the effects of changing conditions on the portfolio’s behavior. For the alternative investment funds such changing mainly manifest in changes of cashflow patterns which can now be assessed within the Alternatives Strategy module.
Benefits
Enables users to assess how a portfolio of funds will respond to future changes in market conditions and to identify factors that imperil the investment strategy’s success.
Enables users to produce more robust forecasts as stress scenarios can reflect a wider variation of possible futures and situations that have not necessarily occurred in the past.
Allows users to flexibly combine several types of cashflow-related stresses like, for illustration, the acceleration of capital calls plus a delay of repayments plus an extension of fund lifetimes and define the groups of funds to which these combined stresses can be applied.
The Alternatives Strategy module allows users to generate liquidity and capital risk related KPIs, such as a portfolio’s Cashflow-at-Risk (i.e., the net of contributions and distributions) and how it develops over time: Applying a stress scenario that assumes an acceleration of contributions results in a situation where an investor needs to pay out money earlier than expected and, as several contributions are compressed within a shorter time frame, also result in higher aggregate amounts that are called:
The Alternatives Strategy module allows users to look at this in more detail, separately for contributions and distributions and also assess the impact on the portfolio’s overall valuation:
This image shows a combination of various stresses: an accelerated contribution schedule where investors have to provide funding quicker than usual. Consistent with a stressed market environment are longer lifetime for funds as fund managers attempt to ‘ride out’ crises and wait for a better exit environment for their portfolio companies. Therefore also delayed realizations are part of this stress scenario. Consistent with these cashflow patterns is a portfolio valuation that achieves its peak significantly later.
Subscription based licensing
Alternatives Strategy Analysis
Sales module dependency
Alternative Investments Manager, Cash-flow Forecasting for Illiquid Alternative Investment Funds
Transfer of Data from SCD to Snowflake using Snowpipe
In 2025 Snowflake introduced its Snowpipe high performance architecture for direct ingestion of data to Snowflake schema tables. In version 26.04 the SimCorp Data Warehouse introduced the ability to utilize Snowpipe to ingest data directly from SimCorp Dimension into Staging tables on the Data Warehouse Schema as part of the Data Warehouse load. This replaces the existing process which stages data in an Azure Blob Container or Amazon S3 bucket before importing to the staging tables on the Data Warehouse. The functionality uses key-pair authentication with JSON Web Tokens (JWT) to establish a connection at run-time and then stream data using REST APIs.
Benefits
No longer a dependency on Azure/Amazon cloud architecture to move data from SimCorp Dimension into Snowflake reducing the amount of required infrastructure to deploy the SimCorp Data Warehouse.
Improves operational resilience by removing multi‑step cloud‑storage dependencies, reducing points of failure and simplifying troubleshooting across the data ingestion pipeline.
Reduces end‑to‑end load latency by streaming data directly into Snowflake, enabling faster availability of refreshed datasets for downstream reporting
Note: This functionality is only available for clients using Key-Pair authentication for Data Warehouse. It does not support ingestion from API Data Sources as yet. Subsequent releases will provide Snowpipe support for clients using OAUTH to Authentication with Snowflake, as well as API Data Source ingestion to SimCorp Data Warehouse.
Caption: Architecture showing data flow from SCD to Snowflake
Subscription based licensing
Snowflake Data Warehouse
Sales module dependency
Data Warehouse Manager/IAP
Release 26.01
Ability for clients to configure Loading of tables into Data Warehouse using variable based approach
Clients using the Investment Analytics Platform (IAP) for Performance have a need to store historical performance data in the SimCorp Data Warehouse for reporting and downstream publication. To support this, version 26.01 introduces new functionality that makes importing data from IAP APIs easier and more customizable.
With this release, you can:
Create and execute multiple configurations for API-based fact tables tailored to your reporting needs.
Leverage new standard fact tables added to the IMW model for seamless integration of IAP data.
This enhancement gives you greater flexibility and control over how performance data flows into your Data Warehouse.
Benefits
Greater Flexibility: Ability to easily configure Data Warehouse loads to extract the relevant IAP data based on different parameters available in the APIs
Standardization of Integration: Complexity of constructing ETL logic from IAP APIs is now managed as part of the Data Warehouse Investment Management Warehouse(IMW) model.
Historical Data Management: Simplifies storing and versioning of historical IAP performance data for accurate client reporting and downstream publication.
Caption: New Menu for configuring Table Imports for API Based tables in DWH Manager
Caption: Clients can define multiple configurations for extracting different data sets from tables based on APIs, eg different date sets for daily vs month-end requirements. Configuration names are customisable
Caption: Each configuration has a set of variables attached to it which allows the client to flexibly control what data is extracted from the APIs by adding values for the available variables. These variables are linked to the parameters available on the underlying API
Caption: Each configuration appears as a separate item that can be executed as part of a load plan and can be executed independently or at the same time
Caption: New standard tables have been added to SimCorp IMW model to capture Single-Day figures from IAP
Subscription based licensing
Snowflake Data Warehouse
Sales module dependency
Data Warehouse Manager/IAP
Ability for clients to execute Data Warehouse Processes using API
As of version 26.01, clients using the Snowflake Data Warehouse now have access to the REST API Led – Cloud Data Warehouse Service, a modernized, HTTP-based execution layer designed specifically for Data Warehouse workloads. This new framework replaces the legacy Reporting Data Jobs Service, facilitating a cloud-friendly, scalable approach to orchestration and control of warehouse processes.
Benefits
Built on industry-standard HTTP/REST within the SimCorp API Gateway framework, this service enables direct invocation of Data Warehouse processes without reliance on traditional batch jobs.
With expanded endpoint coverage and REST-driven execution, users can now run multiple Data Warehouses in parallel without spawning additional services. This allows for more efficient scaling for Data Warehouse processes.
The service can also be executed via command line, enabling seamless integration into enterprise scheduling and DataOps automation tools, making orchestration repeatable, scriptable, and CI-friendly.
Subscription based licensing
Snowflake Data Warehouse
Sales module dependency
Data Warehouse Manager
Release 25.10
Data Integration API (Data Ingestion API)
This module makes it possible to expose Data Format Setups as well as their integration with Direct Filters through Web API endpoints, using standard technologies like JSON and HTTPS. This allows external systems to exchange data with SimCorp Dimension in a structured format.
In addition to a set of predefined endpoints that accept flat data structures, users can also define custom endpoints with tailored JSON models based on individual Data Format Setups—offering flexibility for more specific integration needs.
The module is built on SimCorp’s WebAPI framework, which handles authorization and other core functions. To use it, the required infrastructure must be in place within your SimCorp Dimension environment.
Benefits
Extends the range of windows available via API endpoints in a configurable way.
Enable external systems to trigger filter import operations via API.
Optimize data governance by exposing only selected fields through publishable definitions.
Definition of Dynamic Endpoint with configurable JSON contract via Data Format Setup.
Subscription based licensing
Foundations
Sales module dependency
Filter Tool Box
Data Extraction API
This module makes it possible to directly expose Extraction Definitions, Extraction Setups, and Extract Exporters as Web API endpoints, using standard technologies like JSON and HTTPS. This allows external systems to retrieve structured data from SimCorp Dimension in a consistent and secure format.
The module is built on SimCorp’s WebAPI framework, which handles authorization and other core functionalities. To use it, the required infrastructure must be configured within your SimCorp Dimension environment.
Benefits
Enable easy data access by exposing Extraction Definitions, Setups, and Exporters through standardized Web API endpoints.
Leverage SimCorp’s modern WebAPI framework for scalable, authorized data exchange across systems.
Subscription based licensing
IMS Data Domain API + Foundations
Sales module dependency
IMS Data Domain API
Release 25.07 Data Management
Data Warehouse connectivity via Managed Identity – Azure-hosted clients
In anticipation of a mandatory change to Snowflake authentication protocols (Snowflake documentation here), the SimCorp Data Warehouse offers clients who host SimCorp Dimension on Azure the option to authenticate to Snowflake using an External OAuth service hosted in Azure. From June 2026, usernames and passwords for service user type (which the Data Warehouse currently uses to authenticate) will no longer be supported by Snowflake. The External OAuth functionality offers a more secure method for authenticating with Snowflake, which does not rely on the storage of credentials in Azure Keyvault. Access to the OAuth Service uses the Azure Managed Identity of the machine hosting the Reporting Data Jobs Service in SimCorp Dimension.
Benefits
Enhanced security: By using External OAuth authentication, credentials are no longer stored in Azure Key vault, reducing the risk of credential leakage or misuse.
Future-proof compliance: The new method aligns with Snowflake’s upcoming authentication requirements, ensuring continued access and support beyond June 2026.
Integration with Azure: Leveraging Azure’s Managed Identity for authentication simplifies access management and enhances integration with existing Azure-hosted infrastructure.
Schema Connections Window in Data Warehouse with new Authorization Method for External OAuth. Clients Specify the UID Managed Identity Client and Object ID to be used to authenticate with the OAuth Service.
Subscription based licensing
Data Warehouse Manager
Sales module dependency
Snowflake Extension for Data Warehouse
Azure Blob Storage authorization via Azure Managed Identity
Clients hosting SimCorp Dimension on Azure now have the option to authorize Azure Blob Storage using Azure Managed Identity instead of an access key. The Azure Managed Identity is used to obtain an access token via Microsoft Entra ID (formerly Azure Active Directory) authorization, enabling secure access to the required Blob Storage container.
Benefits
Improved aecurity: Eliminates the need to store and manage access keys, reducing the risk of accidental exposure or misuse of credentials.
Simplified access management: Authorization is handled automatically through Azure’s identity platform (Microsoft Entra ID), streamlining permissions and reducing administrative overhead.
Seamless integration with Azure Services: Managed identities are natively supported across Azure, enabling secure and consistent access to Blob Storage and other resources without additional configuration.
Schema Connections Window in Data Warehouse with Managed Identity specified as method of Authorization for Storage. The Managed Identity to be used is saved as a parameter in the CNF.ini file in the SimCorp Dimension Netroot Directory.
Subscription based licensing
Data Warehouse Manager
Sales module dependency
Snowflake Extension for Data Warehouse
Snowflake Authentication via Key Pair
In anticipation of a mandatory change to Snowflake authentication protocols (Snowflake documentation here), the SimCorp Data Warehouse offers clients the ability to authenticate to Snowflake using the Key Pair authentication method. From June 2026, username and password (which the Data Warehouse currently uses to authenticate) will no longer be supported. The new functionality allows clients to generate a private key which is encrypted and saved into the SimCorp Database. This private key is then paired with a public key which is assigned to the user in Snowflake.
Benefits
Enhanced Security: Key Pair authentication eliminates the need for usernames and passwords, reducing the risk of credential theft and unauthorized access. The use of encrypted private keys stored securely in the SimCorp Database ensures a more robust authentication mechanism.
Future-Proof Compliance: By adopting Key Pair authentication ahead of the June 2026 deadline, clients ensure compliance with Snowflake’s upcoming mandatory authentication protocol changes, avoiding disruptions to data access and operations.
Simplified Configuration: Key Pair offers a more simplified flow for replacing Username and Password than using an OAuth service.
Schema Connections Window in Data Warehouse with new Authorisation Method for Private Key. Upon saving the configuration, the private key is encrypted and saved to the SimCorp Database. The public key can be retrieved from the Schema Creation Script.
Subscription based licensing
Data Warehouse Manager
Sales module dependency
Snowflake Extension for Data Warehouse
AWS S3 Bucket for Data Warehouse Storage
Clients now have the option of using an AWS S3 Bucket for exchange of data between SimCorp Dimension and Snowflake. Prior to this version, only Azure Blob storage was supported. Authorization to the S3 bucket is with access key only.
Benefits
Increased flexibility: Clients can now choose between AWS S3 and Azure Blob Storage, enabling them to align data exchange processes with their preferred cloud infrastructure or existing cloud strategy.
Broader cloud compatibility: Supporting AWS S3 expands integration capabilities, making it easier for organizations already using AWS services to incorporate SimCorp Dimension and Snowflake into their workflows.
Schema Connections Window in Data Warehouse with S3 bucket selected as the Storage Provider. Authentication to the S3 bucket is with an access key.
Subscription based licensing
Data Warehouse Manager
Sales module dependency
Snowflake Extension for Data Warehouse
Cross Cloud Access to AWS hosted Snowflake and S3 Bucket
SaaS clients who are hosting SimCorp Dimension on Azure now have the option of integrating the SimCorp Data Warehouse with a Snowflake Account and Storage Solution (S3) hosted on AWS. In this configuration, Azure Managed Identity can be used to retrieve tokens from an Azure-based OAuth service, which grants access to both Snowflake and AWS S3 bucket. In the case of the latter, the token for accessing the S3 bucket is retrieved from an AWS-hosted security token service.
Benefits
Client-controlled storage compliance: Clients can manage their own AWS S3 storage, aligning data handling with internal security policies and regulatory requirements.
Seamless AWS integration: SaaS clients with existing AWS infrastructure can now integrate the SimCorp Data Warehouse while SCD is still hosted on Azure.
Secure and centralized authentication: By leveraging Azure Managed Identity and OAuth, clients benefit from a centralized, token-based authentication mechanism that securely grants access to both Snowflake and AWS S3 without managing separate credentials.
Data Warehouse cross-cloud architecture.
Schema Connection window in Data Warehouse Manager with Azure Managed Identity used to access a Snowflake account and S3 Bucket hosted on AWS.
