In the next year, both SQL hệ thống 2008/2008 R2 (July 8, 2019) & Windows hệ thống 2008/2008 R2 (Jan 14, 2020) are hitting their end-of-life dates. No more security patches*, hotfixes, or tư vấn from Microsoft. In this day và age, & with your regulatory environment, this is a certain deadline. Soon, if not already, your security and infrastructure audits should flag these versions of SQL server as a vulnerability.

Bạn đang xem: Github

What This Means for your Old SQL Servers

While both the over of life for these Windows and SQL versions present a clear và present danger to your compliance và stability, I’ll be talking mostly about the path forward for your SQL hệ thống environment.

Those long-needed vps upgrade projects need to get rolling. Keep in mind that both products are already outside “mainstream support” & are in “extended support”. In fact, these 2008/2008 R2 versions have been in “extended support” for years, meaning that Microsoft assistance isn’t free, no features are added, and only bug fixes & patches are released.

Your SQL server probably contains many databases, and probably serves one or more applications. At we have a thorough migration checklist for the planning, preparation, migration & testing phases. The safest way to lớn conduct SQL vps migrations is to proceed application by application. This method allows individual applications and their connection strings to lớn be tested with all the component pieces inside of the new SQL vps instance, while also ensuring safe rollback. If your SQL server hosts databases for multiple applications, each mix of databases will be migrated with the application in testing (as opposed to migrating all databases at once).

This is the safest way lớn migrate, because it contains changes when it comes lớn application testing, và ensures safe rollback.

Think Long-Term with Your tăng cấp Project

First off, we vì chưng not recommend an nâng cấp in place solution, where the potential rollback includes uninstalling programs in Windows Control Panel or reverting a VM image. You probably wouldn"t vày an in-place upgrade for your trang chủ PC operating system, so don"t try it with your mission-critical SQL Server.

Since SQL Server năm nhâm thìn and above require at least Windows vps 2012 operating system, now is the time lớn also tăng cấp the operating system & server virtualization/hardware. Take this opportunity—along with the scrutiny, outage, maintenance windows, & testing resources that comes with it—to upgrade the vps for the long-haul.

Upgrading the vps allows for many advantages before và after the migration outage. Prior to lớn the upgrade, we can take our time configuring, updating settings, and performance testing the new vps while normal operation continues. We can restore the old databases up to the new hệ thống many times, testing them and rehearsing our runbook. By leaving the old vps untouched, we retain it for quick và easy reference throughout our preparation phase, & also for failback at the time of migration. By using DNS aliases or Availability Group listeners, we can redirect application connection strings khổng lồ the new SQL server easily for a short, controlled outage. If there"s an issue, we redirect application connection strings back to lớn the untouched old SQL Server.

SQL vps is Built with Backwards Compatibility In Mind

SQL server has released 4 major versions since the 2010 release of SQL server 2008 R2, & each one has aggressively added features while maintaining a loyalty lớn reverse compatibility. There are no changes khổng lồ SQL vps since 2005 that break syntax or stop existing code from working. There are major performance improvements in new versions which are very welcomed và certainly beneficial.

In some edge cases, clients reported that only most of their code worked faster after upgrading to lớn SQL 2014. (Technical aside—I have had 2 clients since năm trước experience some query performance regression which was identified và addressed quickly. Given adequate preparation and knowledge, these issues can be identified & addressed before migration, & are not significant hurdles. I mention the SQL 2014 performance issues only as an honest but rare caveat; but otherwise, the enhanced cardinality estimator that was released in that version was a major improvement.)

The point of mentioning the incremental feature improvements and Microsoft"s stubborn loyalty khổng lồ prior compatibility levels is khổng lồ assure you that upgrading from SQL 2008/2008 R2 khổng lồ SQL hệ thống 2017 is safe and recommended. There is no need khổng lồ incrementally upgrade to 2012, 2014 or 2016. Upgrading straight to lớn SQL server 2017 – released over a year ago and patched monthly – can be successful with no code changes.

While SQL 2005 compatibility mode hasn"t been supported since 2012, SQL 2008 compatibility mode has been supported và will be supported through SQL 2019.

We Know Cost Savings are a Project Driver

The biggest reason that many environments stayed at SQL 2008/2008 R2 is for the old server-based licensing model. Starting with SQL server 2012, Microsoft moved to lớn charging chip core licensing, meaning that extremely high CPU-core machines became prohibitively expensive while 4-core boxes likely did not see an increase in licensing cost.

