So, you've decided to upgrade your databases from SQL Server 2000 to SQL 2005. A lot has been said as to why upgrade: gaining scalability, reliability, up to 30% performance improvements and much more.
You have your desktop or your testing environment with an already installed instance of SQL Server 2000 and you want to try the in-place upgrade or maybe you just want to install a new instance of SQL Server 2005. This article highlights issues that may arise when installing the new instance and also analyzes options for interaction between the two versions, such as: linked servers, multi-server administration and log shipping.
ABOUT THE AUTHOR
Michelle Gutzait works as a senior database consultant for ITERGY International Inc., an IT consulting firm specializing in the design, implementation, security and support of Microsoft products in the enterprise. Gutzait has been involved in IT for 20 years as a developer, business analyst and database consultant. For the last 10 years, she has worked exclusively with SQL Server. Her skills include SQL Server infrastructure design, database design, performance tuning, security, high availability, VLDBs, replication, T-SQL/packages coding, and more.
Copyright 2007 TechTarget