We performed a comparison between SQL Server and Teradata based on our users’ reviews in five categories. After reading all of the collected data, you can find our conclusion below.
Comparison Results: Because Teradata is more expensive, has harder initial setup, harder scalability, and fewer features, SQL Server ultimately wins out in this comparison.
"It is quite reliable in cluster configurations and has helped me to reduce downtime and improve SLAs."
"The solution is very intuitive and easy to use."
"We have many users, between 50 and 100 using the SQL Server product."
"We've found it to basically be pretty problem-free."
"The scalability is very good."
"The tool helps us by being available always."
"The installation is pretty straightforward."
"SQL Server is essentially the backbone of every microservice. From a developer's perspective, it is the backbone of all microservices. The tool enables data retrieval, set data, and essential operations, ensuring the smooth functioning of applications. In essence, it is the integral part that keeps applications operational."
"The ability to handle machine data parallel processing is the most valuable feature of Teradata."
"It effectively has allowed us to remove over 20 portion copies of the data sets on other DB platforms for real-time operational reporting purposes."
"The solution scales well on the cloud."
"It has massive parallel processing ability to do large amounts of concurrent querying."
"It's the same as your visual database. I like the fast load feature for data, the BTQ solution is very good, and storage procedures are very fast."
"It has reduced a lot of reworking on maintaining indexes, partitions, etc."
"The most valuable feature of Teradata is the quick processing of large data."
"The key advantages are Performance when processing Terabytes of data and scalability."
"The price could be better. In the next release, it would be better if the database was more easily extendable."
"In the next releases, I would only like more enhanced backups and more restore points."
"The performance could be better."
"Its ability to handle certain kinds of large data could be improved."
"Technical support could be faster."
"On the SQL Server Management Studio (SSMS) side, I have noticed more bugs in terms of being able to connect to our SQL servers. I can't tell how many times my recent server list got dropped or cleaned out. It is a pain, and it would be nice to have that recent connect list when you connect in. For whatever reason, once in a while, I get a hard error, and it'll close. When I go back in, everything is cleared out. It is annoying when you are working with more than a hundred database instances."
"We experience latency at times when there is a lot of data being processed."
"One stability issue I encountered was the deadlocking between calls to the same resources (tables, etc.). That was solved by row versioning."
"Sometimes the large injestion takes days to load data, and some of our stored procedures take two to three days."
"The user interface needs to be improved."
"Teradata could improve by being less complicated. There are some aspects that are not available on the Unix server and a Unix system is required to access some data, such as in case of an emergency."
"Since I was working on the very basic, legacy systems, the memory thing was always a challenge. If Teradata is moving to the cloud, the space constraint or the memory issue that my company generally faces will eventually resolve, in time. What I'd like to see in the next release of Teradata is that it becomes full-fledged on the cloud, apart from better connectivity to various systems. For example, if I have to read or include a Python script, if I write some basic codes, I should be able to read even unstructured data. I know that it's not supported even in Snowflake, but at least semi-structured data support, if that can be a little more enhanced, that would be good."
"The SQL Assistant is very basic. This tool can be improved for usability."
"Teradata should focus on functionality for building predictive models because, in that regard, it can definitely improve."
"I would like to see an improved Knowledge Base on the web."
"Teradata's UI could be more user-friendly."
SQL Server is ranked 1st in Relational Databases Tools with 260 reviews while Teradata is ranked 7th in Relational Databases Tools with 54 reviews. SQL Server is rated 8.4, while Teradata is rated 8.2. The top reviewer of SQL Server writes "Easy to use and provides good speed and data recovery". On the other hand, the top reviewer of Teradata writes "Offers seamless integration capabilities and performance optimization features, including extensive indexing and advanced tuning capabilities". SQL Server is most compared with MariaDB, SAP HANA, Oracle Database, LocalDB and Amazon Aurora, whereas Teradata is most compared with Snowflake, Oracle Exadata, MySQL, BigQuery and IBM Db2 Database. See our SQL Server vs. Teradata report.
See our list of best Relational Databases Tools vendors.
We monitor all Relational Databases Tools reviews to prevent fraudulent reviews and keep review quality high. We do not post reviews by company employees or direct competitors. We validate each review for authenticity via cross-reference with LinkedIn, and personal follow-up with the reviewer when necessary.