Azure Synapse Analytics is described as the former Azure SQL Data Warehouse, evolved, and as a limitless analytics service that brings together enterprise data warehousing and Big Data analytics. It gives users the freedom to query data using either serverless or provisioned resources, at scale. Azure Synapse brings these two worlds together with a unified experience to ingest, prepare, manage, and serve data for immediate BI and machine learning needs.
$4,700
per month 5000 Synapse Commit Units (SCUs)
Treasure Data
Scoreย 8.9ย outย ofย 10
Mid-Size Companies (51-1,000 employees)
Treasure Data is an enterprise customer data platform (CDP) that reclaims customer-centricity in the age of the digital customer. It does this by connecting all data and uniting teams and systems into one customer data platform to power purposeful engagements.
It's well suited for large, fastly growing, and frequently changing data warehouses (e.g., in startups). It's also suited for companies that want a single, relatively easy-to-use, centralized cloud service for all their data needs. Larger, more structured organizations could still benefit from this service by using Synapse Dedicated SQL Pools, knowing that costs will be much higher than other solutions. I think this product is not suited for smaller, simpler workloads (where an Azure SQL Database and a Data Factory could be enough) or very large scenarios, where it may be better to build custom infrastructure.
Treasure Data is well suited to integrating multiple data sources, including online and digital sources. It is also well suited to trigger audience activations to known customers based on their online activity, integrating 3rd party data, and activating target audiences to ad platforms.
CDP provides a unified view of data from all touchpoints in the customer journey until a single customer uses the service. This feature is very helpful in making service decisions and direction.
It provides a variety of extensions to bring your data together in one place and helps you do this easily.
Kits provided by Treasure Box provide basic but helpful methods for further development of services.
It takes some time to setup a proper SQL Datawarehouse architecture. Without proper SSIS/automation scripts, this can be a very daunting task.
It takes a lot of foresight when designing a Data Warehouse. If not properly designed, it can be very troublesome to use and/or modify later on.
It takes a lot of effort to maintain. Businesses are continually changing. With that, a full time staff member or more will be required to maintain the SQL Data Warehouse.
I do think that we definitely will be renewing. We are putting major resources, time, and effort into Treasure Data becoming an extension of our organization, in many ways. We are working toward complete synergies with this product and leadership is very excited about the direction we are heading to be completely customer-centric.
The data warehouse portion is very much like old style on-prem SQL server, so most SQL skills one has mastered carry over easily. Azure Data Factory has an easy drag and drop system which allows quick building of pipelines with minimal coding. The Spark portion is the only really complex portion, but if there's an in-house python expert, then the Spark portion is also quiet useable.
It's a easy platform to use and give the user detailed logs about what is going on in the workflows, so someone that do not have a lot of experience can start to work with it. And also the master segment usability is awesome, as we can filter a lot of data the way we want.
As treasure data has a 24 hours support, every time we has big issues that impacts the zones, we do have immediatly support from the treasure data team, so I would say that we do not have any issues with availability
Since treasure data has started having a huge amount of data, sometimes we do have problems with the workflows logs because we generate a lot of then. But with integrations I have not to complain, its really easy to integrate with other platforms.
Microsoft does its best to support Synapse. More and more articles are being added to the documentation, providing more useful information on best utilizing its features. The examples provided work well for basic knowledge, but more complex examples should be added to further assist in discovering the vast abilities that the system has.
The technical team has a good hold on the nuances of the data related to our organization. I have found the online technical support on their site quite responsive including the L1 support. In cases where the L1 team isn't able to resolve, I have found they are prompt in getting the product team's input to get a quick resolution.
I wasnt here at the training in the start, but I had a few training with treasure data for a few functionalities, and they provided me god explanations and great documentations, eve if the project were in beta.
When client is already having or using Azure then itโs wise to go with Synapse rather than using Snowflake. We got a lot of help from Microsoft consultants and Microsoft partners while implementing our EDW via Synapse and support is easily available via Microsoft resources and blogs. I donโt see that with Snowflake
We chose Treasure Data for the supreme customer service and lack of hidden costs. We don't need to manage any infrastructure or scale anything to meet customer demand. Treasure Data handles everything and makes it easy for us to integrate and focus on the tasks at hand. There may be cheaper options but we do not regret our decision to go with Treasure Data one bit.
We have built and supported our source of truth data tables using Treasure. This forms the foundation of our decision making.
Most of our Tableau data sources are created using a Treasure Data export which is executed by workflows on a daily basis which allows us to have visibility into day to day performance and communicate them to a wide variety of roles.
We load custom data into our Salesforce instance which allows us to trigger certain workflows and build accountability - i.e. a "Sale" will only count once a certain product driven event occurs which comes from data we pipe into Treasure and then into Salesforce.