SQL Server 2014 has gotten pretty doggone stable. For evidence, I give you the entire list of fixes in Service Pack 3, Cumulative Update 3:
- Query plans are different on cloned databases
- CDC source preview fails with an error
- Incorrect query results for columnstore filter pushdowns
- Log reader agent fails after AG failover when trace flag 1448 is enabled
And for the entire list of fixes in Service Pack 2, Cumulative Update 17:
- SQL jobs fail due to blocking in SSISDB
- Fail to join the secondary replica if the database has a defunct filegroup
- Incorrect query results for columnstore filter pushdowns
And…that’s it. That’s the mark of a pretty stable version. (Or, well, uh, it could also be the mark of a completely lazy group of developers who have stopped fixing bugs, but I prefer to believe the former.)
1 Comment. Leave new
For what it’s worth, I opened a support case with MS not too long ago for a bug in SSAS 2014 that caused the service to crash. I was told it was fixed in 2016 and there were no plans to port the fix to 2014. The recommendation was to upgrade, so there might be something to the lazy group of developers theory.