We primarily use the solution for data storage. We use it for its data warehouse, BI services, and AI.
GF at Innopact GmbH
Extremely mature, scalable, and stable
Pros and Cons
- "The product has been on the market for over 25 or 30 years. It's an extremely mature solution."
- "Technical support could be faster."
What is our primary use case?
What is most valuable?
If you compare the SQL Server with the block storage it's stable and it's working.
The product has been on the market for over 25 or 30 years. It's an extremely mature solution.
The solution is pretty scalable.
The initial setup is pretty straightforward, depending on your requirements.
What needs improvement?
The solution is very expensive.
Technical support could be faster.
For how long have I used the solution?
I've been using the solution for many years. It's been a while. It's likely been over ten years or so - a decade or more.
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,067 professionals have used our research since 2012.
What do I think about the stability of the solution?
The solution is very stable. There are no bugs or glitches. It does not crash or freeze. It's very reliable in terms of performance.
What do I think about the scalability of the solution?
The solution scales well. If a company needs to expand it, it can do so with ease.
Three people are using the solution in our organization.
How are customer service and support?
We've used technical support in the past. However, it's not a very fast support system. For the new Office 365, it's better. This solution still needs to work on support.
Which solution did I use previously and why did I switch?
For a specific task, we are using this solution. However, for some other tasks, we're using MongoDB, MariaDB, Oracle, or something else. It depends on the task and the solution and the requirements.
How was the initial setup?
The installation is not overly complex or difficult for the most part. The initial setup's level of straightforwardness, however, depends. If you only need an SQL Server, it's easy. If you need a cluster, it's more difficult. If you need a great cluster all over the world, it's more difficult.
What about the implementation team?
I handled the installation myself. I did not need the help of an integrator or consultant.
What's my experience with pricing, setup cost, and licensing?
The solution is expensive. The pricing is different and not really standardized. If you're using it on Azure you pay on your workloads. If you have a separate dedicated instance, you pay for the course. It's different, according to the situation, however, in either case, it's expensive.
What other advice do I have?
We are customers and end-users.
We are using the 2014 and 2019 versions of the solution.
I'd recommend the solution to other organizations and users. However, if it will work for a company, or if it will work for them in an ideal manner depends on the requirements you have to fulfill as an organization. For example, race cars may be good cars, and great products, however, it's for a specific task. For other tasks, it may not be useful.
I general, I'm quite satisfied with the solution and it does what I need it to do. I'd rate the solution at an eight out of ten.
I'd recommend the solution to other users and organizations.
Disclosure: I am a real user, and this review is based on my own experience and opinions.
Senior Manager - RPA & Transition at a financial services firm with 10,001+ employees
Stable with prompt technical support and capable of scaling
Pros and Cons
- "The performance is reliable."
- "You do need to have technical knowledge in order to install the solution. It's not something a layperson can do."
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.
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 technical 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.
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,067 professionals have used our research since 2012.
DWH Architect at B2BSoft
Stable, scalable, and good integration services
Pros and Cons
- "The columnstore index feature is useful for us, and we also use the integration services. It is also very stable."
- "We would like to have a common storage option in the SQL Server. This option is available in Oracle Database. It would be great if Microsoft could create something like a columnstore that has not only indexing but also tables for common storage."
What is most valuable?
The columnstore index feature is useful for us, and we also use the integration services. It is also very stable.
What needs improvement?
We would like to have a common storage option in the SQL Server. This option is available in Oracle Database. It would be great if Microsoft could create something like a columnstore that has not only indexing but also tables for common storage.
For how long have I used the solution?
I have been using SQL Server for four years.
What do I think about the stability of the solution?
It is pretty stable.
What do I think about the scalability of the solution?
If we talk about just standard RDBMS, it is very scalable because we don't have to scale platforms.
How are customer service and technical support?
All communication with Microsoft technical support is done by our internal support group. I'm not communicating with them directly. I guess their technical support is okay and fast.
What other advice do I have?
I would recommend SQL Server as a solution for a medium enterprise or a small business.
I would rate SQL Server 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.
Software Developer at OATI
I use it to fine tune my procedures and functions
Pros and Cons
- "Tuning Advisor suggests where to add indexes and from where to remove them. It works like an adviser."
- "SQL Server Profiler makes finding and debugging easy."
- "I use it to fine tune my procedures and functions."
- "Third-party services from Redgate should be built-in to it, like SQL Search."
- "Debugging from the debugger tool functionality should be enhanced."
What is our primary use case?
I use SQL Server to optimize SQL queries and find the estimated cost of my queries.
I also use it to fine tune my procedures and functions.
How has it helped my organization?
- SQL Server has maintained my database problem in an arranged manner.
- SQL Server Profiler makes finding and debugging easy.
- Support for third-party tools, like SQL Search.
What is most valuable?
- SQL Server Profiler: Know exactly which procedures and functions are being called and how much read and write they are taking.
- Tuning Advisor: It suggests where to add indexes and from where to remove them. It works like an adviser.
- Storage capability
- Debugger: The debugger tool can execute code step-by-step.
What needs improvement?
- Third-party services from Redgate should be built-in to it, like SQL Search.
- Debugging from the debugger tool functionality should be enhanced.
For how long have I used the solution?
Three to five years.
What do I think about the stability of the solution?
No stability issues.
What do I think about the scalability of the solution?
No scalability issues.
How are customer service and technical support?
It is good.
Which solution did I use previously and why did I switch?
I have been using SQL Server from the start.
How was the initial setup?
It was straightforward.
What about the implementation team?
In-house.
What was our ROI?
It is good.
What's my experience with pricing, setup cost, and licensing?
The setup cost is high, but it will return every penny.
Disclosure: I am a real user, and this review is based on my own experience and opinions.
Chief of Engineering at a comms service provider with 11-50 employees
Ease of use, stability make it the right choice for us
Pros and Cons
- "Only one CPU core can be used. Can’t move a database between servers easily. Can’t use triggers."
What is our primary use case?
We use it
- to capture long distance calls for billing
- as a quoting database
- to redirect phone calls based on customer caller line id.
What is most valuable?
Ease of use.
What needs improvement?
- Only one CPU core can be used
- Can’t move a database between servers easily
- Can’t use triggers
The free version is cumbersome to use and maintain. But $5000 for a licence is more expense than the benefit I would get from a licensed version.
For how long have I used the solution?
One to three years.
What do I think about the stability of the solution?
No stability issues.
What do I think about the scalability of the solution?
We are capturing 1 million calls per month. The free version can’t scale this much data.
How are customer service and technical support?
Never used. Google is sufficient.
Which solution did I use previously and why did I switch?
Postgre has a weird syntax and it is slower than MS SQL. The command line interpeter makes it complex to learn.
How was the initial setup?
MS SQL is the easiest of the three I tried.
What's my experience with pricing, setup cost, and licensing?
A licence might be worth the price to simplify management and speed up searches.
Disclosure: I am a real user, and this review is based on my own experience and opinions.
Lead Software Engineer at a tech services company with 11-50 employees
We've measured notable performance improvements with this solution
Pros and Cons
- "There was an online system in which we had about 2500 requests to the DB per second. Every request had a completion window of one second to process and retrieve data. After switching to SQL Server, and AlwaysOn, and Snapshot, and tinkering, and configuring and tinkering, the handling capacity we measured increased to about 5000 requests per second, while the time decreased to 0.5 seconds per request."
- "As a software developer, it can be hard to do something in Oracle that is SQL Server specific, and vice-versa, sometimes."
- "One stability issue I encountered was the deadlocking between calls to the same resources (tables, etc.). That was solved by row versioning."
How has it helped my organization?
There was an online system in which we had about 2500 requests to the DB per second. Every request had a completion window of one second to process and retrieve data. Before my arrival, the numbers were 1000 requests per second and two, and sometimes, three to five seconds spent per request.
After switching to SQL Server, and AlwaysOn, and Snapshot, and tinkering, and configuring and tinkering, the handling capacity we measured increased to about 5000 requests per second, while the time decreased to 0.5 seconds per request.
What is most valuable?
The AlwaysOn high-availability feature is the most valuable feature of SQL Server to us. This is because of the relative ease of the configuration, rather than configuring for OLTP-OLAP distinction.
What needs improvement?
As a software developer, it can be hard to do something in Oracle that is SQL Server specific, and vice-versa, sometimes.
Improvements must not be stopped and must not end. When business needs arrive, then the improvements follow. For example, 15-20 years ago, MySQL did not have built-in Stored Procedure support; there was no business need for MySQL to have stored procedures built-in.
For how long have I used the solution?
One to three years.
What do I think about the stability of the solution?
One stability issue I encountered was the deadlocking between calls to the same resources (tables, etc.). That was solved by row versioning. (We were shooting ourselves in the feet).
What do I think about the scalability of the solution?
No scalability issues.
How are customer service and technical support?
I have never had the need to reach out to the vendor.
Which solution did I use previously and why did I switch?
Yes I did use another solution previously. The switch was mainly for the performance. Secondly, it was for the technology compatibility.
How was the initial setup?
It was very straightforward. There was no complexity which I couldn’t handle.
Which other solutions did I evaluate?
I’m not a "product" fan. I try to use "the" product which will comply smoothly with the software I’m working on.
What other advice do I have?
I’ve been working on Microsoft SQL Server since 2005, and currently I’m using SQL Server 2014 in my development environment and SQL Server 2012 in the production environment.
Disclosure: I am a real user, and this review is based on my own experience and opinions.
SQL DBA at a computer software company with 51-200 employees
The SSIS or SQL Server Integration Services is a vital component that is associated to the Server.
SQL Server and SQL Server Integration Services – Informative Article
SQL Server and SQL Server Integration Services: Discussed and Explained
The concept of Relational Database Management System when brought forward by Microsoft was known as SQL Server. Architecture of SQL is a division where all the components combine and work, both; independently and together. This is done in order to process the services offered, in a defined way. This allows SQL Server to work smoothly.
The external SQL Server interface is developed by the Protocol Layer. All the operations conducted on the server are transmitted through a defined format known as the Tabular Data Stream (TDS). Basically, this is an Application Layer Protocol that helps to transfer data between the client and server (database).
Some other points that in a combination help make SQL an essential database management system for users include the following:
Data Storage
It is a collection of a variety of tables with all sorts of types including; primary types – decimal, integer, float, etc., varchar, and more.
Concurrency and locking:
The server permits users to make use of the SQL database concurrently by multiple types of clients. So it is required to take control of the simultaneous database access to the shared data. The two concurrency control modes provided are; pessimistic and optimistic.
SQL uses lock mechanism, in the pessimistic mode of concurrency control and they can be further classified as; shared & Exclusive Locks.
Data retrieval:
Data in SQL Server is retrieved via querying it and this query procedure is executed by the SQL Server variant; T-SQL. The order of steps in the procedure of querying for essentials to recall the data requested for is decided by the Query Processor.
Buffer Management
This part of SQL Server plays a critical role in reducing the Disc I/O while it buffers the pages into RAM. One can store up to 8 KB of pages in the buffered memory and this collection of all buffered pages is known as the Buffer Cache.
SQL Server and Its Versions
The entire database held by SQL Server is available as Primary (*.mdf) and Secondary (*.ndf) Database respectively. While an LDF file’s role is to hold the entire log details of the transactions carried out on any of the database.
Amongst all the versions of SQL Server; 2005, 2008 R2, 2014, and others; 2000 was the first version to be adding multiple performance measures to the Server. And out of all the measures introduced by SQL Server version 2000, SQL Server Integration Services or SSIS was the most vital one.
Detailing Of SQL Server and SQL Server Integration Services Security
The SSIS Security of SQL Server consist of a variety of layers offering a completely sound environ for the services. These layers constitute of the below mentioned components:
- Package Properties;
- Digital Signature;
- Operating System Permissions;
- Database roles.
When used in a combination for applying security measures, these components act as a defensive shield to the packages of SQL Server.
In order to interpret the concept of SQL Server and SQL Server Integration Services security, understanding the platform of SSIS is of primary importance. The forthcoming segment of this article discusses about the same as well as the attributes offered by it in SQL Server environ.
Understanding the SSIS Concept of Security
The SSIS or SQL Server Integration Services is a vital component that is associated to the Server. Normally used for carrying out a wide number and variety of operations related to data migration this platform has been structured considering the two mentioned elements:
- Data Integration which happens to be an approach for combining the data from different set of resources. Thus, representing it in a manner that is unified and coordinated.
- Workflow programs a set of applications that modify procedures to some point and even require manual agreement / customization or modification of activities sometimes.
The following functions are allowed to be performed at a higher level:
- Data retrieval through any source and loading of components into any source with a defining workflow.
- Carrying out a wide number procedures on the database including; calculation, conversion, etc.
This was an overview of the SSIS platform therefore, proceeding to the concept of SSIS security measures is feasible now.
The Concept of SSIS Security
Always using trusted mediums for launching the packages is one of the most important concepts of the SSIS Security measure. And prior to that, you must necessarily identity the source of package before opening it, which can be done by allotting certificates to packages.
The Perks of It: Unauthorized access to the server’s sensitive data can be kept under control via allotting identity features to a package. Also, it guarantees control on the SQL Server package configuration.
Even the logs, checkpoint files, and the configurations can be protected as well.
The Package Information displayed via SSMS (SQL Server Management Studio) Integration Services is offered integrity and protection by the medium of this platform.
A better understanding about the functional measures and features of the SSIS Security can be referred in the upcoming sections below.
- Access On Package Data Components To Be Controlled: To limit or restrict access to package or its components, they are encrypted via “ProtectionLevel” property applied. Level of this type of security can be adjusted accordingly. Values get automatically encrypted for properties that are assigned to sensitive set of data by the IS (Integration Services). Only on providing the correct password, can an encrypted data be displayed.
- Package Access To Be Controlled: SQL’s MSDB database or an XML file can be used for storing the IS Packages with file extension as .dtsx. In an MSDB database the “sysdtspackages” & “sysssispackages” for storing the package, tables are taken into usage. Thus, when database backup is created, associated packages automatically get backed up. In order to control access to these packages, three types of database roles are allotted to them:
- Db_ssisadmin
- Db_ssisltduser
- Db_ssisoperator
TIP: In case the file system is used for package storing, make sure that file or folders containing the packages are secure completely.
- Access to Packages Containing Files To Be Control: Information encapsulated within the log, checkpoint files, and configuration packages require being prevented and protected due to the sensitive nature they have. Some of the factors associated with the approach are:
- Checkpoint file storage must only be done into the file system.
- Storage of Logs and Config files can be done using; SQL DB Tables or the File System.
- Extra provision of security is needed by the checkpoint files stored under file system.
- IS Service Access To Be Controlled: “Windows Administrative” group members are assigned with package running access & stop roles. Meanwhile, users that are not member of the group are authorized to access or eliminate packages started only by them.
Conclusion: Security is a matter of concern regardless of the platform being discussed about. And understanding the detailed aspects of the SSIS Security measure helps prevent the SQL Server packages from unofficial access.
Disclosure: I am a real user, and this review is based on my own experience and opinions.
Founder & Principal Architect at a tech services company with 1,001-5,000 employees
Best DBMS platform for all of your business needs
Valuable Features:
- Ease of use of this product is much better than equivalent products
- New AlwaysOn availability group enhancements bundles more DR and HA features in one easy to use interface
- In-Memory OLTP, or project Hekaton, allows for utilizing memory to boost application performance with only minor application changes
- Power, scalability, flexibility, and bundled tooling means it will meet all of your organizational DBMS needs for all size workloads
- Support from MS and free knowledge and support from the MS community is terrific
- Virtualization friendly!
- Core features of the product include many features that require additional licenses with other platforms
- SImple to setup and keep running
Room for Improvement:
- Ease of installation means that anyone can install it, but many do not perform the steps required to properly maintain the data
- The increasing cost of the platform is slowing adoption by the SMB space
Other Advice:
I am so fond of this product that I have dedicated this portion of my career to focusing on mastering this platform as a consultant. I feel that this product is the best fit on the market for your database needs. The product is stellar, the amount of free knowledge on the Internet for this product is without parallel, and the community around SQL Server is so strong that I consider it a family.
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?
Thanks! And the answer is nope - Report Builder 2012 is out there and
works great! It's available at
www.microsoft.com
Plus, Report Builder 2014 is out. Here's a great page on what's new in it.
msdn.microsoft.com
Hope this helps!
David A. Klee