SQL Server 2008 End Of Support

SQL Server 2008 and SQL Server 2008 R2 will cease to be supported by Microsoft on 7th September 2019. This is an ideal business opportunity to migrate existing database architectures to the more robust SQL Server 2012 platform and above.

It also makes business and legal sense to migrate to a supported Microsoft Platform so that businesses can leverage the increased security and stability of storing customer and business data. This is essential to confirm to new European wide statues regarding GDPR.

Withdrawal Of Support

Microsoft has provided the following schedule to indicate phased withdrawal of support for SQL Server 2008. Refer to this for scheduled migration.

Products Released

Lifecycle Start Date

Mainstream Support End Date

Extended Support End Date

Service Pack Support
  End Date

SQL Server 2008

11/6/2008

7/8/2014

7/9/2019

4/13/2010

SQL Server 2008 Service Pack 1

3/31/2009

Not Applicable

Not Applicable

10/11/2011

SQL Server 2008 Service Pack 2

9/24/2010

Not Applicable

Not Applicable

10/9/2012

SQL Server 2008 Service Pack 3

10/6/2011

Review Note

Review Note

 

SQL Server 2008 R2

7/20/2010

7/8/2014

7/9/2019

7/10/2012

SQL Server 2008 R2 Service Pack 1

7/12/2011

Not Applicable

Not Applicable

10/8/2013

SQL Server 2008 R2 Service Pack 2

7/26/2012

Review Note

Review Note

 

What Version Of SQL Server Am I Running

There are two very quick ways to identity which version of SQL Server you are running:

Use SQL Health Monitor

SQL Health Monitor provides the full version information on the Sever->System screen as shown below:

(You can always click the CHECK SQL Version button which will interrogate the server for all particulars of its current version)

Showing the SQL Server version

Use SSMS (SQL Server Management Studio)

If you start a new query:

And enter the following into the editor:

SELECT @@VERSION

This will bring the relevant version information to the Results Grid.

If the version of SQL Server is 2008 or 2008R2 then you will need to migrate.

Orpheus Enterprises can assist in the migration of your legacy database systems. If you require information or support: Contact Orpheus Enterprises

PowerShell Integration

SQL Health Monitor has integrated Microsoft PowerShell to facilitate PS Script Execution. This is for those users who require the Database Processes to be automated within a DevOps Environment – without the need for a dedicated hands-on Database Administrator.

PowerShell is very Unixlike so if you have exposure to either $Bash or PERL Scripting, PowerShell can be a useful tool to leverage existing SQL Skills.

The first requirement is to Register PowerShell within SQL Health Monitor

Go to the Settings -> Program Locations Section
Add the PATH to the PowerShell Executable

Second, generate a PS1 (PowrShell) Script – or use one of the pre-built Templates specially targeting SQL Server.

Templates Section, Filtered for PowerShell, showing PowerShell script library

Thirdly, add the required Parameters to the script and click on the Execute Button.

Adding Parameters to the PowerShell Script. Execute by clicking on the Exclamation Button

This will bring up the PowerShell window so you can view the process.

PowerShell Executing the Script. In this case, backing up a database

PowerShell integration allows the control of PS1 Scripts and Tasks within SQL Health Monitor to facilitate quick results in Server and Database Performance.

It is a valuable tool in controlling your PowerShell scripts and leveraging existing SQL Skills.