Installing SQL Server 2005 in VS .NET

Printer PDF-417 2d barcode in VS .NET Installing SQL Server 2005

1

17. Repeat the previous step for the transaction log file, specifying .ldf as the extension for all log files. 18. Click OK to restore the backup. When the process is complete, click OK to close the displayed message box.

When upgrading a SQL Server installation to SQL Server 2005, you have the option of performing an in-place upgrade or a side-by-side upgrade. An in-place upgrade requires the installation of SQL Server 2005 on top of a current installation, replacing the old SQL Server files. A side-by-side upgrade involves installing SQL Server 2005 as a new instance either on the same server as the old instance or on a different server. The databases are then moved to the new SQL Server 2005 instance. Always make a backup copy of your databases before attempting an upgrade. In a side-by-side upgrade, DBAs have multiple ways to move databases from an old SQL Server instance to a SQL Server 2005 instance: detach/attach, backup/ restore, the Copy Database Wizard, and manual. Before upgrading your SQL Server installations, create a testing plan to validate the successful upgrade of your installation. Before upgrading your SQL Server installations, you should create an upgrade rollback plan in case you need to recover from an unsuccessful upgrade.

The following questions are intended to reinforce key information presented in this lesson. The questions are also available on the companion CD if you prefer to review them in electronic form.

Answers to these questions and explanations of why each answer choice is right or wrong are located in the Answers section at the end of the book.

1. The term in-place upgrade refers to which type of upgrade A. Installing SQL Server 2005 in the same directory as the current installation and replacing the SQL Server files B. Installing a new instance of SQL Server 2005 and sharing the older databases between the new instance and the old instance C. Installing a new instance of SQL Server 2005 on the same server as the old instance and moving the databases from the old instance to the new instance D. Installing a new instance of SQL Server 2005 on a different server from the old instance and moving the databases from the old server to the new server

2. Which upgrade data-movement method requires that users not be accessing the database you want to upgrade A. Copy Database Wizard B. Detach/attach C. Backup/restore D. Manual scripting 3. Which of the following is not recommended when performing a SQL Server upgrade A. Create a series of checklists to ensure that all processes needed before, during, and after an upgrade have been completed. B. Reserve enough disk space for the extra copies of database files needed for the upgrade. C. Disable all startup stored procedures to prevent the stored procedures from firing multiple times during the upgrade. D. Configure system databases not to autogrow to prevent system databases from filling your disks during the upgrade process.

Review the chapter summary. Review the list of key terms introduced in this chapter. Complete the case scenarios. These scenarios set up a real-world situation involving the topics of this chapter and ask you to create solutions. Complete the suggested practices. Take a practice test.

Summary

SQL Server 2005 includes five editions, with each edition having different functionality and feature sets and different infrastructure requirements. Understanding the editions and their hardware, OS, and network requirements is key to selecting the correct edition for your needs. You can install a default, unnamed instance of SQL Server 2005 and multiple additional named instances on the same server. Multiple instances can be beneficial for testing purposes and for separating different customers databases. SQL Server 2005 requires at least one account for use by the SQL Server service and the SQL Server Agent service. To make sure that the SQL Server service doesn t have more privileges than necessary, you often need to use a separate account for each service. When upgrading a SQL Server installation to SQL Server 2005, you can perform either an in-place upgrade or a side-by-side migration. A side-by-side migration, which allows for the continuous operation of the original database environment while the upgraded environment is being installed and tested, can often minimize downtime for the SQL Server environment. You can use detach/attach, backup/restore, the Copy Database Wizard, or manual scripting to move database files in a side-by-side migration. Whichever method you choose, you should make a copy of your original files in case you need to recover your original environment because of an upgrade problem.