There are many ways to lớn save money on SQL hệ thống licensing when moving up from SQL 2008/2008 R2:

Server workload upgrade and consolidation, taking advantage of many performance improvements khổng lồ run more data on less hardware

Move and upgrade to lớn Azure VM’s with built-in SQL server licensing costs

Migrate lớn Azure VM’s running SQL vps 2008 and 2008 R2 – which will receive không tính phí additional years of Extended Security Updates

*That’s right – Extended Security Updates will be made available, but at a new and additional cost. If you have Software Assurance or an Enterprise Agreement, you can stay on SQL Server and Windows hệ thống 2008 và 2008 R2 for 3 more years by paying 75% of the cost of the latest version with the vi xử lý core licensing model. This is not exactly an affordable option, as you’d be paying near-new price for 9-year old software.

Highlights of New Features in Each Version Since SQL 2008 R2

Be sure to ask your DBA and/or the SQL DBA team about the following features:

SQL 2012 (11.0)

Introduction of Availability Groups: High Availability, Disaster Recovery, and Online readable secondary replicas

Generational improvements khổng lồ how SSIS packages are designed và deployed with the new Project deployment model

Introduction of Columnstore indexes, a crucial & easy-to-implement performance boost for reporting large data sets

SQL năm trước (12.0)

Enhancements further stabilize và improve performance of Availability Groups

In-memory table engine introduced for ultra-fast writes

Columnstore indexes are further enhanced, now writeable when the clustered index

Native backup encryption, native backup to lớn Azure blob store

Many performance improvements including the new cardinality estimator

SQL năm nhâm thìn (13.0)

With năm nhâm thìn SP1, many Enterprise features were moved down lớn Standard edition, lowering the cost for some key deployments, potentially reducing the need lớn buy Enterprise edition

Columnstore indexes are further enhanced, now writeable in all forms

Built-in AT TIME ZONE syntax for easy datetime time zone conversion

The Query Store feature allows developers to lớn have easy, detailed reporting on the worst-performing và most resource-consuming queries

New security features for regulated environments including Dynamic Data Masking, Always Encrypted, and Row màn chơi Security

Native JSON processing in the SQL engine

Better tooling và separate development cycles for Data Tools và Management Studio

Huge improvements for Reporting Services và incremental integration with PowerBI

Polybase query engine khổng lồ allow querying of Hadoop and Azure Blob files

Introduction of built-in Machine Learning services, the only commercial DB platform with this feature

SQL 2017 (14.0)

Huge improvements và new features for built-in Maintenance Plans, Availability Groups, index maintenance, performance of Columnstore indexes

SQL vps on Linux

Availability Groups get a clusterless option, full tư vấn for Distributed Transactions

New syntax additions prevent reinvention of the wheel for common string manipulation và more

Automatic plan correction feature for no-admin performance tuning pulled down from Azure SQL

New native graph database capabilities with SQL Graph

SQL 2019 (15.0)

Due out in 2019 (Summer?)

Create a live alternative to ETL for heterogenous data systems with Polybase external tables, to lớn natively query data in Cosmos, SAP HANA, Teradata, Apache Spark, Mongo DB, Oracle, HDFS, DB2, or any ODBC connection.

Xem thêm: 100¥ Bằng Bao Nhiêu Tiền Việt Nam? 100 Đô La Mỹ Đổi Được Bao Nhiêu Tiền Việt Hôm Nay

SQL hệ thống in Docker or Kubernetes, including Availability Groups across containers

Always Encrypted enhanced with addition of secure enclaves to restrict data in SQL vps to application use only for regulated data environments

SQL Configuration Manager has been enhanced with a new certificate management feature

A lot more…

Much more info coming in Microsoft Press publication SQL hệ thống 2019 Administration Inside Out, due in 2019

What Is the Next Step?’s SQL DBA team has extensive experience with upgrades and migrations, & a detailed template checklist runbook for planning, prep, execution, và testing. We’d be happy to nói qua and reviews your upgrade/migration plan, or help you develop your upgrade/migration plan from scratch. Reach out to us for a quick planning meeting, a nhận xét of our migration planning documentation, and an explainer on any new features.

Information & material in our blog posts are provided "as is" with no warranties either expressed or implied. Each post is an individual expression of our Sparkies. Should you identify any such content that is harmful, malicious, sensitive or unnecessary, please contactmarketing