Bye bye SQL Server 2005, now is the time for you to #upgrade


From today SQL Server 2005 will no longer have any support from the Microsoft, which means no security updates or hotfixes that might affect your production platform if you are still managing 2005 version instances.

Microsoft and partners (along with MVPs) have been discussing about end of support for SQL Server 2005, and sharing information about how to upgrade. So now is the time to put all your efforts in one place to plan for action on SQL Server 2005 upgrade.

Upgrade to latest version of SQL Server (2014 and 2016 – soon to be) doesn’t guarantee you better performance or scalability, it is the database that was designed and also failing to prepare, plan and deploy a proper process will result to a disastrous performance loss on your data platform. So your vision must reside on upgrade – prepare, checkpoint and post-upgrade tasks to sustain performance and scalability.

So going into technical details we have tons of information in the Books OnLine and other blogs about SQL Server 2014 support for SQL Server 2005, see below:

  • Upgrade a SQL Server 2005 instance of database engine to SQL Server 2014 by running SQL Server 2014 setup using the installation wizard or from the command prompt.
  • Attach a SQL Server 2005 database (mdf/ldf files) to SQL Server 2014 instance of database engine.
  • Restore a SQL Server 2005 database to SQL Server 2014 instance of database engine from a backup.
  • Upgrade a SQL Server 2005 Integration Services (SSIS) package to SQL Server 2014. Execute packages with automatic-in-place upgrade.
  • Upgrade a SQL Server 2005 Analysis Services (SSAS) to SQL Server 2014 by running SQL Server 2014 setup.
  • Back up a SQL Server 2005 Analysis Services (SSAS) cube and restoring on SQL Server 2014.
  • Upgrade SQL Server 2005 Reporting Services (SSRS) to SQL Server 2014 by running SQL Server 2014 setup.
  • Connect to SQL Server 2005by using SQL Server Profiler 2014.

When a SQL Server 2005 database is upgraded to SQL Server 2014, the database compatibility level will be changed from 90 to 100. (In SQL Server 2014, valid values for the database compatibility level are 100, 110 and 120.) ALTER DATABASE Compatibility Level (Transact-SQL)discusses how the compatibility level change could affect SQL Server applications.

Any scenarios not specified in the list above are not supported, including but not limited to the following:

  • Installing SQL Server 2005 and SQL Server 2014 on same computer (side by side).
  • Using a SQL Server 2005 instance as a member of the replication topology that involves a SQL Server 2014 instance.
  • Configuring database mirroring between SQL Server 2014 and SQL Server 2005 instances.
  • Backing up the transaction log with log shipping between SQL Server 2014 and SQL Server 2005 instances.
  • Configuring linked servers between SQL Server 2014 and SQL Server 2005 instances.
  • Managing a SQL Server 2005 instance from a SQL Server 2014 Management Studio.
  • Attaching a SQL Server 2005 Analysis Services (SSAS) cube in SQL Server 2014 Management Studio.
  • Connecting to SQL Server 2005 Integration Services (SSIS) from SQL Server 2014 Management Studio.
  • Managing a SQL Server 2005 Integration Services (SSIS) service from SQL Server 2014 Management Studio.
  • Support for SQL Server 2005 third party custom Integration Services components, such as execute and upgrade.

….and highly recommended pages:

Features Supported by the Editions of SQL Server 2014
Hardware and Software Requirements for Installing SQL Server 2014
Upgrade to SQL Server 2014
Use Upgrade Advisor to Prepare for Upgrades

 

Also data platform upgrade topic is one of the popular topic that I have been presenting since the year 2008 in majority of SQL Server conferences.