I use this solution as our data warehouse.
We use the reports, data analysis, and for connecting our databases to multiple resources.
I use this solution as our data warehouse.
We use the reports, data analysis, and for connecting our databases to multiple resources.
It's a flexible solution.
The installation process should be simplified.
The configuration could be easier.
I have been using SQL Server for a couple of months.
It's a stable solution. We have no issues with the stability.
We have 10 users in our organization who are using this solution.
We have a team made up of engineers, data analysts, and some developers to maintain this solution.
We have plans to increase your usage.
We have not contacted technical support.
Previously, I was using MySQL.
The installation is not easy, it could be easier.
It can take many hours to configure it.
I completed the installation myself.
It's a bit expensive.
The licensing is expensive.
I would recommend SQL Server to others.
I would rate SQL Server an eight out of ten.
It’s easy to develop and learn for newbies, and community MVP’s are so powerful and qualified, so info is easily accessible.
Also, SQL Server is not only a DBMS solution anymore, it is also a BI platform, and improvements are being made continuously.
SQL Server is our main RDBMS for SIS (Student Information System) and also our DWH, which are hosted on our SQL Server.
Version management, editor capabilities, CDC (change date capture), and some advanced analytic functions should be added; continuous integration solutions.
I’ve been developing with MS SQL Server for nearly 20 years, since Version 6.5.
Not in this version.
Yes, we did, with the 2008 version.
We have a yearly technical support agreement with a major partner. Consultant meetings are a requirement.
No. We’ve been using SQL Server for 17 years.
We’ve been using AlwaysOn availability groups for three years. It took a while to model the structure, but now it is stabilized, and safe with disaster recovery and failover configurations.
It was years ago, so it’s not relevant info anymore.
Database modeling and indexing best practices are so important. Do not defer to implement these practices. Before installation, planning different file groups for temp, data, and index files will help to gain performance and maintenance advantages.
Most of my clients are looking for a solution within the cloud on Azure and SQL Server databases. It is very cost-effective and scalable, meeting all requirements for small to medium-sized enterprises.
I generally do not deal with big enterprise organizations that need large data warehouse solutions, however, it fits the needs of those with small to medium data volume requirements.
The Azure SQL Server database requires almost zero maintenance and management. Once I set it up on Azure cloud, everything is managed automatically by the service, allowing me to start working with the database without worrying about administration tasks that are typically needed for on-premise databases.
SQL Server database capacities could be further increased to be more accessible for larger data requirements. Although some of these needs are being addressed by other services like Delta Lake, improving SQL Server's capacity would make it more suitable for larger enterprises.
I have used the solution for more than five years, possibly seven or eight years.
I would rate the stability a ten out of ten. It’s robust and reliable.
I would rate the scalability a ten out of ten, as it is highly scalable.
The technical support service probably rates about an eight out of ten. It is very commendable.
Positive
The initial setup is very straightforward and manageable, especially when setting it up on different occasions in the cloud environment.
The price point is very competitive and acceptable, often meeting approval from several clients who have used this solution.
I recommend SQL Server to others. It's a highly effective tool for many applications.
I would rate the overall solution an eight out of ten.