The setup of SAP Data Services is straightforward for me because I have been doing it for over 12 years. I did a lot of internal implementation of SAP, HANA, and SAP Data Services. I have become familiar and comfortable. It is easy for me.

The initial setup process is not complex. You need to understand the modeling part. If you understand what a database is and what tables and columns are, it is easy to handle.

There are three kinds of deployments. So, we can deploy it export and import-wise. Or we can use a central repository. Through the central repository, we can export and import. Also, through XML files, we can export and import within an environment.

The time taken for deployment depends on how many kinds of modeling one has done, including how many tables one has extracted. It also includes how many tables one has loaded, apart from what kind of integrations and joining one has done. So, we can't tell the time. The time is based on how big of a system you have given the OLTP.

For deployment, only a developer person is needed. One person is enough to deploy all the tools. The development people will be there, but one person is enough to deploy everything.

The solution is deployed on-premises. The cloud version's name is a different name, SAP HANA Data Warehousing.

Regarding the maintenance part, there is not much maintenance needed because it's an ETL, so batch tools and stream nodes will be there. There's not much maintenance needed.

The initial setup is very easy. It takes about a day for implementation and setup. 

You only need one person to handle deployment and maintenance tasks.

Setting up Data Services is moderately complex. It's a big tool with a lot of components that need to be configured. Data Services is an enterprise-level data extraction and transformation load tool. There are just a lot of pieces. We've struggled because we were trying to install it on Solaris. I just finished an upgrade. I set up our environment five years ago, and we just upgraded it again. 

It took much longer because they didn't have good support for Solaris. They say that they support Solaris, but they really don't. Since we moved over to Linux, we've been a lot better off. But it's a pretty sizable effort to set up the tool and configure it. You have to have DevTest and PRIDE. There are a lot of moving parts and various repository job servers. You have to understand the topology and architecture of the tool to know how to install and configure it. It's not like installing Microsoft Word.

The total amount of time needed to deploy depends on your environment. Generally, it should take about a month to get it up and running. In actuality, it took a lot longer than that. But once we got on the right OS, it was quicker. Our deployment strategy was to have three instances of the tool. First, we have DevTest and PRIDE. Then each developer has their own repository where they can do their work. So we have a development, test, and production repository. Every developer first runs their code in their own repository, which is where your code is stored. The code is then promoted to a common dev area. After that, it goes to a common test area, and finally, it heads to a common production area.

We've deployed Data Services several times, and each time we've had to do a net new install and transfer things over. We ran into some limitations on being able to upgrade in place. We have one person managing and maintaining the solution, but that person's workload fluctuates. It can be very demanding at times. It can use a lot of one person's time for short periods when you do upgrades. You have to know how to get onto SAP's website, open tickets, and work with SAP Support. That's another thing that adds to the time of the deployment. The amount of time you spend with SAP support is non-trivial. You have to understand the ticketing system and how to contact the engineers. It takes a little while to get used to that.

The initial setup is simple. However, the complexity can increase if there is a need for collaboration with other teams, such as database administrators and security personnel. It takes a few days to complete the process.

The initial setup process could be user-friendly. It would take two to three hours to complete for a new executive.

The product's initial setup phase is neither difficult nor easy, so I can describe it as a medium process.

The solution is deployed on the cloud services offered by Azure.

The solution can be deployed in a few weeks.

My company is still looking into and analyzing to figure out how many people are actually required for the deployment process.

The setup process is not very complicated, and the integration is also straightforward. Connecting to systems and using prebuilt extractors through interfaces make it easier. So the setup is not very complicated.

Only one or two people are required from a system maintenance perspective because there aren't many technical problems. Additionally, there are four people dedicated to technical development. So, in total, it's less than five or six people handling the technical aspects.

The initial setup is simple and takes a week to complete.

We need an additional resource for deployment because one person handles administration and technical data migration.

It is easy to initially set up. If we do have questions, we're always able to reach out to them to get support.

