Setting up Teradata took time. The server has to be set up and that takes time. Next, the IDs need to be set up and the role level security that the legacy system provides is definitely not up to the mark when compared to the cloud, so that is a concern. I'm talking truly about the legacy system. I haven't worked on the cloud part of it. It took more time to deploy Teradata.

Deploying the solution from dev to the QA environment, for example, creating tables, then copying over the data, are completed within twenty four to forty eight hours. It's the timeframe the DBA used to give, which is pretty high. With the closing features that we have normally, that would be a long time.

It's not straightforward. You must know what you're doing. If you don't feed the data in correctly, it's read like bad data, bad performance. We've seen a couple of times where we've done an investigation to understand why some of the queries are slow, and then we found out that the programmers made a mistake in the way that they've created the data or the query and that was causing the problems on Teradata. 

We've seen this a couple of times. You can't be an IBM person and think you can become a programmer for Teradata. It's two different systems, and we've seen it several times. You have to know what you're doing when you do it, especially on the analytics side of Teradata.

To deploy Teradata, it takes a lot of pre-planning. It can take anywhere from two to four months. It all depends. There's a lot of stuff, actually, for the pre-planning phase, and that's one of the most important things. You have to do a lot of homework before you actually replace the system or you migrate the system. There's lots of planning that you have to put in place before you do that. YOu need a minimum of two to four months.

For the customer CS support for the hardware and software support, we had around about six engineers that were supporting all six systems and we had three people off-site.

The initial setup was straightforward.

The initial setup is straightforward. The deployment time is contingent upon the scale of the migration and moving from a lower to a higher environment is not a challenging task. The time it takes to migrate the data is also dependent on the source database and what ETL tool we are using. Around two to three engineers and one architect are required for the deployment.

It's a very straightforward installation process. It's good in terms of installation.

I would rate the initial setup six out of ten when it comes to complexity.

The initial setup was fine but whenever we needed to increase the size and capacity, it would literally take a room full of people, a very coordinated effort and it was a huge project, in contrast to a product like Snowflake, where you literally just change the warehouse size and it auto-scales. So those types of things really hindered Teradata prem. 

It's not too complex. It's designed for huge amounts of data, and it's planned out well. As long as you follow some principles, it won't be too complicated. 

I've used the solution for more than a decade. It was a while since I deployed the solution. 

You start with business analysis and design the database structure from there. After that, you can start populating and developing. 

How many people you need for deployment or maintenance would depend on how big the implementation is. 

The initial setup of Teradata is complex. The business layers on top of Teradata add to the complexity. The way the business uses Teradata adds to the complexity that the software itself doesn't necessarily have. 

You can do an upgrade for Teradata in a couple of days. Deploying it is not difficult at all, nor is it time-consuming.

I rate the ease of setup for Teradata a one out of five.

The solution is not straightforward to set up. For example, if I target the users, the users need to install things and set up things up. Even the LDAP integration and all those things are not easy with respect to Teradata if I compare it with BigQuery, Snowflake, and Redshift.

If I want to spin off a new node or anything like that with Teradata, it's a bit tricky compared to other data warehouses where we can easily spin off new nodes and work on them.

Since our system is like a fixed system, when we did this deployment, it didn't take that much time. However, it was not easy. If I wanted to add additional load into the system, I needed to hand over the Teradata system to Teradata, and they had to do it, and that would take a day to do. Now, if I compare it with BigQuery or Snowflake, I can spin off new clusters without any issues. I can just add the number of nodes in that new warehouse, and I can run it. 

How long it takes to deploy depends on how big the system is. That said, compared to others, it definitely takes a little bit of extra time.

Since Teradata takes care of the implementation, I'm not sure how many people are ultimately involved in the deployment. From our side, we had two or three people involved in the setup. 

We have five to six admins to manage a 24/7 project.

The setup is complex and requires specialized people for implementation.

The initial setup was straightforward.

For the most part, the initial setup is good. We found it pretty straightforward. That said, sometimes, in the beginning, we struggle. 

For us, the deployment took around two hours. It didn't take too long. 

We had about ten members on the technical team that handled deployment and maintenance. 

I don't recall if the solution had a complex or straightforward setup. I wasn't part of the process.

The setup took place too long ago to remember.

The implementation took approximately one month.

Initial setup is quite straightforward, but previous experience with other databases tends to make it more difficult, because it takes a while until you get used to thinking in Teradata terms, rather than Oracle/SQL Server/PostgreSQL terms.

It’s a different animal. However, once you start thinking like a Teradata DBA, things are much easier.

For the on-premises deployment, a lot of people consider the initial setup to be difficult. Keep in mind, however, that Teradata is a million-dollar product, so they set it up for you.

For a cloud-based deployment, it is now pretty simple to deploy.

It was easy for me to set up since I didn't handle the setup. Our local support company managed everything and prepared the environment, and handed it over to us. It was very easy in that sense.

The initial setup is straightforward if you have some knowledge about the logic of the environment. However, for those without knowledge, there will be a learning curve to understand how to use the solution.

It's complex in terms of physical data modeling.

It was easy, the whole job was done by Teradata.

Teradata setup is straightforward and simple.

The setup was complex, but the work was outsourced to the Teradata Professional Services.

The initial setup is straightforward.

I would not say the setup is too complex. Teradata has a direct sales model, so Teradata employees usually set it up with help from the customer because they don't support a big system of resellers or partners. It's pretty easy because they are actively involved in the deployment. But later on, when the customer is expanding the solution and doing many things themselves, they make mistakes, which should be corrected using the support resources of Teradata.

I have never setup a Teradata box personally.

The initial setup of Teradata is not simple.

The initial setup is very easy.

Deployment takes a couple of weeks.

The initial setup was done with the free Teradata Express. I downloaded and installed it. The implementation process was not easy to do and there are many steps involved. Other data warehousing tools are plug-and-play. It is a three to four-step process.

We followed some useful YouTube videos.

I rate the initial setup of Teradata a five out of ten.

Complex. The process requires multiple meetings and all teams working together.

I cannot say for sure. We have not taken part in deployment activities. As it is an appliance, I expect it is a bit complex.

Done by Teradata PS.

It was straightforward.

There were a few ups and down with the initial setup but it's only one time during the initial phase.

Very complex.

Complex. My experience was the Teradata Solution Architects were less friendly and hid information and charged for simple things.