SQL Server Performance

  • Home
  • Articles
  • Forums
  • Tips
  • Training
  • FAQ's
  • Blogs
  • Software
  • Books
  • About Us
RSS Feeds
Sign in | Join


FAQ Topics

All FAQ's
General DBA
General Developer
DBA Performance Tuning
Developer Performance Tuning
Clustering
Error Messages

USEFUL SITES :

ASP.NET Tutorials
Windows and SQL Azure Tutorials
Cloud Hosting Magazine
SharePoint Tutorials
Windows Server Help

Write for Us

Share your SQL Server knowledge with others and raise your profile in the community More...
Latest Articles

A High Level Comparison Between Oracle and SQL Server - Part ...
A High Level Comparison Between Oracle and SQL Server - Part ...
A High Level Comparison Between Oracle and SQL Server - Part ...
A High Level Comparison Between Oracle and SQL Server

More     
 
Latest FAQ's

Add Node to A SQL Server failover Cluster failed with invalid ...
SQL Server Destination remote server error
Setting Up Data And Log Files For SQL Server
Will Check Constraints Improve Database Performance?

More     
   
Latest Software Reviews

dbForge Review
Spotlight on ApexSQL Diff - Server-based database comparison tool ...
Spotlight on ApexSQL Data Diff - Server-based database comparison tool ...
Spotlight on ApexSQL Doc 2008

More     

What is the best way to test the upgrade process from SQL Server 7.0 or 2000 to SQL Server 2005, before I perform the actual upgrade?



As you indicate in your question, it is very important that you test the upgrade process before you upgrade your production server. Here's what I recommend.

  1. Restore a backup of each of your production databases onto another (test) server, including the system databases running the same version of SQL Server as your production box. In other words, you essentially need to duplicate your current production system on a test server.
  2. Run Upgrade Advisor on the test box and see what your results are. In some cases you may have to modify your application for it to work properly with SQL Server 2005, although this is not common.
  3. Assuming that the Upgrade Advisor results are positive, then perform an in-place upgrade on the test box. Once the box has been upgraded to SQL Server 2005, then you will want to test each of the applications that use the databases on this server to ensure they work correctly.
  4. Once you are sure that all your old applications work fine, then you are ready to upgrade your production box.

Note: The above example assumes that you are performing an in-place upgrade, but this is not your only option. You can also create a new test box that has SQL Server 2005 on it, and then detach the user databases from the production server (during a down time), copy them to the test server, and then reattach them. This will automatically upgrade the older databases to SQL Server 2005. At this point, you will of course want to test your applications to see if they work properly before you do this for your production server. In addition, you will need to run the Upgrade Advisor on the production box, as there may be no test box to run it on. Running Upgrade Advisor on a production SQL Server will not cause any problems.

To download the Upgrade Advisor as a separate component (it also comes on the SQL Server 2005 install DVD), visit:

http://www.microsoft.com/downloads/details.aspx?familyid=1470E86B-7E05-4322-A677-95AB44F12D75&displaylang=en

Additional information from Microsoft on peforming upgrades is available at:

http://www.microsoft.com/sql/solutions/upgrade/default.mspx

and

http://www.microsoft.com/technet/prodtechnol/sql/2005/sqlupgrd.mspx

Also, don't forget, Books Online has a very good section on how to upgrade to SQL Server 2005. 








C# Help and Tutorials | PHP MySQL Tutorial | Sharepoint Tutorial | Azure Tutorial | Cloud Hosting Magazine | ASP.NET Tutorials | Windows Server Help | Windows Phone Pro | Silverlight Ace | Visual Studio Tutorials | Home | Peformance Articles | Audit Articles | Business Intelligence Articles | Clustering Articles | Developer Articles | Reporting Services Articles | DBA Articles | ASP.NET / ADO.NET Articles | SQL Server Training Videos | DBA FAQ's | Developer Peformance FAQ's | DBA Peformance FAQ's | Developer FAQ's | Clustering FAQ's | Error Messages | Audit Tool Reviews | Backup Tool Reviews | Coding Tool Reviews | Compare Tool Reviews | Documentation Tool Reviews | Design Tool Reviews | Monitoring Tool Reviews | Log Tool Reviews | Reporting Tool Reviews | Clustering Tool Reviews | Security Tool Reviews | Change Management Tool Reviews | Remote Access Tool Reviews | Book Reviews | Security Tool Reviews | ADO.NET / ASP.NET | Administration | Analysis/OLAP Services | Application Development | Configuration | Components | ETL | Hardware | High Availability | Hints | Index | Misc | Operating Systems | Performance Tuning | Replication | T-SQL | Views


              © 2010 Jude O'Kelly. All rights reserved