Currently, I'm moving to another set of projects. One is for a small company that supports a client and is building on a different surface on the SQL server. The cloud that is used is essentially Amazon AWS.
Sr Tech Business Analyst, Group Data Projects & Ventures at a financial services firm with 10,001+ employees
Stable, flexible, and scalable
Pros and Cons
- "The solution seems to be pretty flexible."
- "Due to the fact that I'm dealing with the product more as a data analyst, the SQL Server management studio is really relatively primitive compared to other more advanced tools."
What is our primary use case?
What is most valuable?
SQL SSIS is the most useful aspect of the solution.
We find the product to be relatively stable.
The solution seems to be pretty flexible.
What needs improvement?
Due to the fact that I'm dealing with the product more as a data analyst, the SQL Server management studio is really relatively primitive compared to other more advanced tools. There are other tools on the market that are much more advanced. It would be better if they managed to give us a bit more of a user-friendly product with just a bit more meat on the bone. It's a bit basic.
There are a number of features that are lacking. Just recently I had to do something and it's not available on the SQL Server. However, it's available on another solution that's actually a much cheaper product.
Some areas need improvement. For example, how you deal with the manipulation of data is probably not the best.
For how long have I used the solution?
While I haven't constantly used the product all of the time, overall, I've used it for over 10 years at this point. I have quite a few years of experience with it.
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 quite stable. It doesn't have issues with bugs or glitches. It doesn't crash or freeze. It's good.
What do I think about the scalability of the solution?
In general, the solution is scalable. Microsoft, compared to the others, tends to focus more on the programming ability of the solution rather than the user experience. Rather than making it more user-friendly, they tend to make it more program-friendly.
We have about 70 users on the solution currently.
It's my understanding that the client is planning to scale up to be able to take on more customers in the near future. They may therefore increase usage.
How are customer service and support?
Mostly, I personally am on the analytics and new project development side of things in our organization. Therefore, I typically don't deal with technical support. I can't speak to how supportive, knowledgeable, or responsive they are.
Which solution did I use previously and why did I switch?
I typically use SQL wherever I go, however, I don't necessarily use Microsoft all the time. I also occasionally use a solution called Teradata.
How was the initial setup?
I was not involved in the installation of the solution. I'm more on the side of creating metadata. Therefore, it would be difficult for me to comment on if the solution was easy or difficult to implement or how our team deployed it. I don't have any exact details on that front.
What's my experience with pricing, setup cost, and licensing?
While there are costs involved in using the product, I'm not a part of the billing or payments team. I can't speak to how much the solution costs or how much our organization pays. I do not know if it's monthly or yearly and how long our contract is for, if we have one.
What other advice do I have?
I'm using the 2016 or 2017 version of the solution.
There are many SQL options. I'd only recommend this one if it made sense to the individual company and their requirements.
In general, I'd rate the solution at an eight out of ten.
Which deployment model are you using for this solution?
Public Cloud
If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?
Amazon Web Services (AWS)
Disclosure: I am a real user, and this review is based on my own experience and opinions.
Software Architect at a tech consulting company with 51-200 employees
Enabled us to use an Agile approach to the design and implementation of DW solutions.
What is most valuable?
- SQL Server Integration Services tools
- Data Quality Services tools
- Master Data Services tools
- SQL Server Reporting Services tools
- Data Partitioning (Horizontal Partitioning) tools
- ColumnStore Indices
- In-Memory OLTP tables
How has it helped my organization?
We design and implement DW solutions with SS 2016 Dev Ed tools. This solution has given us high levels of productivity, which has allowed us to use an Agile approach to the design and implementation of DW solutions for our customers, and this Agile approach has in turn given us a competitive advantage in our market.
We have also started exploring the use of Microsoft R Client, MS R Services and MS R Server with SQL Server 2016 Dev Ed, which are part of the hosted Data Science package.
We are also looking forward the inclusion of Python support in SQL Server 2017 for said hosted Data Science package.
We are very interested in complementing DW solutions with Data Science and Machine Learning solutions, which could be a major plus for our existing DW customers, even though all hosted data science tools are only available in Enterprise Ed (for our customers), which again presents the same limiting factor (budget) already mentioned.
Having said that, we see that the potential that the hosted Data Science tools offer to some of our customers is large enough to be explored and considered on a case by case basis, with proper ROI analysis.
What needs improvement?
We do not have much to complain about SS 2016 Dev Ed in itself, we do have some complaints regarding licensing for SQL Server 2016 Enterprise Ed. In an emerging market like Argentina, it is very steep for our customers to pay U$S 28,000 or more on licensing for an instance of SS 2016 Enterprise Ed, and this poses a limiting factor to our growth.
For how long have I used the solution?
We have been using SS 2016 Dev Ed for a few months so far, but have been using the previous version (SS 2014 Dev Ed) for more than two years.
What was my experience with deployment of the solution?
The deployment tools for DW solutions in both 2014 and 2016 editions of SQL Server are part of the SQL Server Data Tools (SSDT) package. As SSDT is based on Visual Studio, this toolset has been very stable since its inception, both in terms of performance as well as in terms of functionality, so, deployment in 2016 is done in the same way as in 2014, which translates into no issues during deployment.
What do I think about the stability of the solution?
There were no stability issues.
What do I think about the scalability of the solution?
There were no scalability issues, even though the Dev Ed does not offer the same level of performance and scalability that the equivalent Enterprise Ed offers.
Pertaining to the hosted Data Science package that we have been exploring, we have found an important increase in scalability when comparing the performance of a given solution running as hosted, and the same solution running on the same server with only client R tools.
This scalability advantage presents itself as an important reason to consider these tools as a viable solution to some of our DW customers.
How are customer service and technical support?
Customer Service:
As usual, MS offers a very good customer service. The amount of resources (self-study materials, online courses, tutorials) is huge, most of it is free.
Paid customer service is also very good.
Technical Support:Paid tech support is very good and efficient.
Which solution did I use previously and why did I switch?
I have always used DW tools from Microsoft since SQL Server 2000.
How was the initial setup?
If prior to the setup you do the proper training, there are no issues with setup, but the learning curve is wide and tall.
You could get started fast and sure if you stick to the many Wizards included with the tools, but the scope of said Wizards is limited.
What about the implementation team?
We did not have deployment/implementation issues.
What was our ROI?
Since SS 2014 Dev Ed, MS is offering these tools free of charge, ROI mainly is focused around training investment. As I have said, we do the training in-house. ROI is around one year (12 months).
What's my experience with pricing, setup cost, and licensing?
No issues with pricing and licensing for SS 2016 Dev Ed, as it is free of charge, as mentioned above, the thorny issue with pricing and licensing is with customers. We do our best to design DW solutions that can cover reqs from our customers within the capabilities of SS 2016 Standard Ed.
Which other solutions did I evaluate?
The cost-benefit ratio offered by Microsoft's DW solutions is, by a long shot, much more convenient for our customers (small and medium companies) than solutions from other vendors, hands down.
What other advice do I have?
Consider the ROI (most training investment). If training is not in-house, only hire training from an official Microsoft Training Center in your region. Look for the best Training Center. Once you are done with the training, you can start taking customers for DW projects.
Disclosure: My company has a business relationship with this vendor other than being a customer: I teach MOC courses on the design and implementation of DW solutions with the aforementioned tools.
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.
IT Consultant & IT Project Manager Assistant with 10,001+ employees
SSIS, SSRS, and DB help in everything.
What is most valuable?
How has it helped my organization?
There is improvement in the performances and stability.
What needs improvement?
SSIS needs improvement.
I think that it should be easier in managing SQL packages, especially when we have multiple environments. With Kerberos Authentication, we had different issues on this and sometimes, we needed Microsoft Support too. Thus, a better and an organized SQL package review is needed.
What do I think about the stability of the solution?
When using HA (high availability), we experienced some stability issues.
What do I think about the scalability of the solution?
There were no scalability issues.
How are customer service and technical support?
Technical support is the best, I would give them a 10/10 rating.
Which solution did I use previously and why did I switch?
We were using a few other solutions such as MySQL, Oracle and Pervasive PSQL.
What's my experience with pricing, setup cost, and licensing?
It’s okay as compared to the features that it has.
Which other solutions did I evaluate?
We evaluated the Oracle solution.
What other advice do I have?
If you want stability, then choose the best.
Disclosure: I am a real user, and this review is based on my own experience and opinions.
Software Architect at a tech consulting company with 51-200 employees
Provides data quality services tools and In-Memory OLTP tables.
What is most valuable?
SQL Server integration services tools
Data quality services tools
Master data services tools
SQL Server reporting services tools
Data partitioning (horizontal partitioning) tools
ColumnStore indexes
In-memory OLTP tables
How has it helped my organization?
We design and implement data warehouse solutions with SQL Server 2016 Developer Edition tools. This solution has:
Given us high levels of productivity
Allowed us to use an agile approach to the design and implementation of data warehouse solutions for our customers
Given us a competitive advantage in our market
What needs improvement?
We do not have much to complain about SQL Server 2016 Developer Edition in itself.
We do have some complaints regarding licensing. In an emerging market like Argentina, it is very steep for our customers to pay USD 28,000 or more on licensing for an instance of SQL Server 2016 Enterprise Edition. This poses a limiting factor to our growth.
For how long have I used the solution?
We have been using SQL Server 2016 Developer Edition for a few months so far. We have been using the previous version (SQL Server 2014 Developer Edition) for more than two years.
What was my experience with deployment of the solution?
We did not encounter any deployment issues.
What do I think about the stability of the solution?
We did not encounter any stability issues.
What do I think about the scalability of the solution?
We did not encounter any scalability issues. This is the case even though the Developers Edition does not offer the same level of performance and scalability that the equivalent Enterprise Edition offers.
How are customer service and technical support?
Customer Service:
As usual, Microsoft offers very good customer service. The amount of resources (self-study materials, online courses, and tutorials) is huge and most of it is free. Paid customer service is also very good.
Technical Support:Paid technical support is very good and efficient.
Which solution did I use previously and why did I switch?
I have used data warehouse tools from Microsoft since SQL Server 2000.
How was the initial setup?
If you do the proper training prior to the setup, there will be no issues. However, the learning curve is wide and tall.
You could get started fast and sure if you stick to the many wizards included with the tools. However, the scope of those said wizards is limited.
What about the implementation team?
We implemented with an in-house team only, with proper, prior training that was also done in-house.
What was our ROI?
Since SQL Server 2014 Developer Edition, Microsoft has been offering these tools free of charge. The ROI is mainly focused around training investment. We do the training in-house, so the ROI is around one year.
What's my experience with pricing, setup cost, and licensing?
We have no issues with pricing and licensing for SQL Server 2016 Developer Edition, as it is free of charge. The thorny issue is with pricing and licensing with customers.
We do our best to design data warehouse solutions that can cover requirements from our customers within the capabilities of SQL Server 2016 Standard Edition.
Which other solutions did I evaluate?
The cost-benefit ratio offered by Microsoft's data warehouse solutions is, by a long shot, much more convenient for our customers, small and medium sized companies, than solutions from other vendors.
What other advice do I have?
My advice is focused on companies that develop and offer data warehouse solutions for customers that use SQL Server. Consider the ROI, which is mostly training investment (for the Developer Edition). If training is not done in-house, only hire training from an official Microsoft training center in your region. Look for the best training center. Once you are done with the training, you can start taking customers for data warehouse projects.
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
The best-ever SQL Server release - again
Microsoft’s flagship database engine, SQL Server, keeps getting better with every release. The SQL Server 2014 platform is the best-ever SQL Server release, and is packed full of features for organizations of all sizes.
Every organization has different requirements for data. Vendors might specify a particular product or platform for their software. In-house development staff might be geared towards one platform over others. Management might have their preferences. SQL Server might not be right for all shops out there, but I can state that it provides the same scalability, flexibility, and raw power of other DBMS platforms on the market, and does it with the easiest to manage suite of features that I encounter. I enjoy this product and the technical community that has grown up around this product so much that I have dedicated this portion of my career to the mastery of SQL Server as a database and architecture consultant. SQL Server 2014 continues the platform’s evolution towards the future, and I continue to stand by it.
The core database engine is one of the easiest portions of the product to administer via the included SQL Server Management Studio tool. Quite a few of the SQL Server installations that I encounter in the wild are installed by non-DBAs who just click through the installation wizard and stand up their required SQL Server instances. This simplicity is one of the product’s double-edged swords, because even though it is trivial to install, non-DBAs tend to skip the best practices around infrastructure architecture, installation, post-installation configuration, and ongoing management that helps the product to really shine.
The Enterprise edition contains an updated and enhanced feature called AlwaysOn, and it allows for the simple setup of highly available databases so that the data is available if a server fails. It also plays a double role in allowing for the setup of disaster recovery database servers so that if an entire datacenter fails, applications can continue to work with only a minor interruption in service (usually measured in seconds). Failover and failback are trivial, and a single interface is all that is required to manage the entire setup. I love this feature, and as my clients are starting to migrate to SQL Server 2012 and SQL Server 2014, see a tremendous increase in AlwaysOn adoption at the moment.
The other huge feature is with In-Memory OLTP, or codename Hekaton. It is in-memory extensions that allow an application to begin to use memory to dramatically improve the performance of an application with only minor modifications to the app code.
Other features included in the core engine and licenses editions of the production include:
- Backup encryption to make things more secure
- Resource governance to keep high trafficked databases from being ‘noisy neighbors’ to other application databases
- Data and backup encryption
- Finely tuned security levels, based on your organization’s requirements
- Integration Services - that includes a graphical means to transport, load, and transform data
- Analysis Services – build data warehouses and cubes to help you gain serious insight into your business trends
- PowerPivot for Excel to allow your end users to manage and transform the data that they require for decision support processes
- Reporting Services – grant your users the ability to run and schedule their own reports in a simple to use management interface
- Report Builder – advanced end users can construct their own reports, and even their own queries with the ‘model’ of the data that you present to them
SQL Server also now has the ability to move data into and out of the public cloud with ease through backing up to Microsoft’s Azure platform.
If you currently have SQL Servers in your organization, run – don’t walk – to SQL Server 2014. If you have some of the other database platforms on the market, consider migrating to SQL Server so you can reduce licensing costs, improve scalability while reducing complexity, and increase the number of database that a single DBA can individually manage.
Pros: Tremendous scalability. Easy to use and manage. Blur High Availability and Disaster Recovery with AlwaysOn Database Availability Groups. Business intelligence tools increases business insight into data.
Cons: The licensing has persisted the per-core model, and as a result the cost for the platform stays higher than expected. Adding software assurance, which I consider a must for virtualizing SQL Server, also drives up the cost.
Disclosure: I am a real user, and this review is based on my own experience and opinions.
Admin at IEC (Electoral Commission of South Africa)
Stable and scalable data storage for enterprise applications
Pros and Cons
- "SQL is stable."
- "SQL could be improved by making all features available on the on-premise version of the product as well as the cloud version. When you buy the on-premise version, it's sort of an inferior product compared to the cloud version, which seems to get most of the latest and greatest features."
What is our primary use case?
SQL is our main data store for enterprise applications, all applications that we have in the organization.
What needs improvement?
SQL could be improved by making all features available on the on-premise version of the product as well as the cloud version. When you buy the on-premise version, it's sort of an inferior product compared to the cloud version, which seems to get most of the latest and greatest features.
For how long have I used the solution?
I've been using this solution for a few years.
What do I think about the stability of the solution?
SQL is stable.
What do I think about the scalability of the solution?
This solution is scalable.
How are customer service and support?
I am satisfied with Microsoft's technical support.
How was the initial setup?
The initial setup was ok, it met our requirements.
What about the implementation team?
We implemented SQL ourselves, and it took around a week to install.
What's my experience with pricing, setup cost, and licensing?
Subscriptions are available on a yearly basis.
What other advice do I have?
I would give SQL a score of 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.
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?
We have been using SQL Server for more than 10 or 15 years.
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.
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.
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.
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?
@KathyC, I really appreciate your thoughtful remarks on my review. Feedback is always welcome, as it helps all reviewers to focus on what is important to our peers.
Kind regards, GEN