We have been using SQL Server for more than 10 or 15 years.
Technical Systems Support Manager at a hospitality company with 201-500 employees
Has a reliable database
Pros and Cons
- "The solution has a reliable database."
- "Microsoft support is an issue unto itself."
For how long have I used the solution?
How are customer service and support?
Microsoft support is an issue unto itself. We mainly benefit from common support, such as a forum or Microsoft support, of which I don't have that much experience.
Which solution did I use previously and why did I switch?
As with Oracle Database, the solution has a reliable database. I do not see much difference between the two when it comes to usage and the program decision to use one solution over another varies with the appropriateness of a given product, some utilizing Oracle, others Scale.
What other advice do I have?
I am an SQL partner.
As with Oracle, SQL Server is deployed on private cloud.
I rate SQL Server as a nine out of ten.
Buyer's Guide
SQL Server
October 2024
Learn what your peers think about SQL Server. Get advice and tips from experienced pros sharing their opinions. Updated: October 2024.
816,406 professionals have used our research since 2012.
Which deployment model are you using for this solution?
Private Cloud
Disclosure: I am a real user, and this review is based on my own experience and opinions.
Sr. Solution Architect at a computer software company with 5,001-10,000 employees
Easy-to-use interface for building queries
Pros and Cons
- "The interface for building the queries or writing the store procedures is good."
- "Additional interfaces would be an improvement."
What is our primary use case?
SQL Server is the database for the transactional database that is being used.
The solution can be used for the BI, the data warehouse part as well, but mostly I have seen it used for the transaction data being stored by the DBMS part of it.
What is most valuable?
The solution is very easy to use, because even the technical engineers that we get are able to use it more efficiently. I like the programming interface they have where they help us get the table names that we are dealing with, and the field names in that particular table.
The interface for building the queries or writing the store procedures is good.
What needs improvement?
If I compare the solution with current technology needs, like NoSQL, that have been prevailing now, they could improve it so there could be a single solution, where we could deal with a single database for both transactional as well as for the in-memory needs that we have.
For the integration part, additional interfaces would be an improvement. If SQL Server could expose certain APIs or certain interfaces which can be used for integration with the warehouse solution, then it would be great.
What do I think about the stability of the solution?
The solution is stable.
What do I think about the scalability of the solution?
The solution is scalable.
How was the initial setup?
The team needed for implementing the solution depends on the project size and functionalities needed. But as far as the DB administrator, generally, we use a single resource for each project. One database engineer is sufficient for optimizing the query or indexes or building any database scripts.
What other advice do I have?
I would rate the solution an eight out of ten.
Which deployment model are you using for this solution?
On-premises
Disclosure: My company has a business relationship with this vendor other than being a customer: Partner
Buyer's Guide
SQL Server
October 2024
Learn what your peers think about SQL Server. Get advice and tips from experienced pros sharing their opinions. Updated: October 2024.
816,406 professionals have used our research since 2012.
Senior Digital Services Engineer at a pharma/biotech company with 1,001-5,000 employees
Configurable, stable, and scalable
Pros and Cons
- "The solution is configurable."
- "The integration could be better. They are not open-source, so the integration with other platforms is not that easy."
What is our primary use case?
We only use it as a logging solution. We use it as logging for processing our database. It holds records for some systems and so on. That's it.
What is most valuable?
The solution is stable.
The product is scalable.
The solution is configurable.
What needs improvement?
The IT and digital transformation department are a bit fresh in this company that I am working for. They have a lot of plans, a lot of visions. I don't know how are they are going to do the infrastructure. I don't know their vision.
So far, the solution fits the scope of our company. We aren't missing any features.
The integration could be better. They are not open-source, so the integration with other platforms is not that easy.
For how long have I used the solution?
The company has been using them for a long time. I newly joined the company two months ago, so I don't know when exactly they start using it.
What do I think about the stability of the solution?
The solution is very stable. There are no bugs or glitches. It doesn't crash or freeze.
What do I think about the scalability of the solution?
You can scale the product. You can increase and decrease the storage as needed. It's very easy.
The amount of users on the solution is anywhere between 1,000 and 2,000 users.
How are customer service and technical support?
While I've never been in touch with technical support, the administration team has. They've contacted the team in Egypt. I haven't heard of any negative experiences.
Which solution did I use previously and why did I switch?
I've also worked with Oracle in the past. At this company, since it is an older server, it may have been in service longer. We were using the two databases for two different functions.
How was the initial setup?
I wasn't a part of the installation process, however, it's my understanding that the company handled the installation themselves.
The administration team has three or four team members. They can handle maintenance tasks and rotate tasks between themselves.
What about the implementation team?
My understanding is that the company handled the installation internally. However, I was only recently hired.
What's my experience with pricing, setup cost, and licensing?
Any kind of information related to costs or licensing is beyond my scope. I don't deal with that aspect of the solution. I do not know if licensing is paid monthly or yearly.
What other advice do I have?
We are customers and end-users.
Our architecture is divided. There are parts on-premise and parts on Azure cloud. I don't know exactly where the SQL Server sits.
I'd rate the solution at a nine out of ten.
I might recommend it to other organizations. That said, it depends on the solution they need. I've worked on Oracle, I have worked on my Microsoft SQL servers. What would be best depends on the solution they need. However, Microsoft SQL servers are a very trusted product. I would recommend it if someone was asking about it.
Disclosure: I am a real user, and this review is based on my own experience and opinions.
Senior Manager at a financial services firm with 201-500 employees
Easy to manage with good stability and knowledgable technical support
Pros and Cons
- "The solution is easy to set up."
- "The configuration process can be a little complex."
What is most valuable?
We find the Microsoft SQL Server affordable compared to its real competitors.
We find it easy to manage.
It offers a very robust infrastructure for us.
The solution is easy to set up.
We have found the stability to be good.
We've had a good experience with technical support. They are helpful.
What needs improvement?
We may use different levels of SQL Server when it comes to licensing. We have some Enterprise and some Standard services. They can improve the recovery processes of the replication or disaster recovery scenarios for the lower-tiered version, such as the Standard server.
While we have many options in Enterprise, it's expensive for most companies.
The configuration process can be a little complex.
Technical support can take a while to respond in Turkey.
The solution may be better with some integration with some factory cloud software. With the standard version, the lodgement process is never enough. We are replicating near real-time to make recovery easy and to make all the RPO targets as expected.
You cannot recover SQL Servers, especially for big financial companies like ours. It's not easy to erect SQL Servers on any other site, and with an acceptable data loss in the foundations.
For how long have I used the solution?
Personally, I have used the solution for about 15 years at this point. It's well over a decade. I've used it for a while.
What do I think about the stability of the solution?
The stability has been great. There are no bugs or glitches. It doesn't crash or freeze. it's reliable.
How are customer service and technical support?
The Microsoft team never responds fast in Turkey. I cannot say they are fast. Unless you have some Enterprise agreement, they're not quick. However, I find that when I deal with the same technician a few times, they are quite good and very helpful. They are very capable. They know what they are talking about.
Which solution did I use previously and why did I switch?
We also use Oracle Servers.
How was the initial setup?
The initial implementation is easy and straightforward. It's not overly complex or difficult to set up.
However, it's not just the server we have to set up. We have a cluster environment. Mostly it's just, click, click, click and you are done, however, the configuration process is a bit more difficult. Adjusting performance levels, in particular, can be a real challenge.
What's my experience with pricing, setup cost, and licensing?
The enterprise version of the solution is very expensive and most companies would likely find that they wouldn't be able to afford it.
What other advice do I have?
We're a customer and an end-user.
I'd rate the solution at a nine out of ten. We've been very happy with its capabilities.
I would recommend the solution, however, it will only be effective if the company hires an effective administrator. While there are default settings, you will likely need to configure quite a bit and connect most of your hardware in the correct way. To be effective, it really needs to be tuned by a professional.
Disclosure: I am a real user, and this review is based on my own experience and opinions.
Information Security Manager at a financial services firm with 501-1,000 employees
Good for publishing web applications, but security, stability and performance can be improved
Pros and Cons
- "We have found the feature that allows us to publish web applications to be valuable."
- "As we have faced problems with the solution in both the past and present, I feel it could be more stable."
What is our primary use case?
We use the solution for nearly all of the services we provide that utilize Windows Server. We use it to provide continuous service and in respects of our mail server.
What is most valuable?
We have found the feature that allows us to publish web applications to be valuable.
We have 20 servers and we use disparate ones for different applications, such as Kaspersky Anti-Virus Server and Windows SharePoint in respects of the surveillance system.
What needs improvement?
The solution should be more secure and stable and have better performance, particularly as concerns the endpoint operating systems. I would like to have a better operating system that links the CPU and the RAM efficiently.
For the majority of our servers we have not used other operating systems, although there are certain features or requirements that necessitated their use, such as Red Hat. This was rare. Mostly, we used Windows OS.
As for the performance issue, we have recently encountered situations in which everything would fail in spite of the CPU and memory being 100 percent operable.
For how long have I used the solution?
We have been using SQL Server for 12 or 13 years.
What do I think about the stability of the solution?
As we have faced problems with the solution in both the past and present, I feel it could be more stable.
What do I think about the scalability of the solution?
The solution seems scalable to me.
How are customer service and technical support?
We have not had experience with technical support and have handled this independently whenever we encountered problems.
How was the initial setup?
When it comes to the installation of the operating system, we have found it to be easy and user-friendly.
Our greatest praise for the solution we reserve for its ease of installation and usage. These provide definite advantages. Perhaps this can be attributed to the fact that we have always made use of the solution for nearly every relevant company in South Africa.
While I cannot recall exactly how long the installation lasted, I did recently install endpoint Windows 10 Operating System and this took an hour and a half.
We were able to handle the installation on our own, as we are well versed in this process when it comes to Windows OS.
On an individual basis, we solely make use of Windows OS. There are between 300 and 400 people in our organization who do so.
Generally speaking, we do not make use of a technical team for deployment and maintenance purposes and do so internally. There are a maximum of seven or eight people in our organization who are responsible for this. We are talking about technical people who are responsible for the direct installation and configuration of Windows OS and they do not include managers.
What's my experience with pricing, setup cost, and licensing?
I believe the licensing to be on an annual basis. In 2019 we purchased a three year license.
Which other solutions did I evaluate?
We did not evaluate other other options before going with the solution.
What other advice do I have?
I rate SQL Server as a seven out of ten.
Disclosure: I am a real user, and this review is based on my own experience and opinions.
IT Assistant at Hotel 2 Fevrier
has an efficient configuration but is not sufficiently scalable in size for simultaneous connections
Pros and Cons
- "The initial setup is time-efficient and can be done independently."
- "As SQL server could not support the number of connections we desired, we were forced to go with Oracle."
What is our primary use case?
We use SQL Server with Sage products.
It is used by our finance team and also human resources.
What is most valuable?
the database management tool is very easy to use and largely meets expectations
What needs improvement?
As SQL Server could not support the number of connections we desired, we were forced to go with Oracle. This is an area that needs to be improved.
For how long have I used the solution?
for 04 Years now
What do I think about the stability of the solution?
The solution could be more stable
What do I think about the scalability of the solution?
The performance in terms of simultaneous connection must be reviewed.
How are customer service and technical support?
We do not pay for technical support.
Which solution did I use previously and why did I switch?
No
How was the initial setup?
The initial setup is time-efficient and can be done independently.
There is no need for developers or managers to deploy and maintain the solution. One or two systems' administrators are sufficient for its deployment.
The deployment is on-premises. We installed the solution on a server and this on the Windows server. The user is provided an application for connecting to it.
What was our ROI?
great
What's my experience with pricing, setup cost, and licensing?
The licensing involves a one-time fee.
Which other solutions did I evaluate?
We evaluated Oracle as an alternative.
What other advice do I have?
For my part, SQL Server is aimed at small and medium-sized businesses, I would give it an eight out of ten.
I would not recommend it for a large company that has to support more than 40 simultaneous bi-directional connections to the database
Which deployment model are you using for this solution?
On-premises
Disclosure: I am a real user, and this review is based on my own experience and opinions.
Computer engineering student at a educational organization with 501-1,000 employees
Stable with good technical support and integrates well with Visual Studio
Pros and Cons
- "The most valuable aspect of the solution is that it's integrated with the Visual Studio and also with Microsoft SQL Server Management Studio. It's a tool they have and it's quite easy to use and understand. It's the interface for programming for SQL Services."
- "The solution could be better integrated with the SQL Server Studio tool."
What is our primary use case?
I primarily use the solution for the development of various applications, database connections, that I need for projects.
I just use it myself, for assignments. I am a student and am studying the product.
What is most valuable?
The most valuable aspect of the solution is that it's integrated with the Visual Studio and also with Microsoft SQL Server Management Studio. It's a tool they have and it's quite easy to use and understand. It's the interface for programming for SQL Services.
The solution is very stable.
The solution scales well.
The initial setup is straightforward.
What needs improvement?
I don't have a deep technical knowledge of the solution. It's hard to discuss features that may be lacking.
The solution could be better integrated with the SQL Server Studio tool.
There are some complexities with the initial setup sometimes as there are a lot of options.
For how long have I used the solution?
I've been using the solution for two years at this point.
What do I think about the stability of the solution?
The solution is very stable. There are no bugs or glitches. It doesn't crash or freeze. It's reliable in terms of performance.
What do I think about the scalability of the solution?
The solution can scale. If a company needs to expand it, it can do so.
As a student, I don't yet have plans to increase usage of the product.
How are customer service and technical support?
I've been in touch with technical support. I contact them to assist with a bug that I detected, that was not really related to SQL Server. It was, however, related to another tool, the Microsoft SQL Server Studio. They responded quickly. I was quite satisfied with their level of support for the most part.
Which solution did I use previously and why did I switch?
I've also worked with PostgreSQL, and MySQL as well as MongoDB. I found that, in comparison, PostgreSQL was not as easy to use.
How was the initial setup?
The initial setup was pretty straightforward. It's very similar to other software products. The Visual Studio is easier, however, it's still mostly straightforward. It could be better integrated with this SQL Server Studio tool. You have to install it separately. If they could be installed together, that would be an improvement in my opinion. While not everyone would use it, the developer would find it a helpful item to have.
It can sometimes be confusing to install by yourself since it does have many options that you need to decide on.
What about the implementation team?
I was able to install the solution myself. I did not need the assistance of an integrator or consultant.
What's my experience with pricing, setup cost, and licensing?
You do need to pay for a license in order to use the product.
What other advice do I have?
I'm just an end-user.
I'd rate the solution at a nine out of ten. I'm mostly happy with its capabilities.
I'd recommend the solution to other users. It's a solution that is nice and standardized. We are learning all about it at school and its industry standards make it a good option.
Which deployment model are you using for this solution?
On-premises
Disclosure: I am a real user, and this review is based on my own experience and opinions.
Associate Manager at a consultancy with 501-1,000 employees
Provides great CDC mechanism for adding data incrementally; simple installation
Pros and Cons
- "A big advantage is the ability to store any type of data in SQL Server."
- "Performance could be improved."
What is our primary use case?
We use SQL Server to import data from different source systems. Depending on requirements, you act as the resource and can schedule jobs in the Azure environment. The server can be stopped when not required so there's no cost when it's not being used. We make use of the pipeline to put the data into the SQL Azure environment and extract it to the server. I'm the associate manager.
What is most valuable?
The best feature in SQL Server is the CDC mechanism for adding data incrementally. Another good feature is the ability to store any type of data in SQL Server, it's a big advantage.
What needs improvement?
You need to be careful if you have a very large amount of data, because the platform can be degraded if you're not on top of it. Oracle handles that issue better and it's the main problem I have with SQL Server. The performance should be better.
What do I think about the stability of the solution?
This is a stable product.
What do I think about the scalability of the solution?
This product is scalable, we have between 20 and 30 users in our company. We'll continue to use this product.
How are customer service and technical support?
We haven't needed to contact technical support. If there is an issue we use the different SQL forums and we can easily fix issues.
How was the initial setup?
The initial setup is straightforward, you can install with basic knowledge. Installation doesn't take long at all, I did it myself.
What's my experience with pricing, setup cost, and licensing?
There are no annual licensing fees, you pay when you use the product.
What other advice do I have?
I rate this solution a nine out of 10.
Which deployment model are you using for this solution?
Public Cloud
Disclosure: I am a real user, and this review is based on my own experience and opinions.
Buyer's Guide
Download our free SQL Server Report and get advice and tips from experienced pros
sharing their opinions.
Updated: October 2024
Product Categories
Relational Databases ToolsPopular Comparisons
MySQL
Oracle Database
Teradata
MariaDB
SAP HANA
IBM Db2 Database
Amazon Aurora
CockroachDB
LocalDB
IBM Informix
Oracle Database In-Memory
Citus Data
YugabyteDB
SAP IQ
SAP SQL Anywhere
Buyer's Guide
Download our free SQL Server Report and get advice and tips from experienced pros
sharing their opinions.
Quick Links
Learn More: Questions:
- Microsoft sql2017 VS SAP Hana
- SQL Server 2005 vs. InfoBright - what are the pros and cons of these solutions?
- SQL Server 2012 - can I make OLTP transactions from my ERP run in memory?
- How does NuoDB compare to MySQL and SQL Server?
- What are the main architectural differences between Microsoft SQL Server and Oracle Multitenant?
- Would you say the price of SQL Server is high compared to that of similar products?
- Has using SQL Server helped your organization in any way?
- Which authentication mode is best for SQL Server?
- Which solution do you prefer: Microsoft SQL Server's enterprise edition or Oracle Database's enterprise edition?
- Which is better: SQL Server or SAP HANA?