SQL Server 2005 was installed onto server DMRTK-SRVR-A2, which was running Windows 2003 Server R2 Enterprise x64 Edition. The following steps were completed on the server before installing SQL Server 2005:
-
All updates applied to Windows 2003 Server R2 Enterprise x64 Edition
-
Microsoft .NET Framework 2.0 installed on server
-
iSCSI targets logged on as volumes “Q” and “R”
SQL Server 2005 Deployment
SQL Server 2005 provides a wizard to perform the installation. Most of the defaults were selected. First the wizard checked for SQL Server prerequisites.
After the SQL Server prerequisites were completed, the main installation began.
All the SQL Server components were installed. Most of the other defaults were chosen.
The installation completed successfully. After the installation, the system was rebooted. SQL Server 2005 Service Pack 2 was installed after the reboot.
The sample AdventureWorks databases were installed into the default SQL Server file location. The Copy Database Wizard was used from within SQL Server Management Studio to copy the AdventureWorks database and AdventureWorksDW (data warehouse) to the iSCSI target volumes “Q” and “R”. Volume “Q” was used for the data and volume “R” was used for the SQL logs. The source and destination server were the same, but the destination file location was set to the iSCSI target volumes.
The wizard prompts for the file locations. The source files were in the default location from installation. The destination files were the iSCSI target volumes. Two databases, the AdventureWorks and AdventureWorksDW were copied. The data files were copied to the “Q” volume and the logs were copied to the “R” volume.
The Integration Services package was configured and run immediately with the SQL Server Agent service account.
The copy was completed successfully to the iSCSI target volumes using SQL Server services.
| 