We primarily use SQL Server as a database management system.
This solution is deployed on-prem.
We primarily use SQL Server as a database management system.
This solution is deployed on-prem.
One of the most valuable features of SQL Server is that it's easy to use.
SQL Server could be improved with cheaper licensing because it's very expensive.
We have been using SQL Server since 2016, so more than five years.
This solution is stable.
Before implementing SQL Server, we used Oracle. We switched to SQL Server because it had good integration.
The installation is straightforward. I was able to handle deployment and maintenance by myself.
We implemented this solution through an in-house team.
For licensing, we pay yearly. The licensing is very expensive, and it should be cheaper.
I rate SQL Server an eight out of ten. I would recommend it to others, as long is it meets their requirements.
We have a large amount of information and data. We are using a lot of business models for our menu mix.
Because we are using the solution from an analytics perspective, the performance is good. We have a large amount of information in our dashboard. The data navigation could be improved.
We are using the net for our environment. We're using the ADF Azure data factory for our analysis services, and it is pretty good.
Something that could be improved is the cost because it's very high. That's the only thing I'm concerned about but the technology is good. We are looking forward to getting some discounts because we have a large amount of data.
I have been using this solution for three and a half years. The solution is deployed on a public cloud. Azure is the cloud provider.
It's much more stable. It's good. We haven't had any downtime during the past two years. The solution has gone down maybe once.
It should be scalable within the coming years because data is growing and the business is growing.
Right now we have about 300 users, but by next year we might have around 2,000 because we also have a retail side, which could also use the platform. Some of their roles are in the executive layers and the managers layers, and reporting line people also.
We are planning to increase the usage. This is a transformation phase, so we are currently using SAP business objects, and we are on the Oracle database. We just moved to Azure cloud with the data warehouse and Power BI tools.
My team works with support. As far as I know the technical support is good, but occasionally it takes a little bit of time.
Previously, I was using SAP, which is good. The technology is great. It has many more features than Microsoft SQL, like the data architect and performance.
My plan was to use SAP HANA, but we had an acquisition in our company, so we got a new team and new managers. The head of BI decided to go with Microsoft, however, my POC was already accepted with SAP HANA and AWS cloud hosting. We went in the other direction and started using SQL because the people who were hired were more familiar with the Microsoft technology rather than SAP.
It is mostly straightforward. There were no issues. It takes about two or three months to prepare. Development takes another three months. It takes almost one year to just kick off the project with live production.
For deployment and maintenance, we used seven or eight people. Most of them were developers and DBAs, and some of them were business analysts.
We used in-house developers and had some consultation from Microsoft.
There is a return on investment because based on analytics, we are reducing the number of people who are doing the analytical part so that it's an automated process, and the data will be available to everyone, including business users.
Licensing fees increase depending on size and performance. If you want higher performance, you should go for a different course.
I would rate this solution 7 out of 10.
My advice is to know your use case and requirements so that you aren't surprised after deciding to get this product and realizing in the implementation that you need much more space. You at least need to make a massive POC to know if the product will give you 100% what you need.
SQL Server can be used for managing and storing information.
I have a lot of databases with more than one terabyte of information and we use technology, such as Stretch database to switch out the information to Azure databases with this type of technology.
SQL Server could improve the integration with nonrational database solutions, such as MongoDB.
I have been using SQL Server for eight years.
SQL Server has good performance. It is one of the best features.
We have approximately 300 instances of SQL Server.
I have approximately five customers using this solution.
I currently have one ticket open with Microsoft support and I have been waiting about two days. However, it's not a critical incident. The technical support they provide us is good.
In the latest version of SQL Server, Microsoft has split the product. For example, if you want to start with the engine or the reporting server you have to download it separately. I think that the installation is easier on the new versions. There are other kinds of options that you can set up in the installation progress. For example, the number of 10 DV files or the limit of maximum use of memory.
The installation process takes approximately 10 minutes.
There is a license to use this solution. However, the model is not easy to understand. There is a guide you have to read about all the information on how it works. If you read this documentation, you can understand how it works. We are paying for our SQL Servers by CPU cores with an enterprise license.
If a new company wants to implement SQL Server, they need to know that there should be a person who has all the knowledge about DBA position, such as how the SQL Server will be set up because I have a lot of customers and when I checked they have a lot of bad options or practicing in their SQL Servers instance. If someone wants to start with SQL Server, they have to improve and have good knowledge about this technology. It's important to have knowledge about this technology. They should take some courses or maybe have a person who has all the knowledge about this technology with certification, it's the most important. It's not easy to keep up to date with the best practice from a provider, in this case, Microsoft.
I rate SQL Server a seven out of ten.
SQL Server is used for storing data.
I have found SQL Server easy to use.
SQL Server could improve by having better usability or user guidance.
I have been using SQL Server for approximately five years.
The solution is stable and the performance is good.
SQL Server is scalable.
I have not needed to contact support.
The implementation was done by our IT department.
We did the implementation in-house.
The price of the solution is fine.
I would recommend this solution to others.
I rate SQL Server an eight out of ten.
Out of all the tools in the complete SQL Server package, I'm mainly using Toolbox and SQL Profiler because I'm using SSIS packets, so we're using job scheduling a lot. And sometimes we are creating the SSIS packages, so I'm using SQL Server for MSD for maintenance purposes. SQL Server is quite user-friendly. I have experience with Oracle and PostgreSQL, so out of three, I like SQL Server a lot.
They could increase the intelligence of SQL Server. That would be good for us. There are some good intelligent features in SQL Server. However, they need to increase the intelligence because people switching to SQL Server from other solutions are not so familiar with it. I've been working with SQL Server for the last six years, but people are coming from MySQL or Oracle, so it will take one or two months to adjust. Still, they could add some intelligent tools to convert Oracle into SQL Server something like that.
And sometimes when I'm writing a function, there is already a predefined structure available. So if they defined their structure more precisely, that would be good for us. And the last thing I would like to add is that SQL Server should handle queries more like Oracle does. For example, you submit a query in Oracle, and the whole table comes up. In SQL Server, you go to the table, right-click, and it lets you see the first 200 rows. Then on top of that, you can add 200 more rows.
So in place of those 200 rows, if I can update all my table records or search my table record without a new search query, it'll be very beneficial. That functionality exists in Oracle, but this feature is not available everywhere in SQL Server. So if SQL Server had the feature, it'd be great because SQL Server is lacking only on this point. For example, one of my clients is a semi-technical person, so I have to train them to file a query in SQL. And they say that Oracle is much better. Say, for example, that I wanted to query a particular employee from a list of all staff. So the query output comes, and they can directly filter out the data by just applying the filter. They don't have to use the drop-down menu and search for all the employees with a given name.
I've been using SQL Server for the last six years. I'm working with SSIS, SSRS, or MDS. These tools are part of SQL Server, and the back-end queries are developed in SQL Server.
SQL Server is stable. SQL Server has crashed only two times in six years, but it wasn't a major system error.
It may be a licensing issue, but sometimes its operating speed becomes slow if we have multiple users. It's lacking some performance, but it's acceptable because we have a heavy load. And I would like to add that we're running SQL Server and SSIS at the same time. So while I've found that SQL Server is quite fast, SSIS is a part of SQL Server. It is just for data testing in India. But if a person knows SSIS, then they usually have very little knowledge about SQL and vice versa.
I know both of them. I found that maybe it's a bad habit, but I'm using SSIS packages. And in the SSIS package, I'm using Toolbox from SQL Server to improve the latency. Implementing both together takes a little time. And one more point is data handling. I am just forwarding the error names, and there are multiple errors in the SQL Server tool, but what if a person comes to work under me and has only one or two years of experience? Sometimes it might be difficult for them to understand what the errors mean. For example, when joining data, it's easy to implement the inner joint. In the inner joint, there are two columns, so when there's an output error, someone who is inexperienced with SQL Server might not understand. Error messages should be a little more precise and defined, so it's easy to understand.
Setting up an individual SQL Server is pretty straightforward, but when you are implementing multiple tools, it's more complicated. In terms of maintenance, for the DBA part, there are two based in my company because I am on a master device, so they don't allow me to maintain the server part. So one person is from South Korea, and the other is from China. They are handling my SQL Server. So maybe there are multiple teams, but I am contacting these two guys, the DBA. And I'm MDS, so I'm a single person. There are two people on my team, and I have one junior staff member. So I have a three-person team, and there are two DBA sites because I'm discussing my master team. I am deployed on the business side, and there are more than 80 people who are end-users of SQL.
If you're using SQL Server along with SSIS and SSRS tools, it works pretty smoothly and all. When working with Oracle SQL, PostgreSQL, MySQL, etc, there are a few problems with the connection.
Overall, SQL Server is good, but sometimes, optimization becomes a little bit tricky when you're using SQL Servers in place of Oracle. For example, while I was implementing two queries one time, the SQL Server gave me the wrong results. This wasn't because of their internal modules. So there may have been some missing data, but SQL Server failed to identify those issues. SQL Server needs to improve there.
For example, say there is a line with a value of 136 or 137. The second value is a space, and the third value is null. And the last one is space. So a space means this is also null. So you are comparing these four values, and if you don't have any idea about data, it's a little problematic. So cases like this, we can deal with such queries using syntax, but if a person has no idea how to deal with this, they'll face an issue.
Here's another example. Say there's a team query that means we are erasing data from the teams, and some people are just analyzing the string. So I see data from it, which means the calling system is there. In the calling system, we receive the data to call anyone, and that type of wire call setup is there. So I am receiving a full-text format from the file I have to upload in the SSIS package. And some cells have a null value. It's a text file, so you can understand there are blanks in some places. I don't know the file type, so I am just trying to dump it into our SQL Server. But when I have time to get to that table, I realize that some values are null, space, and blank. So these four values make problems for me.
I rate SQL Server nine out of 10. I would recommend SQL Server to anyone because you can use cloud-based services, so it's very beneficial. If you install SQL Server on-premise and on the Azure cloud, it is much more advantageous for you.
We use SQL Server as a database solution.
The performance of the SQL Server is very good.
I have been using SQL Server for a few years.
The stability is very good.
The solution is scalable. However, we do not have many large servers using SQL Server anymore, we have moved to SAP HANA.
We have approximately 2,000 users using this solution in my organization.
The support offered by Microsoft is very good. We have not faced any issues with SQL Server to need to contact their support.
We use SAP HANA as a database solution for certain use cases.
We have technical managers and engineers that do the maintenance and support for this solution.
We are on an annual enterprise license for the solution and the cost of the license could be reduced.
I rate SQL Server an eight out of ten.
We have hundreds of databases that are using SEL Server and there may be other capabilities.
It's a standard product that is used with standard applications, which is why we use it.
There is no lack of features.
There are newer models that are available on the market. The agility of the non-SQL-based features is relevant on the market.
Integration is one thing but it's making use of all the iterations or the new cloud data result.
Today's architectures are in many different directions. Not always via SQL relational databases, but also NoSQL databases, and they have a pretty good Java database as well.
We have been using SQL Server in our organization for 10 years, but I am not a day-to-day user.
We use a couple of the versions. We have used the 2016 version and most likely have used some newer versions as well.
SQL Server is a stable product.
We don't have any issues with the scalability of SQL Server.
We have hundreds of thousands of applications using this solution.
We have a dedicated Microsoft account team and we have also dedicated support conditions.
Areas in our organization use AWS Lambda.
We use other relational databases. The most important product besides SQL Server is Oracle. We use SQL Server and Oracle equally.
I am not a patient person with installations, but there are no issues with the installation of this solution.
We have a database team to maintain this solution along with an engineering team, an operational team and we have eternal resources.
The enterprise-level license agreement is very complicated. It's complex, not only with SQL server but with a number of products.
I would recommend this solution to others.
I would rate SQL Server an eight out of ten.
Despite the core database is not SQL Server in my working company, SQL Server is widely being used as the backend for many in-house applications and customized applications like Solarwinds.
Helping to effectively and efficiently manage the business-critical data
- There are hundreds of "Dynamic Management Views" (DMVs) & Dynamic Management Functions (DMFs) that are system views & system functions that return metadata of the system state and they provide valuable insight into the current SQL instance state.
- Resumable online index rebuild
- Table Partitioning and the Swap out to covert a Table Partition into a separate table.
- Python & R2 Integration, Graph Databases
- Automatic Database Tuning
- Very reliable Backup technology and many more
The price could be better:
Compare to Oracle it is cheaper but with the existence of many open source databases currently in the market, consider reducing the Licensing cost. Secondly, with the Core-based Licensing since SQL 2012 Version, the SQL Licensing price has substantially increased.
Postgres Extensions is a concept in Postgres to extend the Postgres features that are very useful for Performance Monitoring & Optimizations. Similarly option to extend the features as necessary.
I have been using SQL Server for 12 years.
It's been scalable since 2016. With each version, they are adding more features which are very helpful.
On a rare occasion, I had contacted technical support about five or six years ago and only when I had a specific use case.
The GUI-based step-by-step initial setup is easier for the initial setup and even the Jr.DBAs can handle it with minimal training. The automated installation is possible with PowerShell Scripts and the Infrastructure Provisioning and Configurations tools like Ansible. We managed to automate the SQL installation using Ansible Playbooks and Gitlab to deploy Continous Integration and Continous Deployment.
We implemented this solution by ourselves.
CPU Core-based Licensing & Windows Licensing costs are additional overheads compare to open source databases like MySQL and PostgreSQL.
Managed SQL Server Database Service in Azure is lagging with many features like Linked Server, DB Mail.
SQL Server deployment in the Cloud does not seem to be cost-effective with respect to the Licensing cost and average Life cycle of 5 years (I reiterate, this is in my opinion).
If you take Postgre SQL and MySQL, they provide almost all the same features even though they are both open source databases.
I recommend this solution because you can engage in database manipulation, administration and manage almost all your requirements. When compared to Oracle licensing costs, SQL Server is better.
On a scale from one to ten, I would give SQL Server a ten.
We primarily use the solution mainly for databases on all types of applications.
SQL is the all around leading Database server
The solution is very stable.
The scalability of the product is great.
We'd like the deployment process to be better in the future.
The licensing is pretty expensive.
I've been using the solution for 20 years at this point. It's been two decades. We've used it for a while now.
The solution is stable and the performance is great. There are no bugs or glitches. It doesn't crash or freeze.
The product scales well. If you need to expand it, you can do so.
We have 900 to 1,000 people using it currently.
I'm more on the architecture side and therefore do not directly deal with technical support. I cannot speak to how helpful or responsive they are.
We also use Oracle. We've used it for over a decade already.
The deployment could be easier.
While the deployment only takes about 15 minutes, you have to follow up with a lot of configuration.
We handled the implementation ourselves. We did not enlist the assistance of any integrators or consultants. It was all handled in-house.
We're paying too much for licensing at this time. They need to work on the pricing. They could be cheaper, however, it's also difficult to run the licenses in the right way.
We pay licensing fees on a yearly basis.
We're a customer and an end-user. We don't have a business relationship with SQL.
While everything is currently on-premises, we're making moves to shift to the cloud.
We're using the 2019 and 2016 versions of the product.
I'd rate the solution at an eight out of ten. In general, we've been quite happy with its capabilities.
The solution is an RDBMS and can be used to simplify customers' requirements for a back-end database. The main function of the solution is to store information from front-end users.
The most valuable feature of the solution, compared to other RDBMS solutions, such as Oracle MySQL or IBM DB2, it is more user-friendly and has backward compatibility. For example, if you have an application that requires an old version of SQL Server and you have the latest version of the license, you are able to install and use it in backward compatibility mode. They keep supporting the existing legacy application. Additionally, the solution is simple and if it is configured properly it performs very well.
I have used the solution for approximately six years.
I find the solution to be very stable.
The solution is scalable.
The technical support is only provided to the customers having a subscription-based license with a Software Assurance server. For other forms of licensing the solution will not provide support.
I have previously used other RDBMS solutions, such as Oracle MySQL, Maria DB, PostgreSQL, and IBM DB2.
When comparing PostgreSQL, Oracle MySQL, and Microsoft SQL, Microsoft SQL has an advantage over the other two server databases because it provides a graphical user interface by default.
The initial setup of the solution is very easy and the time it takes depends on the architecture required. If the deployment of a cluster is required then the setup may take up to three hours, whereas standard environment deployment needs half an hour.
The solution can be installed by our selves but the use of an integrator makes it much easier.
The solution requires authorization in either the form of perpetual licensing or subscription-based licenses for two years. If a perpetual license version is purchased then customers have it to the end of life, whereas a subscription-based called server with Software Assurance, has to be renewed every two years.
The areas that need improvement are with regards to the commercial aspect of the solution, the licensing cost could be reduced in order to help customers to adopt it.
I would recommend this solution. However, the customer has to make sure it fits their use case.
I rate SQL Server a nine out of ten.
