Technology Solutions

Stelo + MySQL

My SQL

Use Stelo to move operational data from MySQL to use in data warehouse, dashboard or delta lake applications that allow you to run and monitor your business. Stelo can connect all source and destination target types for every user, so you can easily move data from anywhere to anywhere.

Stelo is a cost-efficient, low-impact, real-time data replication software for SQL environments. Moving data across a wide area network (WAN) is inherently associated with a high level of information delay due to limitations on how fast data can transit across a network. Stelo compensates for the inherent high latency of WANs, providing a seamless experience.

Our team has worked with each version of the SQL programming language over the last 30+ years, allowing us to create the most resilient, robust, and efficient solution for offloading heterogeneous source data into and out of your MySQL data stores. Easily replicate millions of transactions per hour and transfer data sets over 1TB.

Related Resources

TECHNICAL DATA SHEET →

QUICK START GUIDE →

WHAT IS TRANSACTIONAL REPLICATION →

SCHEDULE A DEMO

 

Connects To

Flexible Deployment Icon_Noun 4351350_Green Customizable

Anywhere-to-Anywhere

Avoid vendor lock-in. Stelo uses heterogeneous replication for bi-directional support across all source and destination types. Our open-standards approach allows us to remain vendor-agnostic while providing highly flexible deployment models.

Rapid Deployment Icon_Noun 3967969_Green Quick Setup

Rapid Deployment

Streamline your deployment plan without costly delays. Stelo typically deploys in less than a day and cuts production time down from months to only weeks.

 Time and Labor Icon_Noun 4636078_Green Easy-to-Use

Set It and Forget It

Simple installation with GUI interface, configuration wizard, and advanced tools makes product setup and operation straightforward, with no programming needed. Once running, Stelo reliably operates in the background without requiring dedicated engineering support to maintain and manage. Alter, add, and drop schema changes are replicated automatically.

Near-Zero Footprint Icon_Noun 1465960_Green Low Impact

Near-Zero Footprint

Our process provides ultra-low CPU load (less than 1% typical) to minimize production impact and avoid operational disruption. No source or destination software installation required. Only transfer data you need thanks to Dataset Partitioning.

Data Scalability Icon_Noun 1304652_Green Cost-Efficient

Unlimited Connections

A single instance can support multiple sources and destinations without additional licensing. The Stelo license model is independent of the number of cores to either the source or destination, so you only pay for the capacity required to support the transaction volume. Your data ecosystem can change over time without additional costs.

Multi-Threaded Loading Icon_Noun 3263022_Green Low Latency

Multi-Threaded Processing

Stelo leverages native data loading functions, and exploits multithreaded processing to provide fast, reliable performance for replicating multiple tables concurrently.

Data Warehousing: It's Time to Evolve Your Data Management Strategy

The “new frontier” of data ingestion goes beyond warehousing to enable a lot more choice. Some companies prefer to stream data into cloud-based delta lakes while maintaining their existing data warehouse; that way, they can take advantage of new technologies from companies like Synapse while maintaining their existing applications. Others would prefer to get rid of their in-house data centers all together.

Stelo encourages customers to make improvements by integrating technologies that allow them to use their data better. We bring the robustness and power our customers have come to expect from data warehousing to delta lakes, too. Advancing data management strategy is not about displacing current software and hardware investments; it’s about making it easier to leverage new technologies that can unlock your data’s embedded potential.

READ THE BLOG

FAQ

Can Stelo use pre-generated tables or indexes to migrate my Oracle JDE data from Db2 to SQL Server?

We encourage customers to configure Stelo’s software to create the destination tables on the SQL Server. In part, this is to ensure the proper mapping of change data captured on the IBM i system and the destination table. Also, if your high availability (HA) software utilizes *AFTER images only for capturing change data, then Stelo’s software must rely upon a synthetic column (the Relative Record Number or "RRN") to uniquely identify the row in the destination table, and it is unlikely that the Oracle JD Edwards (JDE) tool would provide this column. Therefore, it is best to allow Stelo to create the destination, including this column for each table. Alternatively, if the HA software configures *BOTH images in the journals then we can dispense with the RRN column and just utilize any unique index (including a primary key) to identify rows.

