Azure Data Factory vs DBamp comparison

"We haven't had any issues connecting it to other products."

"When it comes to our business requirements, this solution has worked well for us. However, we have not stretched it to the limit."

"The most valuable feature of Azure Data Factory is that it has a good combination of flexibility, fine-tuning, automation, and good monitoring."

"Microsoft supported us when we planned to provision Azure Data Factory over a private link. As a result, we received excellent support from Microsoft."

"It is a complete ETL Solution."

"We use the solution to move data from on-premises to the cloud."

"The platform excels in data transformation with its user-friendly interface and robust monitoring capabilities, making ETL processes seamless."

"What I like best about Azure Data Factory is that it allows you to create pipelines, specifically ETL pipelines. I also like that Azure Data Factory has connectors and solves most of my company's problems."

"DBM allows integration with SQL Server, which is beneficial for Microsoft."

"Their support is good, very responsive despite being overseas."

"Azure Data Factory should be cheaper to move data to a data center abroad for calamities in case of disasters."

"The main challenge with implementing Azure Data Factory is that it processes data in batches, not near real-time. To achieve near real-time processing, we need to schedule updates more frequently, which can be an issue. Its interface needs to be lighter."

"The initial setup is not very straightforward."

"There aren't many third-party extensions or plugins available in the solution."

"The solution should offer better integration with Azure machine learning. We should be able to embed the cognitive services from Microsoft, for example as a web API. It should allow us to embed Azure machine learning in a more user-friendly way."

"There is always room to improve. There should be good examples of use that, of course, customers aren't always willing to share. It is Catch-22. It would help the user base if everybody had really good examples of deployments that worked, but when you ask people to put out their good deployments, which also includes me, you usually got, "No, I'm not going to do that." They don't have enough good examples. Microsoft probably just needs to pay one of their partners to build 20 or 30 examples of functional Data Factories and then share them as a user base."

"I do not have any notes for improvement."

"The need to work more on developing out-of-the-box connectors for other products like Oracle, AWS, and others."

"DBM is a bit more complicated when compared to DataLoader, especially for more complex operations."

"DBM is a bit more complicated when compared to DataLoader, especially for more complex operations."

"It seems very low initially, but as the data grows, the solution’s bills grow exponentially."

"I am aware of the pricing of Azure Data Factory, but I prefer not to disclose specific details."

"The price is fair."

"My company is on a monthly subscription for Azure Data Factory, but it's more of a pay-as-you-go model where your monthly invoice depends on how many resources you use. On a scale of one to five, pricing for Azure Data Factory is a four. It's just the usage fees my company pays monthly."

"The solution's pricing is competitive."

"Our licensing fees are approximately 15,000 ($150 USD) per month."

"Data Factory is affordable."

"This is a cost-effective solution."