In this live roadmap and release session, our product team will present the newest version of the Exasol Engine: featuring major performance enhancements, ease-of-use improvements, and improved AI and ML capabilities. You’ll also see how we’re extending Exasol’s support for Data Lakehouse architectures and broader use cases.
Speakers:
Alexander Stigsen, Chief Product Officer at Exasol
Dr. Florian Wenzel, VP Product Management at Exasol
Madeleine Corneli, Lead Product Manager AI&ML at Exasol
Jürgen Albertsen, Principal Product Manager at Exasol
Nico Conforti, Lead Product Manager at Exasol
Marco Nätlitz, Director Software Engineering at Exasol
Ian Stewart, Product Marketing Director at Exasol
The VOD is available here: https://youtu.be/gVmxWEnndF8
FAQ:
Q: When will the release be available?
A: The release is scheduled for May 18.
Q: Is Lakehouse Turbo is planned to support mirroring data from Azure ADLS instead of AWS S3?
A: Azure ADLS support will be included in a upcoming release in 2026.
Q: When you use Claude with you sales and revenue data and other data. Aren’t you concerned about governance and safety with your data?
A: When you use Claude with you sales and revenue data and other data. Aren’t you concerned about governance and safety with your data?
→ There are several layers of data governance built into the Exasol MCP Server when used with production data. First is authentication - the MCP server can be configured with enterprise systems such as Active Directory to support user impersonation. Therefore the analysis is limited to only the data a user has access to in the database. AI systems such as Claude do not retain information, the data stays in Exasol. However, for added security you can deploy the MCP server locally or with other systems such as AWS Bedrock to reduce data movement and add additional layers of security.
Q: Given that there is no point-in-time recovery and no standby failover, how do you recommend customers in regulated industries to handle disaster recovery?
A: Disaster Recovery, especially in regulated industries, is a critical topic for our customers and a very common requirement. The approach to handle it depends on the RPO and RTO set by the organization and the cost to manage that. For our customers with the strictest and mission-critical databases, many of them choose to make use of our Synchronous Dual Data Center feature, which allows the database to write the data redundantly to nodes in a different data center. This effectively puts the Recovery Point at 0 because all data is written redundantly during the COMMIT phase. Likewise, the database just needs to be started in the other data center to resume operations within minutes. For customers with longer RPOs, they could use a backup approach that is also written to a second cluster, multiple times per day. The organization also needs to consider cost of achieving their RPO/RTO vs what they really need. In either case, we always recommend at a minimum to write backups to external sources to prevent against a disaster on the cluster. Feel free to visit Business Continuity to get an overview of various solutions.