Gluesync 2.2.6

With the release of Gluesync 2.2.6.0, we are introducing major new agents and deep architectural refinements. Specifically, these updates enhance how enterprises synchronize data across diverse environments.

What’s New in 2.2.6.0

This release marks a significant milestone in our mission. In fact, it bridges legacy systems with modern cloud data warehouses through powerful new source and target capabilities.

Expanding the ecosystem: SAP HANA and Redshift

We continue to broaden our connectivity options for complex enterprise architectures. Consequently, this release introduces two major agent additions:

• SAP HANA (source): Real-time data integration is now available for SAP HANA databases, utilizing our specialized triggers-based auditing structure.
• Amazon Redshift (target): Support for Redshift as a target now includes high-performance Bulk operations via AWS S3 as a staging area (which is required), alongside batch operations for transactional writes.

Granular data control: precision and scale

Architects now gain fine-grained control over their data structures. Indeed, this version introduces refined discovery for column length, precision, and scale across all databases. This improvement ensures accurate schema synchronization and data type mapping. Furthermore, it enables optimized Parquet file generation with full decimal support.

Optimized write performance

Efficiency remains a core pillar of this update. By significantly reducing network round trips during write operations, Gluesync 2.2.6.0 boosts overall performance. As a result, data moves across your infrastructure with minimal latency.

Operational clarity and UI evolution

We are transitioning to a new React-based UI framework. For example, we debuted a redesigned login screen that displays release notes directly upon access. On the backend, we improved observability and fixed minor bugs across our agent catalog. This includes connectors for Oracle, MS SQL Server, Couchbase, and DynamoDB.

Note on the upgrade process

Due to the under-the-hood architectural updates, the upgrade process towards version 2.2.6.0 may take some time to complete. Users might see a “Bad gateway” message while it is loading: this is totally normal and expected behavior. The ingress proxy handles the 443 GETs from your client until the Core Hub activates the Web Server back again at the end of the migration process.

Why this matters for your data strategy

As Gluesync continues to bridge the gap between legacy silos and modern destinations, the focus shifts toward operational excellence.

Version 2.2.6.0 isn’t just about moving data. It’s about moving it with the peace of mind that your integration layer is compatible with the latest industry standards and resilient to the complexities of enterprise databases. Whether you are offloading query-intensive workloads or powering real-time analytics, this release provides the stability required for 24/7 production environments.

Ready to upgrade? Consult the official documentation for the full technical changelog and upgrade instructions.