The implementation timelines depend on the customer. Sometimes clients know what they want to do quickly. Others are more slow and steady and take their time. 

The initial setup of SAP Data Services is easy. The length of time it takes for the implementation depends on the tool you use. If you use the desktop tool it should not take long.

For myself, I find the initial setup quite simple. However, I have many years under my belt working directly with the product. Someone with beginner-level knowledge might find it a bit challenging. In general, however, it's easy, not difficult.

The length of deployment depends on the organization and requirements. It does take a few days, but some projects are longer than others. It really depends on the client's needs. Each situation is unique.

The initial setup is not straightforward. You need experience with data services, and if you're upgrading or migrating, you'll need a consultant to help. A brand-new installation takes a day or two, but migration will take longer. However, one good thing is that SAP provides the white papers for their products on their website, so you can find the installation guides there.

The ease of setup depends on the systems you're connecting to. If I'm just forming a data store with say any database it's easy. However, if I'm forming it with any of the SAP systems targeting S4 or above, it's slightly complex and takes some time. There are also a lot of authorizations required and due to all that it's not a thing for an individual person to just pass through. That said, on a technical level, it is still relatively easy if you do receive all the required inputs.

The level of maintenance needed is always dependent on the projects and the amount of data that you're getting. Supposedly if you're giving me ten to 20 million records, my application issues I've stabilized. Data is going fine, and one person can support it if he has a bit of knowledge (somewhere around two to three years working with SAP). However, if it is much more dynamic and still there is a lot of junk data coming in, corrections are needed. In that case, a team of seven or even eight members will not suffice. I've worked once in a team of 40 members and it took us close to four years to stabilize the entire application. 

The initial setup of this solution was very complex. The process requires multiple steps, but there is very limited documentation available to aid the implementation tasks. This results in deployment being very slow.

The solution was implemented prior to my joining the company. We do upgrades and implement some small changes. Unfortunately, this can take some time and is not as easy as it should be. Deployment could be improved. We have a team of four people maintaining Data Services. 

The initial setup is very straightforward. It's not too complex.

You need some specialized knowledge about SAP tools before the setup. 

Just last week we installed data services to impact data sharing in one of the bigger companies we work for and from an implementation point of view, the ease of setup is okay, I believe.

To be honest, because of the economic situation we are in we always install on-premises. This is because of the Turkish market and some telecom companies aren't quite ready to elect to deploy on the cloud. So the business environment here is not ready yet.

The initial deployment is usually easy if you have one machine/one box deployed. However, if you have a network in which there are several job servers, then it is a little bit complex.

The maintenance is not complex. One morning session is enough to upgrade the tool itself.

The initial setup was straightforward and easy to complete.

I think it is easy to use. When we started to use it we had never worked with Dataservices and we could adapt to it easily because the main functions are similar to other tools.

The product is simple to setup. If you are setting it up on Windows, then it's a matter of a few clicks. 

The solution is straightforward to set up. A lot of research needs to go into the work, however. A standard deployment takes a few months.

Initial setup is rather complex. SAP Analytics requires integration with the rest of SAP models. We are the final link in the chain of implementation of SAP technology so some customers could do with external assistance. It really depends on the client's internal culture and skills. It helps to have a consultant and in some cases it's crucial. 

I was not directly involved at the initial setup.

The initial setup is complex. It takes time to get used to.

Straightforward. You just have to follow the guides, check Product Availability Matrix (PAM) and if issues related to sources and targets arise do some research.

I wasn't part of the initial setup, so I can't speak directly to the implementation of the solution.

Data Services itself, none. The must difficult (kind of) ids to setup the databases connectivity for sources and targets.

Initial setup was fairly simple.

It is straightforward.

Wasn't personally involved, but was straightforward for the development environment. Production was more complex.

It was quite straightforward for me as I had experience with other ETL tools and the concepts.

Straight forward.

The initial setup was straightforward and took about a day.

Setup was straightforward, but the customization and implementation process was complex.

It was already setup on the client system. I used it just for ETL purpose.