Microsoft SQL Server
Updated May 05, 2021

Microsoft SQL Server

Anonymous | TrustRadius Reviewer
Score 9 out of 10
Vetted Review
Verified User
Review Source

Overall Satisfaction with Microsoft SQL Server

Our business's in house desktop and web applications run off a SQL Server database. We have used it (and abused it) for 12 or so years now. I don't personally have experience with other databases (a little MySQL) but so far I haven't come across a scenario where SQL Server has been lacking, and that is coming from someone who advocates putting the business logic in SP's (OK, let's not start down that path...).
  • Stored procedures, efficient and so much easier to update business logic when under pressure!
  • High availability always on groups (since 2012), is pretty easy to set up and just works - has been an absolute savior on 2 server failures.
  • Fairly straightforward to administer out the box as it were (but this can be enhanced see below).
  • So widely used that someone somewhere has probably faced the same challenges that you have so [to] find a guide, solution, suggested path is relatively easy (not strictly a SQL server thing but makes a massive difference knowing that you have access to huge resource with a well supported well adopted piece of software).
  • Very well supported in terms of third party software to enhance administration (backups, performance, etc.).
  • Enterprise is unbelievably expensive.
  • Not tolerant of bad practices and poor query writing, really shows up when you do it badly!
  • Deep insight into what is happening with query performance is not especially great (but as mentioned in the "Pros", software support from third parties does cover this).
  • Fast to deliver adhoc reports for managers wanting to know what's going on. We have junior team members that have picked the language (and the business logic quickly enough to do that).
  • Very reliable, cannot say I have had issue with the software (as mentioned had at least 2 unrelated hardware failures but Always On has saved us).
  • Business logic in stored procedures allows for quick changes to enhance the business and allow for quick reactions to circumstance.
On this one, I cannot fairly comment as I was not involved in the original decision making behind choosing SQL Server. I am aware that MySQL was a contender, and as mentioned I have some experience but not vast. I am pleased that we didn't go with MySQL at least as I think that SQL Server is overall more powerful and more robust a product, but it is expensive in comparison.

Do you think Microsoft SQL Server delivers good value for the price?

Yes

Are you happy with Microsoft SQL Server's feature set?

Yes

Did Microsoft SQL Server live up to sales and marketing promises?

I wasn't involved with the selection/purchase process

Did implementation of Microsoft SQL Server go as expected?

Yes

Would you buy Microsoft SQL Server again?

Yes

I have grown very fond of SQL Server, as I say I don't have a lot of experience with other relational databases, but I haven't hit upon a limitation within our use cases. Its TSQL is a pretty easy (scripting) language to pick up, stored procedures are very powerful and offer efficiency and security, not to mention allowing for quick changes to logic can be a real time-saver.

I will say I have had limited joy with text search (full-text indexing) to achieve better text searching results, but that's probably done to me. It's the one area I have never really managed to find a great guide on though.