2019-07-29T10:11:00Z

What advice do you have for others considering Azure Data Factory?


If you were talking to someone whose organization is considering Azure Data Factory, what would you say?

How would you rate it and why? Any other tips or advice?

Guest
99 Answers

author avatar
Top 5Real User

Within the next six months, we are planning to enter into the machine learning part of this solution. This is a product that I can recommend. I would rate this solution an eight out of ten.

2020-01-12T12:03:00Z
author avatar
Top 10Real User

The advice that I would give to someone considering this solution is to have some background in data warehousing and ETL concepts. Have the background about data warehousing and ETL that extract, transform, and load. If you have the background you need, you will be successful. If not, then my advice would be to learn a little more about it before using Data Factory. I would rate Data Factory as an eight out of ten.

2019-12-31T09:39:00Z
author avatar
Top 10Real User

We have nine people using Azure Data Factory. On a scale of one to ten, I give it an eight.

2019-12-23T07:05:00Z
author avatar
Top 10Real User

The advice I would give to someone who is looking to implement this product is to understand the IT technology of the product first and why it would be needed. That is the point where you have to start. Next, you have to understand if the product itself fits your organizational needs. That is you have to look at the business requirements and see whether the product really fits the organization and solves the problems while conforming to the business model. On a scale from one to ten where one is the worst and ten is the best, I would rate the product overall as an eight-out-of-ten.

2019-12-16T08:14:00Z
author avatar
Top 5Real User

My advice for anybody who is implementing this solution is to first get in touch with the Microsoft team to get their support so that you don't spend too much on research. I would rate this solution a seven out of ten.

2019-12-12T07:48:00Z
author avatar
Consultant

We use the public cloud deployment model. I'd warn others to ensure that the design should be frozen before you start building because overriding each other's code and managing code takes effort. To avoid or to reduce that effort, ensure that the design is frozen. You can build some configurable code rather than hard-coding everything into the jobs. That's the biggest recommendation. I'd rate the solution seven out of ten. It's a pretty good solution, but over the past year, I've been limited on the number of cases I have on it. If it had a better user interface and was more intuitive I would have rated it higher.

2019-12-09T10:58:00Z
author avatar
Top 10Consultant

We primarily use the solution in a hybrid environment. We're Azure partners. I would suggest others start with a small POC and with a smaller dataset or simple pipeline to test the product before fully implementing it. Users shouldn't hesitate to try it, because there are not so many risks. Practice is the best way to start with this service, as opposed to planning. I'd rate the solution eight out of ten.

2019-12-05T11:14:00Z
author avatar
Top 10Real User

We use both the on-premises and cloud deployment models. We typically work with enterprise-level companies. Azure Data Factory is pretty good but should be considered as an orchestrator, not as an integrated tool. We can use some building components in that tool to orchestrate the entire workflow but if we are thinking about more details, processing, or data modification during the flow, we'd have to consider Azure Databricks or Data Flow for making those calculations or changes. Users will need Azure Data Factory plus third party tools to reach that level of functionally. I would recommend using Data Factory. I don't have a lot of experience with integration or with integration services, for example, SQL server integration services. However, there are points that should be considered if you are already using SQL server integration services already. You can implement the packages already prepared in Azure Data Factory. It's something that needs to be considered when deciding which technology you are going to use. I'd rate the solution eight out of ten.

2019-11-18T07:22:00Z
author avatar
Top 20Consultant

I don't use Azure Data Factory for my own company; I help clients implement the solution for their companies. In terms of advice that I would give to others looking to implement the solution, I would say you have to learn. You have to really understand the overall concept. It does not allow you to just click and go. I would rate this solution ten out of ten.

2019-07-29T10:11:00Z
Learn what your peers think about Azure Data Factory. Get advice and tips from experienced pros sharing their opinions. Updated: April 2020.
442,283 professionals have used our research since 2012.