stormhoogl.blogg.se - Sql versions

#Sql versions install#

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.In all, I just can’t recommend 2012 new installs today. You either don’t need robust encryption for your backups, or you’re willing to buy a third party tool to get it.Ģ012 introduced a few other features – Availability Groups, columnstore indexes, contained databases, Data Quality Services – but they were so limited that it’s hard to consider this a good starting point for those features today.You’re comfortable being out of support (because support ends in July 2022.).You’re dealing with an application whose newest supported version is only SQL Server 2012, but not 2014 or newer.But I got a really good deal on this CD at a garage sale You should consider SQL Server 2012 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?

#Sql versions install#

Wait! Before you install that next SQL Server, hold up.