Microsoft SQL Server 2005 Reaches end-of-life. How to Migrate

microsoft sql serverExtended support for Microsoft SQL Server 2005 came to an end on 12 April 2016, after 10 years of excellent service. This is bad news for businesses still reliant on this version. In short, Microsoft SQL Server 2005 reached its end-of-life. From now on, no more hotfixes or security updates will be released by Microsoft. If your organisation still runs SQL Server 2005, it is being exposed to a potential security breach (IBM, 2016). According to the IBM report, the average cost of a data breach grew from $3.8 million in 2015 to $4 million in 2016.

Introduction

Organisations that are planning an on-premise upgrade of Microsoft SQL Server 2005 64-bit can perform an in-place upgrade to SQL Server 2014. In the case of the 32-bit edition, a side-by-side upgrade must be attempted. The exact size of the remaining SQL Server 2005 deployment in the enterprise is not clear, but the steady stream of questions fielded by Stack Overflow tagged “sql-server-2005” clearly indicates that the user-base is relatively large.

Microsoft SQL Server Migration Using Double-Take SQLMove

Vision Solutions offer an alternative upgrade path for SQL Server 2005. Their Double-Take Move product assists administrators to upgrade SQL Server 2005 to 2014 edition. The Double-Take Move video explains how the process works.

https://www.youtube.com/watch?v=k9Oy6bLyyk0

How Double-Take SQLMove Works

Double-Take SQLMove practically eliminates Server downtime. The steps to complete an SQL Server move are listed below.

Step 1
Install the Double-Take Move agent onto the source SQL Server 2005 server and the target SQL Server 2014 server.

Step 2
The next step is to create a migration job and select the SQL Server 2005 database that you want to migrate plus the target storage location, on the SQL Server 2014 server.

Step 3
Start the SQLMove replication job (created in Step 2) and the software will migrate your data from the live SQL Server 2005 instance to the Microsoft SQL 2014 instance, in real-time and during regular business hours. All this is done without any downtime on the SQL 2005 instance.

Step 4
When the initial synchronisation between SQL Server 2005 and SQL 2014 is complete, you can switch the SQL 2014 over to production and the SQL Server 2005 instance can be taken off-line.

Conclusion

Migrating an SQL Server instance has always been a challenge for the IT staff because traditionally migration involves risks and takes a long time to complete. During the migration, user productivity suffers because no data changes are permitted. Also, the entire process can take hours if not days. Vision Solutions changed all this with the introduction of Double-Take SQLMove.

If you want to learn more about Double-Take SQLMove, please fill in your details in the form below and one of our representatives will contact you to discuss your business requirements.

References

IBM, 2016. Available: Ponemon Cost of Data Breach Study [2016, June 22] http://www-03.ibm.com/security/data-breach/

Stack Overflow, 2016. Available: SQL-Server -2005 [2016, June 22] http://stackoverflow.com/search?q=sql-server-2005

Recent Posts
Contact Us

We're not around right now. But you can send us an email and we'll get back to you, asap.

Not readable? Change text. captcha txt

Start typing and press Enter to search