What is our primary use case?
Typically, the SQL Server is used in many, many ways. We primarily use SQL Server when there is a data requirement for our projects.
Typically there are uses around where you are creating a database. I've yet to store the data in our RPA server. We need MS Excel through Microsoft.
Any sort of RPA process where you require data through housing data or using a database, you need an SQL Server.
What is most valuable?
The solution is extremely stable. The performance is reliable.
The scalability of the solution is very good.
Technical support is pretty good. they are prompt in their responses.
What needs improvement?
You do need to have technical knowledge in order to install the solution. It's not something a layperson can do.
The scalability can always be improved.
For how long have I used the solution?
I've been using this solution for a number of years now. It's been a while. I have some experience with it.
Buyer's Guide
SQL Server
December 2024
Learn what your peers think about SQL Server. Get advice and tips from experienced pros sharing their opinions. Updated: December 2024.
831,369 professionals have used our research since 2012.
What do I think about the stability of the solution?
The stability of the product is very good. It's reliable. There are no bugs or glitches. It does not crash or freeze. It doesn't give us any trouble.
What do I think about the scalability of the solution?
The solution is very capable of scaling. A company should have no trouble expanding the solution as needed.
You can always add on to the server or make compartments into it.
We have a team of about 200 or more people using the solution.
We do plan to continue using the solution.
How are customer service and support?
We've dealt with technical support in the past. We found that their responses have been prompt. Given their engagement to typical organizations, they do decent work. I would say that we are mostly satisfied with the level of support on offer.
Which solution did I use previously and why did I switch?
We did not use any other databases prior to SQL. We only use SQL.
How was the initial setup?
The initial setup does take some time. It depends upon how you are establishing the server in your environment and depends upon the firewall of your organization. It is a lengthy process, however, it is not that grueling. Depending upon the firewall of your organization, it does take time. That influences the time.
What about the implementation team?
I can handle the installation myself. I did not need the help of a consultant or integrator. However, whoever installs it must be somebody who has the technical knowledge. Not everybody can do it.
What's my experience with pricing, setup cost, and licensing?
We have an organizational license.
What other advice do I have?
We are customers and end-users. We do not have a business relationship with SQL.
We are using the latest version of the solution. I cannot recall the exact version number.
I would recommend the solution to other users, companies, and organizations.
I'd rate the solution at an eight out of ten.
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.
I agree with the fact that the inclusion of AlwayOn tools (since SQL Server 2012) has somehow simplified the configuration of High Availability (HA) settings in SQL Server, in this sense, the HA part in HADR (High Availability - Disaster Recovery) is a little bit simpler than with previous versions of SQL Server.
But we have to realize that when you include an HA solution to an instance of SQL Server, you should previously conduct a proper analysis on HADR for said instance, and that analysis is more complex than a (simpler) Disaster Recovery Plan.
It will take more time to complete a proper HADR Plan for your instances at your site, once you have your HADR Plan approved, you have to design and plan the detailed implementation of said plan.
But then again, AlwaysOn simplifies the config of HA in SQL Server, and said AlwaysOn (HA) solutions in SQL Server are a great complementary solution to a DR solution in SQL Server, in particular, if you combine Failover Clustering and Automatic Failover DB Mirroring with a DR solution for a given database in a given instance, instance that is covered by Clustering.
Kind regards, GEN