1 / 11

Upgrading Best Practices

Upgrading software is essential for maintaining security, performance, and reliability. This guide covers best practices for various types of upgrades, including hotfixes, security fixes, service packs, and new releases. Before installation, it’s crucial to test, plan, and create a baseline of the current environment. Perform backups, verify compatibility, and consider rollback plans. During the installation, monitor logs and check basic functionality. After the upgrade, further monitor the system and perform a backup to ensure everything operates smoothly.

odette
Télécharger la présentation

Upgrading Best Practices

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Upgrading Best Practices

  2. Type of upgrade • Hotfix • Security fix • Service pack • New release

  3. Why upgrading? • Hotfix • Fix a specific bug • Security fix • Fix a security issue • Service pack • Increase reliability, increase performance • New release • Get new features, increased reliability, increased performance

  4. Before installation • Test • Plan • Create a baseline • Verify the current environment • Backup

  5. Before installation (cont.) • Test • Test your application • Check that the upgrade does what it should • Test the installation procedure • Test the performance implications Best Practice Analyzer can help checking application compatibility Ostress can be used to test performance

  6. Before the installation (cont.) • Plan • Plan the installation procedure • Plan how to rollback the installation • Plan the time to do the upgrade • Decide the success criteria • Decide the when the last chance to rollback

  7. Before the installation (cont.) • Create a baseline • Performance monitor • Profiler trace • Blocking trace • Application trace PSSDiag can be used to automate Read80Trace can be used to analyze profiler Relog can be used to analyze performance monitor

  8. Before the installation (cont.) • Verify the current environment • DBCC • Error log • Event log • Reboot the server

  9. Before the installation (cont.) • Backup the server • Backup the database • Perform the backup • Verify the restore • Verify the time needed to restore

  10. During the installation • Turn off unnecessary services • Upgrade the server • Check the installation logs • Reboot the server • Check the version • Check basic functionality

  11. After the installation • Perform a backup • Monitor the system

More Related