Many organizations are still in the process of upgrading from SQL Server 2000 to 2005. When looking at going to SQL Server 2008, you may have a decision to make - upgrade directly from SQL 2000 to SQL 2008 - or - upgrade to SQL 2005 first, and then to 2008. In this session, we’ll look at factors such as incompatibility issues (e.g. deprecated functionality, security models, etc.), choosing the appropriate upgrade mechanism, and rollback planning. These can help you chose the best upgrade path for your organization. Like so many other things in life, timing is everything. A little strategic evaluation and planning on your part could result in a 2-for-1 upgrade process - saving you both time and money. It could also result in you saving your company from a costly situation in attempting to upgrade to a version your environment for which it is not ready. Most of the evaluations and processes would also apply to a SQL 2005 to SQL 2008 migration.
Ronald Yenko
Ronald Yenko is a Database Architect at iSECUREtrac in Omaha, NE. For the past 15 years he has been involved with various Microsoft technologies including providing enterprise database architecture solutions using Microsoft SQL Server (from 6.5 through 2005) in the retail, law enforcement, government and financial industries. In recent years, he has specialized in enterprise architecture and focused on business continuity/disaster recovery and performance tuning.