The OneView Ad Platform (formerly Dataxu, acquired by Roku October 2019) is a solution for marketers and content owners to, according to the vendor, reach more cord cutters and measure performance using the largest TV identity dataset, where advertisers can manage their entire campaigns – including OTT, linear TV, omnichannel, and more – all in one place.
N/A
SSIS
Score 7.6 out of 10
N/A
Microsoft's SQL Server Integration Services (SSIS) is a data integration solution.
N/A
Pricing
Roku OneView
SQL Server Integration Services (SSIS)
Editions & Modules
No answers on this topic
No answers on this topic
Offerings
Pricing Offerings
Roku OneView
SSIS
Free Trial
No
No
Free/Freemium Version
No
No
Premium Consulting/Integration Services
No
No
Entry-level Setup Fee
No setup fee
No setup fee
Additional Details
—
—
More Pricing Information
Community Pulse
Roku OneView
SQL Server Integration Services (SSIS)
Features
Roku OneView
SQL Server Integration Services (SSIS)
Data Source Connection
Comparison of Data Source Connection features of Product A and Product B
Roku OneView
-
Ratings
SQL Server Integration Services (SSIS)
7.0
56 Ratings
16% below category average
Connect to traditional data sources
00 Ratings
9.056 Ratings
Connecto to Big Data and NoSQL
00 Ratings
5.043 Ratings
Data Transformations
Comparison of Data Transformations features of Product A and Product B
Roku OneView
-
Ratings
SQL Server Integration Services (SSIS)
6.8
56 Ratings
17% below category average
Simple transformations
00 Ratings
9.056 Ratings
Complex transformations
00 Ratings
4.755 Ratings
Data Modeling
Comparison of Data Modeling features of Product A and Product B
Roku OneView
-
Ratings
SQL Server Integration Services (SSIS)
7.5
54 Ratings
4% below category average
Data model creation
00 Ratings
9.028 Ratings
Metadata management
00 Ratings
6.035 Ratings
Business rules and workflow
00 Ratings
7.045 Ratings
Collaboration
00 Ratings
9.040 Ratings
Testing and debugging
00 Ratings
6.351 Ratings
Data Governance
Comparison of Data Governance features of Product A and Product B
Dataxu is great for running multiple campaigns at the same time. It's reporting features are great as well as the exchanges it has to offer. For a company just wanting to run one campaign, I don't think it would be worth their time learning how to navigate Dataxu; however, for a company running to run multiple campaigns, Dataxu makes the process easier. Dataxu has great customer service representatives that provide superior training whenever needed.
As I mentioned earlier SQL Server Integration Services is suitable if you want to manage data from different applications. It really helps in fetching the data and generating reports. Its automation make it very easy and time efficient. It works well with large database as well. But it doesn't work well with real time data, it will take some time to gather the real time data. I would not recommend using it in a real time/fast-paced environment.
The platform's mobile serving capacity is great; spending is always consistent and the impression numbers are some of the highest we've seen. We can always depend on this method of ad serving to get us the results that we and our clients expect.
The intelligence and audience information (found under the Reports tab) is helpful when writing a "story" for the client; it assists us in determining future targeting strategies. Custom Queries are also available under the Reports tab and these are extremely helpful when we need to view specific details about the campaign.
The dashboard's spend-to-date graphic helps us to immediately recognize what campaigns are falling behind so that we may adjust the budgets accordingly.
Flagging problems. For example, if a campaign has been running a week and hasn't spent any of the budgets, there could be a setting enabling it from doing so. When you have multiple campaigns running, it's hard to track this.
Connection managers for online data sources can be tricky to configure.
Performance tuning is an art form and trialing different data flow task options can be cumbersome. SSIS can do a better job of providing performance data including historical for monitoring.
Mapping destination using OLE DB command is difficult as destination columns are unnamed.
Excel or flat file connections are limited by version and type.
Some features should be revised or improved, some tools (using it with Visual Studio) of the toolbox should be less schematic and somewhat more flexible. Using for example, the CSV data import is still very old-fashioned and if the data format changes it requires a bit of manual labor to accept the new data structure
SSIS is a great tool for most ETL needs. It has the 90% (or more) use cases covered and even in many of the use cases where it is not ideal SSIS can be extended via a .NET language to do the job well in a supportable way for almost any performance workload.
SQL Server Integration Services performance is dependent directly upon the resources provided to the system. In our environment, we allocated 6 nodes of 4 CPUs, 64GB each, running in parallel. Unfortunately, we had to ramp-up to such a robust environment to get the performance to where we needed it. Most of the reports are completed in a reasonable timeframe. However, in the case of slow running reports, it is often difficult if not impossible to cancel the report without killing the report instance or stopping the service.
At Haberfeld, we had our own customer service representative out of Boston. He provided superior and timely support for all of our questions and needs. He also ran test campaigns to show us what our potential impact could be before we put dollars towards anything. He even came all the way down to Nebraska to visit with us at one point. Whenever we needed something, he was quick to respond and provide appropriate resources and training.
The support, when necessary, is excellent. But beyond that, it is very rarely necessary because the user community is so large, vibrant and knowledgable, a simple Google query or forum question can answer almost everything you want to know. You can also get prewritten script tasks with a variety of functionality that saves a lot of time.
The implementation may be different in each case, it is important to properly analyze all the existing infrastructure to understand the kind of work needed, the type of software used and the compatibility between these, the features that you want to exploit, to understand what is possible and which ones require integration with third-party tools
We work with multiple platforms, not solely DataXu. As of late, AdWords has proven more beneficial to us. AdWords is very user-friendly and they are easy to contact. If we need a question answered, we can simply hop onto a Google Chat and get the responses we need to move forward. DataXu is much harder to get in contact with and their Help Beta tab is not especially informative. If we need to serve impressions, DataXu is certainly the server to utilize
I think SQL Server Integration Services is better suited for on-premises data movement and ADF is more suited for the cloud. Though ADF has more connectors, SQL Server Integration Services is more robust and has better functionality just because it has been around much longer
Without this, we would have to manually update a spreadsheet of our SQL Server inventory
We would also have poor alerting; if an instance was down we wouldn't know until it was reported by a user
We only have one other person who uses SQL Server Integration Services , he's the expert. It would fall to me without him and I would not enjoy being responsible for it.