Another issue that should be addressed in the planning stage is the use of Unicode datatypes on the destination SQL Server. We strongly encourage customers to use NCHAR/NVARCHAR data types for SQL Server, as this provides the greatest fidelity when mapping data from IBM i EBCDIC to Windows and other non-EBCDIC environments. Our recommendation is to allow Stelo to create the tables and exploit UNICODE data types, and then use the tool to create any additional indexes.

Can Stelo handle high-volume requirements without breaking my bank?

Stelo can handle large-scale data transfers replication with sub-second latency. A single instance can support multiple sources and destinations without additional licensing. The Stelo model is independent of the number of cores of either the source or destination—so you only pay for the capacity required to support the transaction volume connections. This cost-efficient method merges source data flows into one stream, and then it is applied to any number of subscribing destinations. Stelo delivers enterprise-level performance without enterprise-level cost.

Does Stelo use source resources?

Unlike trigger-based replication software that can consume quite a bit of production resources, Stelo is built to have a near-zero impact on production databases. It’s deployed on an intermediate server between the source and destination databases, resulting in virtually no resource drain on production infrastructure.

Can Stelo build my data warehouse?

Yes, Stelo has an automatic method to build out data warehouses, so we can do the heavy lifting for you. It works well whether you're doing a migration up to the cloud or are continuing with ongoing replication.

We encourage you to configure Stelo to create the destination tables on the SQL Server. In part this is to ensure the proper mapping of change data captured on the source system and the destination table. Also, if the Customer's high availability (HA) software utilizes *AFTER images only for capturing change data, then Stelo must rely upon a synthetic column (the Relative Record Number or "RRN") to uniquely identify the row in the destination table, and it is unlikely that some tools such as the JDE tool would provide this column. Therefore, it is best to allow Stelo to create the destination, including this column for each table. Alternatively, if the HA software configures *BOTH images in the journals then we can dispense with the RRN column and just utilize any unique index (including a primary key) to identify rows.

Another issue that should be addressed in the planning stage is the use of Unicode data types on the destination SQL Server. We strongly encourage customers to use NCHAR/NVARCHAR data types for SQL Server as this provides the greatest fidelity when mapping data from IBM i EBCDIC to Windows and other non-EBCDIC environments.

Our recommendation is to allow Stelo to create the tables and exploit UNICODE data-types, and then use the tool to create any additional indexes.

Support Features

Solutions Icon_Green

Accessible Support

Quick support is available for training, troubleshooting, version updates, and data replication architecture. 24/7 Urgent Incident Support is included in annual subscriptions.

Solutions Icon_Green

Highly Experienced Team

Stelo’s technologists have more than 30 years' experience developing reliable data software. Whether you need basic support or have a tricky technical challenge, we can work with you to solve any problem.

Solutions Icon_Green

End-to-End Proficiency

Our team has detailed knowledge of every data platform we support and can troubleshoot end-to-end replication pairing in heterogeneous environments to ensure the pairings are working properly.

Solutions Icon_Green

Constant Evolution

Unlike some other solutions, Stelo won't go out of date. New source and target types are continuously added through active updates to stay compatible with emerging market requirements.

The Latest from Our Blog

Strategies for Futureproofing Data Management

Strategies for Futureproofing Data Management

Nov 10, 2022 2:10:47 PM 1 min read
StarQuest Rebrands as Stelo: New Name, Same Stellar Solutions and Support
StarQuest Rebrands as Stelo: New Name, Same Stellar Solutions and Support

StarQuest Rebrands as Stelo: New Name, Same Stellar Solutions and Support

Oct 6, 2022 8:04:00 AM 1 min read
Evolving Your Data Management Strategy Beyond Data Warehousing

Evolving Your Data Management Strategy Beyond Data Warehousing

Aug 2, 2022 7:35:39 AM 2 min read
Stelo Now Offers Limited Use Oracle GoldenGate Licenses

Stelo Now Offers Limited Use Oracle GoldenGate Licenses

Jul 21, 2022 9:28:56 AM 2 min read

Get Started

These three steps will help you ensure Stelo works for your needs, then seamlessly deploy your solution.

1

Schedule a Demo

Our expert consultants will guide you through the functionality of Stelo, using your intended data stores.

2

Get a Free Trial

Test the full capability of the software in your own environment for 15 days. No obligations.

3

Go Live

When you're ready, we can deploy your Stelo instance in under 24 hours with no disruptions to your operations.

SCHEDULE A DEMO