We use on-premises, standalone deployment of SQL Server for our own CRM database. There are around seven to eight users in our company.
General Manager/MVP at Yotta Infrastructure Solutions LLP
Reliable, Stable, And Cost-effective Solution For A Small Database
Pros and Cons
- "The features that we have found the most valuable are reliability, availability perspective, and current scalability."
- "The scalability and the high availability feature can be expanded or improved. Currently, there is a limitation on scalability. A feature similar to the Oracle Diagnostic feature can be included to provide a better user experience."
What is our primary use case?
How has it helped my organization?
SQL Server suffices our main requirement of a small database, and it is also very cost-effective.
What is most valuable?
The features that we have found the most valuable are reliability, availability perspective, and current scalability.
What needs improvement?
The scalability and the high availability feature can be expanded or improved. Currently, there is a limitation on scalability.
A feature similar to the Oracle Diagnostic feature can be included to provide a better user experience.
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.
For how long have I used the solution?
We have been using SQL Server for around 10 years.
What do I think about the scalability of the solution?
Stability and scalability are both good. It suffices for our current requirements, but if we want to scale up in the future, it has limitations.
How are customer service and support?
We sometimes contacted Microsoft technical support, and we also have in-house Microsoft support. We are happy with the support.
How was the initial setup?
The initial setup was straightforward.
What about the implementation team?
Our in-house team handled the deployment.
What's my experience with pricing, setup cost, and licensing?
SQL Server is a cost-effective solution for a small database.
What other advice do I have?
I would definitely recommend SQL Server.
I would rate SQL Server an eight out of ten.
Not a ten because it has some limitations. When considering overall scalability, reliability, features, if you look at Oracle, it's still ahead of SQL Server.
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
Senior SQL DBA at a financial services firm with 51-200 employees
Quite reliable in cluster configurations and has helped me to reduce downtime and improve SLAs
Pros and Cons
- "If backups and alerts are configured properly, I can also rely on my restoration plan."
- "It is quite reliable in cluster configurations and has helped me to reduce downtime and improve SLAs."
- "Comparing with other database management systems that I tried in other companies, SQL Server is quite easy to install, configure, and maintain."
- "I would appreciate a dark theme for SQL Server Management Studio and ability to add databases with TDE enabled into availability groups."
What is our primary use case?
Usually I install an SQL Server as part of something bigger from Microsoft (NAV, CRM, SharePoint, SCCM, SCOM, BizTalk, etc.) or some custom built solution that was designed around this DMBS.
I also teach in a university. My students admit that SQL Server is quite easy to install and work with if you are a total beginner (compared with others).
How has it helped my organization?
I am not sure, as we have been working with it from the start. Comparing with other database management systems that I tried in other companies, SQL Server is quite easy to install, configure, and maintain. It is also quite reliable in cluster configurations and has helped me to reduce downtime and improve SLAs. If backups and alerts are configured properly, I can also rely on my restoration plan saving my butt more than once.
What is most valuable?
Always On is my favorite feature. I do like availability groups and cannot imagine how I lived with them before.
Microsoft tries to release new features with every version, but I cannot say that they are killer features. Usually these are just "nice to have" stuff. However, SQL Server works and it works just fine. It is really reliable if you don't shoot your own leg. All the basic functionality is 100% bulletproof.
What needs improvement?
I like it the way it is, though I would appreciate a dark theme for SQL Server Management Studio and ability to add databases with TDE enabled into availability groups.
I am aware of Connect and Trello pages, and there are a lot of good ideas from other people, most of them are useful only in some very rare scenarios. There are interesting suggestions present, and Microsoft should pay more attention.
For how long have I used the solution?
More than five years.
What do I think about the stability of the solution?
Over the years, there was one service pack and two cumulative updates that were recalled as problematic ones, but otherwise it is very stable system.
What do I think about the scalability of the solution?
Unfortunately, SQL Server cannot be scaled out so easily as some NoSQL solutions. There are some options that may allow it to work with quite enormous workloads. For example, try to google how Stack Overflow is built (yes, it works with SQL Server). They have quite an interesting architecture.
How is customer service and technical support?
It depends. The shear number of support specialists is huge. You can get a freshman or a seasoned veteran. Usually, it is tolerable but it might take a while to solve a problem. In my experience, 50% of all problems can be resolved by installation of the latest patch. In 25% of times, it is your own stupidity. The 25% that left are real bugs, exotic configurations, and rocket science-level problems with a real high-load and very specific code and environments.
How was the initial setup?
It depends how many features you want to implement. Basic stuff is very easy to install, but if you want to implement all the features or deploy a high-load or a clustered environment, it might be tricky. That is why you need a good architect and skilled DBA for something really complicated.
What about the implementation team?
I have seen everything. It always depends on people skills. To get full performance from the SQL Server you need a well prepared environment and hard team work.
What's my experience with pricing, setup cost, and licensing?
This is a downside of enterprise Microsoft products. Currently, almost all of my machines are in Azure and I think it is the best way of licensing now (VM+software).
What other advice do I have?
Though I do like the SQL Server, I must say it is very hard to find a good DBA nowadays and having a DBMS without a DBA is like having a car without a driver and skills to drive it yourself. Before choosing or switching to this DMBS, check what kind of workforce is available in your area.
You may consider Azure SQL Database as a simple alternative, but I would advise it only for small workloads though.
Disclosure: I am a real user, and this review is based on my own experience and opinions.
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.
Systems Analyst/DBA at Vecima Networks
A relational database system that is critical for storing reporting data
What is our primary use case?
The primary use of SQL Server is to store and retrieve data. If you go into the extra features that come with your license, you can also do reporting, analytics and ETL.
What is most valuable?
Everything is valuable. It is a relational database system which is critical for storing reporting data or any data that is highly relate-able. Plus your data is one of the most important assets in your company. Might as well have a good system to protect it.
How has it helped my organization?
In a manufacturing system, storing test data in an Excel file has limitations in how much data can be stored at one time and how many people can manipulate the data at one time. Storing it in SQL Server allows you to store as much data as you have disk space for. It can be viewed and modified by multiple people at one time.
What needs improvement?
Setting up some of the more complex systems could be simpler. Things like service broker can be tricky to set up for the inexperienced.
For how long have I used the solution?
More than five years.
What do I think about the stability of the solution?
Stability seems very good. I have not seen any issues with this.
What do I think about the scalability of the solution?
I have not run into scalability issues. It feels very scalable.
How are customer service and technical support?
I have not needed to contact technical support for this product
Which solution did I use previously and why did I switch?
I did not use a previous solution. I have heard of other companies using Microsoft Access or Excel for similar problems. However, after hearing the headaches they have, I would not recommend those for large scale projects.
How was the initial setup?
The initial setup was straightforward, but configuration post-install can be complex. Complexity comes from attempting to optimize it and implementing some of the new features that come in new versions.
What about the implementation team?
We implemented it entirely in-house.
What's my experience with pricing, setup cost, and licensing?
Pricing and licensing is based on a per core and/or per-processor license. Try to keep these low, but keep it above four. (Four is the minimum number of cores.) If you are working mostly with OLTP, make sure your single thread CPU speeds are high.
Which other solutions did I evaluate?
We did not evaluate other options. The other options lacked support, lacked performance, or were too expensive.
What other advice do I have?
If you don't have a DBA on site, hiring a consultant is recommended to help get things setup and configured. This will reduce headaches down the line.
Disclosure: I am a real user, and this review is based on my own experience and opinions.
The AlwaysOn feature ensures database availability, even when one of the servers is down.
What is most valuable?
Apart from the standard SQL database-related features, the 2012 version enables the AlwaysOn functionality which enables two or more SQL Servers that can be clustered, with heartbeat across geographic locations along with high availability failover and 99.9999% uptime.
How has it helped my organization?
We have deployed three instances of the SQL Server, i.e., two at the primary datacenter and one at the disaster recovery facility. The AlwaysOn feature has ensured 100% database availability, even when one of the servers is down without any performance issues for the end user.
What needs improvement?
The Always ON (High Availability) functionality is support only with the MS SQL enterprise edition. It would be beneficial to many if this feature were also made available in the Standard Edition.
For how long have I used the solution?
I am using the SQL Server for more than 10 years and the 2012 version, I have been using since the last five years.
What do I think about the stability of the solution?
There were no stability issues. If the initial configuration is done correctly, there are no issues. If the other servers are connected at remote locations, then the connectivity performance plays a vital role and it should be 10-15 ms for best results.
What do I think about the scalability of the solution?
There were no scalability issues.
How are customer service and technical support?
We have received excellent support from Microsoft and the local partners.
Which solution did I use previously and why did I switch?
In the earlier versions, we used log shipping to the other servers for the failover and replication requirements. With this version, all the servers are Active/Active and there is no issue related to the availability or failover.
How was the initial setup?
The basic installation is simple, whereas rest of the clustering requires an expert skill level for the configuration and deployment.
What's my experience with pricing, setup cost, and licensing?
When comparing the Standard Edition to the Enterprise, it is expensive but the performance and features meet with the ROI and TCO. Thus, overall, it minimizes the redundant servers, multiple backup copies, the risk of non-availability of the latest copy at the disaster recovery.
What other advice do I have?
The latest 2016 version has many more new features and functionalities, if you have the Enterprise Level Agreement and subscription model, you can upgrade to the latest version.
The Always ON (High Availability) functionality is support only with the MS SQL enterprise edition. It will be beneficial to many, if this feature is available in Standard Edition.
Disclosure: I am a real user, and this review is based on my own experience and opinions.
ESM Specialist at LetsCloudIT
Synchronization of nodes is very useful and there is no downtime for maintenance needs
Pros and Cons
- "It's great that the nodes are synchronized so if you lose one it automatically moves to another."
- "Could have additional security."
What is our primary use case?
We use this solution to store our data and for running queries, simple select queries that enable me to create the views I need and report from those views. I'm an ESM specialist and we are customers of SQL Server.
What is most valuable?
I like the stability of the solution, the fact that you have two, three, four nodes replicating at any given time at different locations, and they're all synchronized; if one is lost it automatically moves to another. The other advantage here is that when it comes to application maintenance, you switch onto another node while you maintain another server and there's no downtime.
What needs improvement?
The solution could have additional security.
What do I think about the scalability of the solution?
The solution is easily scalable because of its flexibility.
How was the initial setup?
I don't do the installation, but it appears straightforward according to those who carried out the implementation. These days deployment takes about an hour. We have 1,200 or so users. With the onboarding of more customers, we'll be increasing our use of SQL Server. For now, we have one person dealing with maintenance.
What other advice do I have?
I rate this solution nine out of 10.
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.
Chief Information Officer at SYNOVA CONSULTANCT
High performance, setup straightforward, but priced high
Pros and Cons
- "The most valuable feature of SQL Server is the performance."
What is our primary use case?
We use SQL Server for developing systems.
What is most valuable?
The most valuable feature of SQL Server is the performance.
For how long have I used the solution?
I have been using SQL Server for years.
What do I think about the scalability of the solution?
We have approximately three people who are using this solution.
How are customer service and support?
The technical support from Microsoft has been good.
How was the initial setup?
The initial setup of SQL Server is straightforward.
What about the implementation team?
We have two administrators that did the implementation of the solution.
What's my experience with pricing, setup cost, and licensing?
The price of SQL Server could be reduced, the license is expensive. We have an annual subscription.
What other advice do I have?
I would recommend SQL Server to others.
I rate SQL Server a seven out of ten.
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.
senior system integrator at a retailer with 10,001+ employees
Easy to expand and a nice backend server, but requires active-active options
Pros and Cons
- "We have found the solution to be scalable."
- "There are a few use cases where we do need the Active-Active options instead of Active-Passive, yet those kinds of options are not available for Microsoft."
What is our primary use case?
We primarily use the solution as a backend server.
There are a few applications of the Oracle product for our data sitting on the SQL Server as well.
What is most valuable?
It's useful as a backend server.
We have found the solution to be scalable.
What needs improvement?
The stability of the product needs to be improved. It's really not stable enough.
In Microsoft, the Active-Active options are not available. There are a lot of requirements that are coming right from the customer, which may not be provided by Microsoft. There are a few use cases where we do need the Active-Active options instead of Active-Passive, yet those kinds of options are not available for Microsoft.
For how long have I used the solution?
We've been working with the solution for going on five years.
What do I think about the stability of the solution?
We've struggled with the stability of the product. We'd like for it to be more stable and reliable.
What do I think about the scalability of the solution?
The scalability is very good. If a company needs to expand, it can do so.
What other advice do I have?
We are a customer and an end-user.
I would rate the solution at a seven out of ten. While the scalability is there, the solution is lacking a few aspects that customers really need.
Disclosure: My company has a business relationship with this vendor other than being a customer: Implementer
Product Owner at Software Technology
Straightforward installation, easy database access, and scalable
Pros and Cons
- "They have improved the UI and ease of accessing the database and server which is good. You can load it up and start using it from the very minute it is implemented."
What is our primary use case?
We use SQL Server to manage and store information.
What is most valuable?
They have improved the UI and ease of accessing the database and server which is good.
You can load it up and start using it from the very minute it is implemented.
For how long have I used the solution?
I have been using SQL Server for two and a half years.
What do I think about the stability of the solution?
SQL Server is stable. We have more resources that are using it, I am more familiar with SQL Server. I have been using it for a long time. Most of the time it has been stable.
What do I think about the scalability of the solution?
The solution is scalable.
We have approximately 30 people in my organization using this solution.
How are customer service and support?
The technical support is okay.
How was the initial setup?
The installation is straightforward.
What about the implementation team?
We have administrators and engineers that do support the solution.
What's my experience with pricing, setup cost, and licensing?
We are on a monthly subscription and the price could improve. However, the price has worked out well in some deployments. The problem is you never know what kind of services have been installed and you have to be in touch with many people, such as which servers are active or which are not. I did face a couple of issues in terms of subscriptions and the pricing model. They have improved over time.
What other advice do I have?
I would recommend this solution to others. My advice to others wanting to implement this solution is you have to consider the industry demand and the benefits or advantages of a solution before you choose, for example, Oracle or Microsoft.
I rate SQL Server an eight out of ten.
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?