By Joe Terrell
Recently, most of my blog entries have been about SQL Server migrations. With extended support for Microsoft SQL Server 2005 having ended in April, it’s a timely discussion. In this blog, I’d like to share with you how we’ve applied the “lessons learned” during engagements over the last several years to a set of key migration best practices.
It all starts with understanding where you are. Discovery is the key to success. You need identify your full inventory of all servers running SQL Server. This would include deployment architectures, version levels, associated availability requirements, as well as specific performance-level characteristics.
Next you’ll have to identify the interdependencies. Those include more than just databases. There are a lot of additional dependencies such as SQL security users/logins, agent jobs, linked servers, and other configurations that have to be accounted for. You’ll have to take legacy and third-party applications into consideration as well, and understand how your new environment will support those services.