For some time now, we were focusing on syncing data from cloud data sources like Salesforce, Zendesk, NetSuite, etc. Which bothered us quite a lot, especially since our users and customers were using databases like PostgreSQL, MySQL, or MongoDB as their product repositories.
But not anymore…
Earlier this year, we launched PostgreSQL as a data source. Today we launch a bunch of relational and NoSQL databases as sources.
Before I get into more detail, let me share how such integrations helped us internally and why this is so awesome in the end:
Blendo is being accessed daily by users that create events and move data from their data sources to their data warehouses. Our statistical usage events are retained into MongoDB. One of our main struggles was to analyze how is product engagement affected per data source and better understand data volume usage.
Such analysis needed data from our MongoDB (product usage), Salesforce (sales information), and Chargebee (billing/subscription information).
We started by pulling our MongoDB data into our PostgreSQL data warehouse first.
|Sync your Production data along with the rest of your business data to any data warehouse. Analytics-ready data with no hassle.||Integrate Now|
Then connected Chargebee, which has our subscription information that is necessary to segment based on tiers.
|Sync your Subscription data along with the rest of your business data to any data warehouse. Analytics-ready data with no hassle.||Integrate Now|
Lastly, we needed the sales information from our Salesforce CRM to give us revenue-based insights.
|Sync your sales data along with the rest of your business data to any data warehouse. Analytics-ready data with no hassle.||Integrate Now|
Having all this data into our PostgreSQL data warehouse helped us build data models into our Periscope Data dashboard to analyze volume during trials and segment performance per pricing tiers and per integration data source.
Why having your production database into your data warehouse is awesome?
Fewer silos – An essential and valuable part of your company data might live in a version of a database. It can contain from product data to financial info that you need to load it into a data warehouse for analytics use cases. No more silos for your production data, connect your database, and we‘ll handle the rest.
Faster implementation, less maintenance – You don’t need to create any ETL/ELT scripts or engage engineering resources to pull your data from your production database into your data warehouse. Otherway, you would pretty much need a complete software engineering pipeline for the ETL part. Who is writing and maintaining the scripts? How do we version control them? What happens when a bug appears, and how do we react? These things are not in the way anymore.
Only the data you need – Do you need all the data in your production database? If not, does it make sense to replicate everything anyway? Do you need the rest of the data (e.g., Sales, Marketing, Support cloud application data) along? You will have all the data you care in one place.
Data when you need it – If your data in your production DB never change, it would be easy. You can take a full dump (backup) of the DB and load it into a data warehouse. Of course, the data in the database is constantly changing. Even a snapshot can be already out-of-date by the time you’ve load it. With Blendo, you now have access to your production data into your data warehouse the moment you need it.
And now, let’s take a closer look at the functionality we have added.
Integrate easily with a few clicks setup.
Select only the resources you need.
Get incremental imports.
You can get incremental imports based on an existing field. For SQL Server, MySQL, and MariaDB, you may configure an update field, which is a table column, with timestamp type. That field is used by Blendo to detect and support incremental updates.
For MongoDB, the update field is a collection field, with date type, that is used by Blendo to detect when a collection document has been updated.
Connect through SSH or SSH Tunnel.
If your database requires SSL or is behind a firewall, you can set this up too.
How to Automate MS SQL Server, MySQL, MariaDB or MongoDB sync to your analytics warehouse for business insights with Blendo
Firstly, you need to have access to your MS SQL Server, MySQL, MariaDB, or MongoDB and make sure you have a Blendo account. If you do not have access, it is helpful to ask assistance from an engineer from your side or check with our customer support.
- Connect your data warehouse. We support all the popular ones like Amazon Redshift, Google BigQuery, MS SQL Server, PostgreSQL, and Snowflake. Don’t have one? Contact our team to help.
- Connect MS SQL Server, MySQL, MariaDB, or MongoDB as a data source (here is Blendo documentation for MS SQL Server, MySQL, MariaDB, or MongoDB )
- Connect any other business cloud data sources.
- Analyze with your favorite BI tool. Blendo is BI agnostic, so any of the BIs will be able to make use of the analytics-ready data Blendo prepares for you.
New to Blendo? It’s a tool that helps anyone connect their business apps with their data warehouse and BI automatically — without code. Blendo will prepare and keep in sync analytics-ready data from your data sources so you can focus on getting smarter insights. Sign up for a free trial to use MongoDB, MS SQL Server, MySQL, or MariaDB as a source with Blendo.
If you’ve been a Blendo customer for a while, you may know that we’re very receptive to feedback from our users. So if you see any way we could make Blendo even better, please let us know.