You need faster performance without changing the code, and you have lots of time to put into testing – 2014’s Cardinality Estimator (CE) changes made for different execution plans, but they’re not across-the-board better.You use log shipping as a reporting tool, and you have tricky permissions requirements (because they added new server-level roles that make this easier.).You need to encrypt your backups, and you’re not willing to buy a third party backup tool.I’d just consider this a minimum starting point for even considering AGs (forget 2012) because starting with 2014, the secondary is readable even when the primary is down. You want to use Always On Availability Groups – but I’m even hesitant to put that here, because they continue to get dramatically better in subsequent versions.You’re dealing with an application whose newest supported version is only SQL Server 2014, but not 2016 or newer.But I got a really good deal on this CD at a garage sale You should consider SQL Server 2014 if… I’m going to go from the dark ages forward, making a sales pitch for each newer version. I know, management wants you to stay on an older build, and the vendor says they’ll only support older versions, but now’s your chance to make your case for a newer version – and I’m gonna help you do it. Are you sure you’re using the right version? Wait! Before you install that next SQL Server, hold up.
0 kommentar(er)
