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.