- Reliability
- Transaction management
- Its higher limits for storage and table management
Service Operations Manager at a tech vendor with 51-200 employees
Its use of hyper-threading causes stability issues, but the higher limits for storage and table management are valuable features.
What is most valuable?
What needs improvement?
Improvement to synchronous replication. Currently Microsoft's Always-On implementation of synchronous replication is not truly synchronous, as it counts the data to be written to the slave node, when it is written to the LDF file, not when it is committed to the actual database. This cause a problem when you are load balancing transactions across synchronous nodes.
For how long have I used the solution?
I have been using it for over seven years, including 2008 (5/10) and 2012 (6/10) versions. We also have an early release of 2016 (8/10) which I have tested, but it's not in our production environment.
What was my experience with deployment of the solution?
We deploy multiples of these servers now and it is all managed via PowerShell scripts and templates. It does not play nicely with hyper-threading, so we disable this now by default.
Buyer's Guide
SQL Server
November 2024
Learn what your peers think about SQL Server. Get advice and tips from experienced pros sharing their opinions. Updated: November 2024.
824,106 professionals have used our research since 2012.
What do I think about the stability of the solution?
If there is flapping of Always-On database node, SQL Server will break the replication to the child nodes, and it requires manual intervention to restart replication.
What do I think about the scalability of the solution?
Currently no as we use our own load balancer to enable us to scale to any level.
How was the initial setup?
A strong knowledge of AD is a must as well as the ability to decipher MSFT blog posts.
What about the implementation team?
We did it in-house.
What was our ROI?
Depending on how the product is used, it will take about 12 months.
What's my experience with pricing, setup cost, and licensing?
Chose your database based on traffic type and desired functionality not on initial cost.
What other advice do I have?
Take a look at the environment you plan to implement including the application and traffic model. Consider using Azure DB depending on your implementation requirements.
Disclosure: I am a real user, and this review is based on my own experience and opinions.
Database Manager at a tech company with 51-200 employees
A tool of choice for many corporate environments
Valuable Features:
• SQL server has dynamic resource allocation feature that allows disk and memory usage scale to meet changing database demands. This facility provides better performance and simplifies software management.• SQL Server’s Graphical Query Analyzer not only helps building stored procedures and interactive queries but also graphically displays the steps performed by query processor to execute the query.
• SQL Server’s Online Analytical Processing (OLAP) provides services like data warehousing, data marts and decision support to many medium sized companies.• Data Transformation Services is a powerful and flexible tool provided by SQL server, it simplifies importing and exporting data between and OLE-DB compatible databases.
Room for Improvement:
• Installation and operation of SQL Server requires Internet Explorer (IE).
• Reloading all the data in a database can cause potential data loss especially when the size of database is large.
• No Cascading declarative referential integrity is available in SQL server.
Other Advice:
Microsoft SQL Server is the tool of choice for many corporate environments because it is a commercial database server. Its core role in the commercial world is only to store data which is slightly different than other databases like MS Access. In addition to data storage capability, MS Access allows developing a full user interface for data entry and reports generation. Whereas SQL Server simply stores data. Significant numbers of companies are moving to SQL Server. When it comes to costs SQL will very often make a very good business case.
Disclosure: I am a real user, and this review is based on my own experience and opinions.
it_user4524Founder & Principal Architect at a tech services company with 1,001-5,000 employees
Consultant
I politely disagree with the Cons portion of your review. SQL Server does not require Internet Explorer for installation and operation. The only optional module within SQL Server that requires IE present on the server (but not required for the end users) is SQL Server Reporting Services.
I also disagree with the statement about reloading data can cause data loss if the database is large. If the product is used properly, the potential for data loss is extremely small. I load large data sets quite frequently, and data loss simply does not occur. If you are experiencing data loss during loads, you might have an infrastructure problem that is contributing to instability.
Also, SQL Server has had cascading declarative referential integrity features since SQL Server 2000. See msdn.microsoft.com.aspx for more information.
Buyer's Guide
SQL Server
November 2024
Learn what your peers think about SQL Server. Get advice and tips from experienced pros sharing their opinions. Updated: November 2024.
824,106 professionals have used our research since 2012.
Chief Information Officer at a tech consulting company with 51-200 employees
Easy to use, scalable, and reliable
Pros and Cons
- "The main feature of this solution is ease of use."
What is our primary use case?
We use SQL Server for database management.
What is most valuable?
The main feature of this solution is ease of use.
For how long have I used the solution?
I have been using SQL Server within the past 12 months.
What do I think about the stability of the solution?
The solution is stable and reliable.
What do I think about the scalability of the solution?
SQL Server has been very scalable.
We have approximately 200 users using the solution in my organization.
How are customer service and technical support?
We are satisfied with the technical support.
Which solution did I use previously and why did I switch?
I previously used a different solution in the other company I worked for.
What about the implementation team?
We have a hardware support partner who does the implementation.
What's my experience with pricing, setup cost, and licensing?
The price of the solution could be cheaper.
What other advice do I have?
I rate SQL Server a nine 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.
CEO at a tech company with 51-200 employees
SQL Server offers tight integration at low pricing
Valuable Features:
• SQL Server provide end users and database programmers with a broad spectrum of services such as Analysis and Reporting services, Data Engine, Integration Services thus making database development and management easier and reliable.
• SQL Server offers a platform on which data in all levels- structured, semi-structured, and unstructured data can be managed, integrated and analyzed thus enabling an organization to realize its mission-critical information.
• Latest versions of SQL Server provide a handy development studio that not only make the creation of database objects easy but also offer useful tools such Object Explorer to allow quick processes.
Room for Improvement:
• SQL Server work best with Windows Operating System and it is not compatible with some other systems hence limiting its platform friendliness.
• Advance versions with higher functionality such as Work Group Edition have high installation requirement such as multi-processor computers, larger primary memory and are not open source.
Other Advice:
• Database developers who want to have a clear logical and physical understanding of database systems will no doubt benefit much from using SQL Server. I personally marvel at the extensible support provided by the management studio especially on disk and file management as I enjoy using SQL Server 2008. SQL Server is friendly to both beginners and experts and its installation process can be customized to suite different features.
Disclosure: I am a real user, and this review is based on my own experience and opinions.
Good Article. Though i would like to add some points.
1) Microsoft SQL Server is easy to use and offers more features, like full support for triggers.
2) Closely integrated with Microsoft products like .NET Framework.
3) Various features for data restoration and recovery.
4) Microsoft SQL Server only runs on Windows-based servers.
5) Costly license fees.
CEO at a tech services company with 11-50 employees
Integrates well with Microsoft tools, but needs better stored procedures integration
Pros and Cons
- "It is integrated with Microsoft tools."
- "The stored procedure integration with our development could be better. Things are always changing very fast at Microsoft, and it takes a lot of resources to get on top of it. We're struggling with version control. In terms of new features, we don't have any feature requests. We are not focusing on the database."
What is our primary use case?
We are using it for accounts payable and accounts receivable automation. We make accounts payable and accounts receivable solutions, and we're using SQL Server as one of the building blocks.
What is most valuable?
It is integrated with Microsoft tools.
What needs improvement?
The stored procedure integration with our development could be better. Things are always changing very fast at Microsoft, and it takes a lot of resources to get on top of it. We're struggling with version control.
In terms of new features, we don't have any feature requests. We are not focusing on the database.
For how long have I used the solution?
I have been using SQL Server for 17 years.
What do I think about the stability of the solution?
Its stability is okay.
What do I think about the scalability of the solution?
Its scalability is okay.
How are customer service and technical support?
Their technical support is okay.
What's my experience with pricing, setup cost, and licensing?
It is something we have been using for a lot of years. If we're paying, it should be reasonable.
What other advice do I have?
I would recommend looking at other solutions. You can also look at the Azure SQL implementation because it is easier to start with.
I would rate SQL Server a seven out of ten.
Which deployment model are you using for this solution?
Private Cloud
Disclosure: My company has a business relationship with this vendor other than being a customer: partner
Systems Analyst Developer with 1-10 employees
A fast and efficient way to track reporting
Pros and Cons
- "I have experience with this product for many years. I never have problems with it. It can handle a PC, and it can also handle huge data. It is fast and efficient."
- "It would be nice if there was a feature to search for a specific value across multiple tables. This would save a lot of time for its users."
What is most valuable?
It is widely used and we never have problems with it. It can handle a PC, and it can also handle huge data. It is fast and efficient. It is something unique that tracks reporting of records, personnel, finances and more. It also integrates well with everything, not just Microsoft tools.
What needs improvement?
It would be nice to search for specific value across multiple tables. This would save a lot of time.
For how long have I used the solution?
More than five years.
What do I think about the stability of the solution?
I have never had a problem with the stability of the solution.
What do I think about the scalability of the solution?
We have never really had a problem with the scalability of the solution.
How is customer service and technical support?
I have never used technical support. It is the joke at the office that you cannot get help on the Microsoft website at all. Also, downloading anything from Microsoft is usually a nightmare. Honestly, I end up googling the problem and solving it myself. This is definitely something Microsoft needs to improve.
What other advice do I have?
It is definitely important for someone looking at a new vendor to consider the support of the solution. In addition, the customer should really do their research and understand what their needs are, and make sure the new solution will solve those needs.
Disclosure: I am a real user, and this review is based on my own experience and opinions.
Chief Engineer at a tech services company with 51-200 employees
Stable, straightforward installation, and priced well
Pros and Cons
- "The installation was straightforward. We did not have a large installation and it took a couple of weeks to complete."
- "The solution could improve by having better integration."
What is our primary use case?
We used SQL Server to store all of our lab data on the database. We had a front-end application that needed SQL in the background for archiving all the laboratory data.
What needs improvement?
The solution could improve by having better integration.
For how long have I used the solution?
I have been using SQL Server for approximately three years.
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?
We have approximately 200 users that use an application that uses the SQL Servers database.
How was the initial setup?
The installation was straightforward. We did not have a large installation and it took a couple of weeks to complete.
What about the implementation team?
Our IT department does the implementation and maintenance of the solution.
What's my experience with pricing, setup cost, and licensing?
There is an annual license and it is priced reasonably.
What other advice do I have?
I would recommend this solution.
I rate SQL Server a nine 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.
Program Solution Architect at a tech services company with 11-50 employees
Simple to install, easy to use, and it is not difficult to find resources to manage it
Pros and Cons
- "It is easy to use and easy to perform a backup."
- "In my experience, I've found that scalability can be improved."
What is our primary use case?
My background is primarily in software development, and I use SQL Server among other tools in that capacity. SQL Server was one of the main databases in my previous company, and it is used for storing data from different applications.
What is most valuable?
It is easy to use and easy to perform a backup.
It is easy to find resources that can manage SQL Server.
What needs improvement?
In my experience, I've found that scalability can be improved.
For how long have I used the solution?
I have used SQL Server while working for different companies.
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?
We have between 40 and 50 applications running on it, which are used by many people.
How are customer service and technical support?
The support from Microsoft is good.
How was the initial setup?
The installation is simple.
What about the implementation team?
We have an in-house team for deployment and maintenance.
One administrator is suitable for managing it.
What other advice do I have?
In summary, this is a good product and I recommend it.
I would rate this solution a nine 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.
Buyer's Guide
Download our free SQL Server Report and get advice and tips from experienced pros
sharing their opinions.
Updated: November 2024
Product Categories
Relational Databases ToolsPopular Comparisons
MySQL
Teradata
Oracle Database
MariaDB
SAP HANA
IBM Db2 Database
Amazon Aurora
CockroachDB
LocalDB
IBM Informix
Oracle Database In-Memory
Citus Data
YugabyteDB
SAP IQ
SAP Adaptive Server Enterprise
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?
I suggest to engage with an expert in SQL Always ON configuration to address the issues as we have been using it for over 5 years and never faced such issues. Heart-beat Sync between two nodes of remote locations has a dependency on latency which must be less than 15-20 ms. Also review the processor model used for virtualization; sometimes the issue may be at the processor / hyper-visor level.