How To Use A Microsoft Microsoft Database Server 2012

Transcription

1 OFFICIAL MICROSOFT LEARNING PRODUCT 10775A Lab Instructions and Lab Answer Key: Administering Microsoft SQL Server 2012 Database

2 Information in this document, including URL and other Internet Web site references, is subject to change without notice. Unless otherwise noted, the example companies, organizations, products, domain names, addresses, logos, people, places, and events depicted herein are fictitious, and no association with any real company, organization, product, domain name, address, logo, person, place or event is intended or should be inferred. Complying with all applicable copyright laws is the responsibility of the user. Without limiting the rights under copyright, no part of this document may be reproduced, stored in or introduced into a retrieval system, or transmitted in any form or by any means (electronic, mechanical, photocopying, recording, or otherwise), or for any purpose, without the express written permission of Microsoft Corporation. Microsoft may have patents, patent applications, trademarks, copyrights, or other intellectual property rights covering subject matter in this document. Except as expressly provided in any written license agreement from Microsoft, the furnishing of this document does not give you any license to these patents, trademarks, copyrights, or other intellectual property. The names of manufacturers, products, or URLs are provided for informational purposes only and Microsoft makes no representations and warranties, either expressed, implied, or statutory, regarding these manufacturers or the use of the products with any Microsoft technologies. The inclusion of a manufacturer or product does not imply endorsement of Microsoft of the manufacturer or product. Links may be provided to third party sites. Such sites are not under the control of Microsoft and Microsoft is not responsible for the contents of any linked site or any link contained in a linked site, or any changes or updates to such sites. Microsoft is not responsible for webcasting or any other form of transmission received from any linked site. Microsoft is providing these links to you only as a convenience, and the inclusion of any link does not imply endorsement of Microsoft of the site or the products contained therein Microsoft Corporation. All rights reserved. Microsoft and the trademarks listed at /Trademarks/EN-US.aspx are trademarks of the Microsoft group of companies. All other trademarks are property of their respective owners Product Number: 10775A Part Number: X Released: 05/2012

3 Lab Instructions: Introduction to SQL Server 2012 and Its Toolset 1 Module 1 Lab Instructions: Introduction to SQL Server 2012 and Its Toolset Contents: Exercise 1: Verify SQL Server Component Installation 2 Exercise 2: Alter Service Accounts for New Instance 3 Exercise 3: Enable Named Pipes Protocol for Both Instances 4 Exercise 4: Create an Alias for AdvDev 4 Challenge Exercise 5: Ensure SQL Browser Is Disabled and Configure a Fixed TCP/IP Port (Only if time permits) 5

4 2 Lab Instructions: Introduction to SQL Server 2012 and Its Toolset Lab 1: Introduction to SQL Server and Its Toolset Lab Setup For this lab, you will use the available virtual machine environment. Before you begin the lab, you must complete the following steps: Revert the virtual machines as per the instructions in D:\10775A_Labs\Revert.txt. Lab Scenario AdventureWorks is a global manufacturer, wholesaler and retailer of cycle products. The owners of the company have decided to start a new direct marketing arm of the company. It has been created as a new company named Proseware, Inc. Even though it has been set up as a separate company, it will receive some IT-related services from the existing AdventureWorks company and will be provided with a subset of the corporate AdventureWorks data. The existing AdventureWorks company SQL Server platform has been moved to a new server that is capable of supporting both the existing workload and the workload from the new company. In this lab, you are ensuring that the additional instance of SQL Server has been configured appropriately and making a number of additional required configuration changes. Exercise 1: Verify SQL Server Component Installation A new instance of SQL Server has been installed by the IT department at AdventureWorks. It will be used by the new direct marketing company. The SQL Server named instance is called MKTG. In the first exercise, you need to verify that the required SQL Server components have been installed.

5 Lab Instructions: Introduction to SQL Server 2012 and Its Toolset 3 The main tasks for this exercise are as follows: 1. Check that Database Engine and Reporting Services have been installed for the MKTG instance. 2. Note the services that are installed for the default instance. 3. Ensure that all required services including SQL Server Agent are started and set to autostart for both instances. Task 1: Check that Database Engine and Reporting Services have been installed for the MKTG instance Open SQL Server Configuration Manager. Check the installed list of services for the MKTG instance and ensure that the database engine and Reporting Services have been installed for the MKTG instance. Task 2: Note the services that are installed for the default instance Note the list of services that are installed for the default instance. Task 3: Ensure that all required services including SQL Server Agent are started and set to autostart for both instances Ensure that all the MKTG services are started and set to autostart. (Ignore the Full Text Filter Daemon at this time). Ensure that all the services for the default instance are set to autostart. (Ignore the Full Text Filter Daemon at this time). Results: After this exercise, you have checked that the required SQL Server services are installed, started, and configured to autostart. Exercise 2: Alter Service Accounts for New Instance Scenario The SQL Server services for the MKTG instance have been configured to execute under the AdventureWorks\SQLService service account. In this exercise, you will configure the services to execute under the AdventureWorks\PWService service account. The main tasks for this exercise are as follows: 1. Change the service account for the MKTG database engine. 2. Change the service account for the MKTG SQL Server Agent. Task 1: Change the service account for the MKTG database engine Change the service account for the MKTG database engine service to AdventureWorks\PWService using the properties page for the service. Task 2: Change the service account for the MKTG SQL Server Agent Change the service account for the MKTG SQL Server Agent service to AdventureWorks\PWService using the properties page for the service and then restart the service. Results: After this exercise, you have configured the service accounts for the MKTG instance.

6 4 Lab Instructions: Introduction to SQL Server 2012 and Its Toolset Exercise 3: Enable Named Pipes Protocol for Both Instances Scenario Client applications that are installed on the server will connect to the database engine using the named pipes protocol. In this exercise, you will ensure that the named pipes protocol is enabled for both database engine instances. The main tasks for this exercise are as follows: 1. Enable the named pipes protocol for the default instance. 2. Enable the named pipes protocol for the MKTG instance. 3. Restart database engine services for both instances. Task 1: Enable the named pipes protocol for the default instance If necessary, enable the named pipes protocol for the default database engine instance using the Protocols window. Task 2: Enable the named pipes protocol for the MKTG instance If necessary, enable the named pipes protocol for the MKTG database engine instance using the Protocols window. Task 3: Restart both database engine services If necessary, restart the default database engine instance. If necessary, restart the MKTG database engine instance. Check to ensure that both instances have been restarted successfully. Results: After this exercise, you should have ensured that the named pipes protocol is enabled for both database engine instances. Exercise 4: Create an Alias for AdvDev Scenario One badly-written monitoring application has been installed on the server. Unfortunately, it requires a hard-coded server name of AdvDev. In this exercise, you will configure and test an alias for AdvDev that points to the MKTG server. Use the Named Pipes protocol. Both 32 bit and 64 bit aliases should be configured. You will use SQL Server Management Studio to test the alias once it has been configured. The main tasks for this exercise are as follows: 1. Create a 32-bit alias (AdvDev) for the MKTG instance. 2. Create a 64-bit alias (AdvDev) for the MKTG instance. 3. Use SQL Server Management Studio to connect to the alias to ensure it works as expected. Task 1: Create a 32-bit alias (AdvDev) for the MKTG instance Create a 32-bit alias for the MKTG instance. Call the alias AdvDev and connect via named pipes. Use the servername ".\MKTG".

7 Lab Instructions: Introduction to SQL Server 2012 and Its Toolset 5 Task 2: Create a 64-bit alias (AdvDev) for the MKTG instance Create a 64-bit alias for the MKTG instance. Call the alias AdvDev and connect via named pipes. Use the servername ".\MKTG". Task 3: Use SQL Server Management Studio to connect to the alias to ensure it works as expected Open SQL Server Management Studio. Connect to the AdvDev alias. Results: After this exercise, you should have created and tested an alias for the named instance. Challenge Exercise 5: Ensure SQL Browser Is Disabled and Configure a Fixed TCP/IP Port (Only if time permits) Scenario Client applications will need to connect to the MKTG database engine instance via the TCP/IP protocol. As their connections will need to traverse a firewall, the port used for connections cannot be configured as a dynamic port. The port number must not change. Corporate policy at AdventureWorks is that named instances should be accessed via fixed TCP ports and the SQLBrowser service should be disabled. In this exercise, you will make configuration changes to comply with these requirements. A firewall exception has already been created for port 51550, for use with the MKTG database engine instance. The main tasks for this exercise are as follows: 1. Configure the TCP port for the MKTG database engine instance to Disable the SQLBrowser service. Task 1: Configure the TCP port for the MKTG database engine instance to Using the property page for the TCP/IP server protocol, configure the use of the fixed port (Make sure that you clear the dynamic port.) Restart the MKTG database engine instance. Ensure that the MKTG database engine instance has been restarted successfully. Task 2: Disable the SQLBrowser service Stop the SQLBrowser service. Set the Start Mode for the SQL Browser service to Disabled. Results: After this exercise, you will have configured a fixed TCP port for the MKTG database engine instance and disabled the SQLBrowser service.

8 Lab Instructions: Preparing Systems for SQL Server Module 2 Lab Instructions: Preparing Systems for SQL Server 2012 Contents: Exercise 1: Adjust Memory Configuration 3 Exercise 2: Pre-installation Stress Testing 4 Challenge Exercise 3: Check Specific I/O Operations (Only if time permits) 5

9 2 Lab Instructions: Preparing Systems for SQL Server 2012 Lab 2: Preparing Systems for SQL Server Lab Setup For this lab, you will use the available virtual machine environment. Before you begin the lab, you must complete the following steps: 1. Revert the virtual machines as per the instructions in D:\10775A_Labs\Revert.txt. 2. In the virtual machine, click Start, click All Programs, click Microsoft SQL Server 2012, and click SQL Server Management Studio. 3. In Connect to Server window, type Proseware in the Server name text box. 4. In the Authentication drop-down list box, select Windows Authentication and click Connect. 5. In the File menu, click Open, and click Project/Solution. 6. In the Open Project window, open the project D:\10775A_Labs\10775A_02_PRJ\10775A_02_PRJ.ssmssln. 7. From the View menu, click Solution Explorer. In Solution Explorer, double-click the query 00-Setup.sql. When the query window opens, click Execute on the toolbar. Lab Scenario You have reviewed the additional instance of SQL Server. A system administrator at AdventureWorks has expressed some concerns that the existing server may not have enough memory or I/O capacity to support this new SQL Server instance and is reviewing a new I/O subsystem. As the database administrator, you need to review the available server memory and the memory allocated to each of the existing SQL Server instances. You need to ensure that the I/O subsystem of the new server is capable of running SQL Server and the required workload correctly.

10 Lab Instructions: Preparing Systems for SQL Server Supporting Documentation Required Memory Configuration 1.5GB reserved for operating system. 60% of the remaining memory as the maximum value for the AdventureWorks server instance. 40% of the remaining memory as the maximum value for the Proseware server instance. Configure minimum memory as zero for both instances. Required SQLIOSIM Configuration Drive D with a 100MB data file that grows by 20MB increments to a 200MB maximum size. Drive L with a 50MB log file that grows by 10MB increments to a 100MB maximum size. Cycle Duration (sec) set to 60 seconds. Delete Files at Shutdown should be selected. Required SQLIO Tests Drive to be tested is D. Test 64KB sequential reads for 60 seconds. Test 8KB random writes for 60 seconds. Exercise 1: Adjust Memory Configuration Scenario The Adventure Works Marketing server has an existing default Microsoft SQL Server 2012 instance installed and the new MKTG instance. You need to check the total memory available on the server and how much memory has been allocated to each of the two existing SQL Server instances. You should then decide if the memory allocation is appropriate. If not, make the required changes to the memory configuration. The main tasks for this exercise are as follows: 1. Check total server memory. 2. Check the memory allocated to the default instance. 3. Check the memory allocated to the MKTG instance. 4. Decide if the memory allocation is appropriate. If not, make the required changes to the memory configuration. Task 1: Check total server memory Retrieve the installed memory (RAM) value from the properties of the computer. Task 2: Check the memory allocated to the default instance Using the properties of the AdventureWorks server instance in SSMS, retrieve the minimum and maximum server memory settings.

11 4 Lab Instructions: Preparing Systems for SQL Server 2012 Task 3: Check the memory allocated to the MKTG instance Using the properties of the Proseware server instance in SSMS, retrieve the minimum and maximum server memory settings. Task 4: Decide if the memory allocation is appropriate. If not, make the required changes to the memory configuration Review the Required Memory Configuration from the Supporting Documentation. Alter the Memory Configuration for both SQL Server instances as per the requirements. You will need to work out how much memory should be used for all SQL Server instances and apportion the memory based on the requirements in the Supporting Documentation. Note While reducing the max server memory might require restarting SQL Server, there is no need to restart the servers at this point in the exercise. Results: After this exercise, you should have configured the memory for the SQL Server Instances. Exercise 2: Pre-installation Stress Testing Scenario After you have reviewed allocated memory on the server, you need to test whether the new I/O subsystem is capable of running SQL Server successfully. In this exercise, you need to use the SQLIOSIM utility for stress testing to ensure the stability of SQL Server performance. The main tasks for this exercise are as follows: 1. Configure SQLIOSIM. 2. Execute SQLIOSIM. 3. Review the results from executing SQLIOSIM. Task 1: Configure SQLIOSIM Install SQLIOSIM from the file D:\10775A_Labs\10775A_02_PRJ\sqliosimx64.exe (Make sure that you use the Run as administrator option). Configure SQLIOSIM as per requirements in the Supporting Documentation. Task 2: Execute SQLIOSIM Execute SQLIOSIM based upon the configured parameters. Task 3: Review the results from executing SQLIOSIM If any errors are returned in red, review the errors. Locate the final summary for each of the drives and note the average I/O duration in milliseconds. Results: After this exercise, you have run a stress test using SQLIOSIM.

12 Lab Instructions: Preparing Systems for SQL Server Challenge Exercise 3: Check Specific I/O Operations (Only if time permits) Scenario You have identified a specific list of I/O workloads and plan to test their performance on the new I/O subsystem. In this exercise, you need to run the SQLIO utility to verify the I/O workloads. The main tasks for this exercise are as follows: 1. Install the SQLIO Utility. 2. Configure and Execute the SQLIO Utility. Task 1: Install the SQLIO Utility Install the SQLIO Utility from the file D:\10775A_Labs\10775A_02_PRJ\SQLIO.msi (Choose to install for all users). Task 2: Configure and Execute the SQLIO Utility Review the Supporting Documentation for details of the SQLIO tests to be performed. Configure the file C:\Program Files (x86)\sqlio\param.txt as per the requirements in the Supporting Documentation. Execute the sqlio.exe program from within a command window, to test the I/O types as requested in the Supporting Documentation. For each test, record the IOPS and throughput achieved. Also note the minimum, maximum and average latency for each test. Results: After this exercise, you should have executed the SQLIO utility to test specific I/O characteristics.

13 Lab Instructions: Installing and Configuring SQL Server Module 3 Lab Instructions: Installing and Configuring SQL Server 2012 Contents: Exercise 1: Review Installation Requirements 4 Exercise 2: Install the SQL Server Instance 4 Exercise 3: Perform Post-installation Setup and Checks 5 Challenge Exercise 4: Configure Server Memory (Only if time permits) 5

14 2 Lab Instructions: Installing and Configuring SQL Server 2012 Lab 3: Installing and Configuring SQL Server Lab Setup For this lab, you will use the available virtual machine environment. Before you begin the lab, you must complete the following steps: 1. Revert the virtual machines as per the instructions in D:\10775A_Labs\Revert.txt. 2. In the virtual machine, click Start, click All Programs, click Microsoft SQL Server 2012, and click SQL Server Management Studio. 3. In the Connect to Server window, type Proseware in the Server name text box. 4. In the Authentication drop-down list box, select Windows Authentication and click Connect. 5. In the File menu, click Open, and click Project/Solution. 6. In the Open Project window, open the project D:\10775A_Labs\10775A_03_PRJ\10775A_03_PRJ.ssmssln. 7. From the View menu, click Solution Explorer. In Solution Explorer, double-click the query 00-Setup.sql. When the query window opens, click Execute on the toolbar. 8. On the host system, in the Virtual Machines list in Hyper-V Manager, right-click the 10775A-MIA-SQL1 virtual machine and click Settings. 9. In the Settings for 10775A-MIA-SQL1 window, in the Hardware list expand IDE Controller 1, and click DVD Drive. 10. In the DVD Drive properties pane, click Image file, and click browse.

15 Lab Instructions: Installing and Configuring SQL Server Navigate to the file C:\Program Files\Microsoft Learning\10775\Drives\10775A-MIA-SQL1 \Virtual Hard Disks\SQLFULL_ENU.iso and click Open. 12. In the Settings for 10775A-MIA-SQL1 window, click OK. Lab Scenario The development group within the company has ordered a new server for the work they need to do on the Proseware system. Unfortunately, the new server will not arrive for a few weeks and the development group cannot wait that long to start work. The new server that was provisioned by the IT Support department already has two instances of SQL Server installed. The support team has determined that the new server will be able to support an additional instance of SQL Server on a temporary basis, until the server for the development group arrives. You need to install the new instance of SQL Server and if you have time, you should configure the memory of all three instances to balance their memory demands, and you should create a new alias for the instance that you install. Supporting Documentation Required SQL Server Instance Configuration Item Configuration Instance Name Features Data File Folder Log File Folder Service Accounts Startup Server Collation MKTGDEV Database Engine only (excluding Full Text and Replication) D:\MKTGDEV for user databases and tempdb L:\MKTGDEV for user databases and tempdb AdventureWorks\PWService for all services Both SQL Server and SQL Server Agent should start automatically SQL_Latin1_General_CP1_CI_AS Authentication Mode Mixed Administrative User Filestream Support AdventureWorks\Administrator Disabled Note that Pa$$w0rd is used for all passwords in the course.

16 4 Lab Instructions: Installing and Configuring SQL Server 2012 Required Memory Configuration (Used in Exercise 4 only) 1.0GB reserved for operating system. 40% of the remaining memory as the maximum value for the AdventureWorks server instance. 30% of the remaining memory as the maximum value for the Proseware server instance. 30% of the remaining memory as the maximum value for the PWDev server instance. Configure minimum memory as zero for all instances. Exercise 1: Review Installation Requirements Scenario You will review the supporting documentation that describes the required configuration for the new instance. You will also create the required folders to hold the data and log files for the instance. The main tasks for this exercise are as follows: 1. Review the supporting documentation prior to installation. 2. Create the folders that are required for the data and log files. Task 1: Review the supporting documentation prior to installation Review the supplied requirements in the supporting documentation for the exercise. Task 2: Create the folders that are required for the data and log files Based on the supplied requirements, create the folders that are required for the data and log files of the new SQL Server instance. Results: After this exercise, you should have read the requirements and created the two folders that are required. Exercise 2: Install the SQL Server Instance Scenario In this exercise, you need to perform an installation of another instance of SQL Server on the existing server based on the supplied specifications. In the setup steps for this lab, you have mounted an ISO file that contains an image of SQL Server that will be used to install the instance. Pre-requisites have already been installed as there are existing instances of SQL Server. The main task for this exercise is as follows: 1. Based on the requirements reviewed in Exercise 1, install another instance of SQL Server.

17 Lab Instructions: Installing and Configuring SQL Server Task 1: Based on the requirements reviewed in Exercise 1, install another instance of SQL Server Install another instance of SQL Server based on the requirements in Exercise 1. Note On the Server Configuration page, you should configure the service account name and password, the startup type for SQL Server Agent, and the collation. On the Database Engine Configuration page, you should configure Mixed Mode, the sa password, Add Current User, Data Directories tab, and the Filestream tab. Results: After this exercise, you should have installed another SQL Server instance. Exercise 3: Perform Post-installation Setup and Checks Scenario You need to make sure that the services for the new instance are running and you need to create a new alias for the instance you have just installed. Once the instance is created, you should connect to the instance using SQL Server Management Studio to make sure that the instance works. The main tasks for this exercise are as follows: 1. Check that the services for the new SQL Server instance are running. 2. Configure both 32 bit and 64 bit aliases for the new instance. 3. Connect to the new instance using SSMS. Task 1: Check that the services for the new SQL Server instance are running Using SQL Server Configuration Manager, make sure that the newly installed services are running. Make sure that the named pipes protocol is enabled for the new instance. Task 2: Configure both 32 bit and 64 bit aliases for the new instance Configure a 32 bit alias called PWDev for the new instance using named pipes. Configure a 64 bit alias called PWDev for the new instance using named pipes. Task 3: Connect to the new instance using SSMS Start SQL Server Management Studio and connect to the new instance to make sure it is working. Make the connection using the PWDev alias. Results: After this exercise, you should have checked that the services are running, created a new alias, and connected using SSMS. Challenge Exercise 4: Configure Server Memory (Only if time permits) Scenario There are now three SQL Server instances installed on the Marketing server at AdventureWorks. In this exercise, you need to configure the amount of memory that is allocated to each instance.

18 6 Lab Instructions: Installing and Configuring SQL Server 2012 The main tasks for this exercise are as follows: 1. Review the current memory available on the server. 2. Determine an appropriate memory allocation for each instance. 3. Configure each instance appropriately. Task 1: Review the current memory available on the server Review the current memory available on the server. Task 2: Determine an appropriate memory allocation for each instance Review the required memory proportions as specified in the supporting documentation. Determine an appropriate memory allocation for each instance. Task 3: Configure each instance appropriately Configure each instance based on the values you have calculated. Results: After this exercise, you should have modified the memory allocation for each SQL Server instance.

19 Lab Instructions: Working with Databases 1 Module 4 Lab Instructions: Working with Databases Contents: Exercise 1: Adjust tempdb Configuration 5 Exercise 2: Create the RateTracking Database 5 Exercise 3: Attach the OldProspects Database 6 Challenge Exercise 4: Add Multiple Files to tempdb (Only if time permits) 6

20 2 Lab Instructions: Working with Databases Lab 4: Working with Databases Lab Setup For this lab, you will use the available virtual machine environment. Before you begin the lab, you must complete the following steps: 1. Revert the virtual machines as per the instructions in D:\10775A_Labs\Revert.txt. 2. In the virtual machine, click Start, click All Programs, click Microsoft SQL Server 2012, and click SQL Server Management Studio. 3. In the Connect to Server window, type Proseware in the Server name text box. 4. In the Authentication drop-down list box, select Windows Authentication and click Connect. 5. In the File menu, click Open, and click Project/Solution. 6. In the Open Project window, open the project D:\10775A_Labs\10775A_04_PRJ\10775A_04_PRJ.ssmssln. 7. From the View menu, click Solution Explorer. In Solution Explorer, double-click the query 00-Setup.sql. When the query window opens, click Execute on the toolbar. Lab Scenario Now that the Proseware instance of SQL Server has been installed and configured on the server, a number of additional database configurations need to be performed. As the database administrator, you need to perform these configuration changes. You need to create a new database on the server, based on requirements from an application vendor s specifications. A client has sent you a database that needs to be installed on the Proseware instance. Instead of sending you a backup, they have sent a detached database and log file. You need to attach the database to the Proseware instance.

21 Lab Instructions: Working with Databases 3 A consultant has also provided recommendations regarding tempdb configuration that you need to review and implement if appropriate. Supporting Documentation tempdb Size Requirement (For Exercise 1) File Size (in MB) Data 30 Log 10 RateTracking Database Specification Item DatabaseName Primary Data File Log File Secondary Data File #1 Secondary Data File #2 Requirement RateTracking Logical name = RateTracking_dat File name = RateTracking.mdf Folder = D:\MKTG Initial size = 10MB Maximum file size = 100MB Autogrowth amount = 10MB Filegroup = PRIMARY Logical name = RateTracking_log File name = RateTracking.ldf Folder = L:\MKTG Initial size = 20MB Maximum file size = unlimited Autogrowth amount = 20MB Filegroup = Not Applicable Logical name = RateTracking_dat_1 File name = RateTracking_1.ndf Folder = D:\MKTG Initial size = 20MB Maximum file size = 100MB Autogrowth amount = 10MB Filegroup = USERDATA Logical name = RateTracking_dat_2 File name = RateTracking_2.ndf Folder = D:\MKTG Initial size = 20MB Maximum file size = 100MB Autogrowth amount = 10MB Filegroup = USERDATA

22 4 Lab Instructions: Working with Databases (continued) Item Secondary Data File #3 Secondary Data File #4 Default Filegroup Requirement Logical name = RateTracking_dat_3 File name = RateTracking_3.ndf Folder = D:\MKTG Initial size = 200MB Maximum file size = 500MB Autogrowth amount = 50MB Filegroup = ARCHIVE Logical name = RateTracking_dat_4 File name = RateTracking_4.ndf Folder = D:\MKTG Initial size = 200MB Maximum file size = 500MB Autogrowth amount = 50MB Filegroup = ARCHIVE USERDATA tempdb Requirements From The Consultant (For Exercise 4) 1. Move the tempdb primary data file to the folder D:\MKTG. 2. Move the tempdb log file to the folder L:\MKTG. 3. Add three additional files to tempdb as per the following table: Filename Secondary Data File #1 Secondary Data File #2 Secondary Data File #3 Requirements Logical name = tempdev2 File name = tempdb_file2.ndf Folder = D:\MKTG Initial size = 20MB Maximum file size = unlimited Autogrowth amount = 10MB Logical name = tempdev3 File name = tempdb_file3.ndf Folder = D:\MKTG Initial size = 20MB Maximum file size = unlimited Autogrowth amount = 10MB Logical name = tempdev4 File name = tempdb_file4.ndf Folder = D:\MKTG Initial size = 20MB Maximum file size = unlimited Autogrowth amount = 10MB

23 Lab Instructions: Working with Databases 5 Exercise 1: Adjust tempdb Configuration Scenario You will adjust the current configuration of the tempdb database. The main tasks for this exercise are as follows: 1. Adjust the size of tempdb. 2. Check that the tempdb size is still correct after a restart. Task 1: Adjust the size of tempdb Review the requirement for tempdb size in the Supporting Documentation. Adjust the tempdb size based on the requirement in the supporting documentation. Task 2: Check that the tempdb size is still correct after a restart Restart the Proseware server using SQL Server Configuration Manager. Check that tempdb is still the correct size. Results: After this exercise, you should have inspected and configured the tempdb database. Exercise 2: Create the RateTracking Database Scenario You will create a new database named RateTracking as per a supplied set of specifications. The main tasks for this exercise are as follows: 1. Create the database. 2. Create the required filegroups and files. 3. Change the default filegroup for the database. Task 1: Create the database Review the supplied requirements in the supporting documentation for the exercise. Create a new RateTracking database based on the requirements. Task 2: Create the required filegroups and files Review the supplied requirements in the supporting documentation for the required files and filegroups. Create the required filegroups and files. Task 3: Change the default filegroup for the database Review the supplied requirements in the supporting documentation for the default filegroup. Modify the default filegroup. Results: After this exercise, you should have created a new RateTracking database with multiple filegroups.

24 6 Lab Instructions: Working with Databases Exercise 3: Attach the OldProspects Database Scenario A client has sent you a database that needs to be installed on the Proseware instance. Instead of sending you a backup, they have sent a detached database and log file. You need to attach the database to the Proseware instance. The main tasks for this exercise are as follows: 1. Copy the database files. 2. Attach the database to the MKTG instance. Task 1: Copy the database files Copy the files to new folders as per the table below: Filename Source Folder Destination Folder OldProspects.mdf D:\10775A_Labs\10775A_04_PRJ D:\MKTG OldProspects.ldf D:\10775A_Labs\10775A_04_PRJ L:\MKTG Task 2: Attach the database to the MKTG instance Attach the OldProspects database to the MKTG instance. Results: After this exercise, you should have attached a database to a client s server. Challenge Exercise 4: Add Multiple Files to tempdb (Only if time permits) Scenario A consultant has also provided recommendations regarding tempdb configuration that you need to review and implement. The main tasks for this exercise are as follows: 1. Review the tempdb file requirements. 2. Move existing files. 3. Add new files. 4. Restart the server and check file locations. Task 1: Review the tempdb file requirements In the Supporting Documentation review the tempdb Requirements From The Consultant section. Task 2: Move existing files Move the existing tempdb data and log files to the required locations as specified in the supporting documentation. Task 3: Add new files Add the additional tempdb files as required in the supporting documentation.

25 Lab Instructions: Working with Databases 7 Task 4: Restart the server and check file locations Restart the Proseware server. View the Properties of the tempdb database and ensure the list of files match the requirements. Results: After this exercise, you should have reconfigured tempdb as per the requirements.

26 Lab Instructions: Understanding SQL Server 2012 Recovery Models 1 Module 5 Lab Instructions: Understanding SQL Server 2012 Recovery Models Contents: Exercise 1: Plan a Backup Strategy 5 Exercise 2: Configure Recovery Models 6 Challenge Exercise 3: Review Recovery Models and Strategy (Only if time permits) 7

27 2 Lab Instructions: Understanding SQL Server 2012 Recovery Models Lab 5: Understanding SQL Server Recovery Models Lab Setup For this lab, you will use the available virtual machine environment. Before you begin the lab, you must complete the following steps: 1. Revert the virtual machines as per the instructions in D:\10775A_Labs\Revert.txt. 2. In the virtual machine, click Start, click All Programs, click Microsoft SQL Server 2012, and click SQL Server Management Studio. 3. In the Connect to Server window, type Proseware in the Server name text box. 4. In the Authentication drop-down list box, select Windows Authentication and click Connect. 5. In the File menu, click Open, and click Project/Solution. 6. In the Open Project window, open the project D:\10775A_Labs\10775A_05_PRJ\10775A_05_PRJ.ssmssln. 7. From the View menu, click Solution Explorer. In Solution Explorer, double-click the query 00-Setup.sql. When the query window opens, click Execute on the toolbar. Lab Scenario You need to implement a database recovery strategy. The business unit from Proseworks, Inc. has provided you with the availability needs for the databases on the new Proseware SQL Server instance. You need to plan how you will meet the requirements and then implement your strategy.

28 Lab Instructions: Understanding SQL Server 2012 Recovery Models 3 If you have time, there is another issue that your manager would like you to work on. There is another instance of SQL Server installed for supporting Customer Service operations. There is concern that existing databases on the CustomerService server instance are configured inappropriately and have invalid backup strategies, based on their RPO and RTO requirements. In this exercise, you need to review the database recovery models and backup strategies for the databases on the CustomerService instance and provide recommended changes. Supporting Documentation Business Database Continuity Requirements for Databases on the Proseware Server Instance (for Exercises 1 and 2) Recovery Time Objectives 1. The MarketDev database must never be unavailable for longer than eight hours. 2. The Research database must never be unavailable for longer than two hours. Recovery Point Objectives 1. When the MarketDev database is recovered from a failure, no more than 30 minutes of transactions may be lost. 2. When the Research database is recovered from a failure, all transactions that were completed up to the end of the previous weekday must be recovered. Projected Characteristics Characteristic MarketDev database size Research database size Total backup throughput Total restore throughput Average rate of change to the MarketDev database during office hours Estimated Value 20GB 200MB 100MB per minute 80MB per minute 1GB per hour Average rate of change to the Research database during office hours 10MB per hour Percentage of the MarketDev database changed each day (average) 1.2% Percentage of the Research database changed each day (average) 80% Office hours (no full database backups permitted during these hours) 8am to 6pm

29 4 Lab Instructions: Understanding SQL Server 2012 Recovery Models Business Database Continuity Requirements for Databases on the CustomerService Server Instance (for Exercises 3) Recovery Time Objectives 1. The CreditControl database must never be unavailable for longer than two hours. 2. The PotentialIssue database must never be unavailable for longer than one hour. Recovery Point Objectives 1. When the CreditControl database is recovered from a failure, no more than five minutes of transactions may be lost. 2. When the PotentialIssue database is recovered from a failure, no more than 30 minutes of transactions may be lost. Projected Characteristics Characteristic CreditControl database size PotentialIssue database size (at the start of each week after archiving activity is complete) Total backup throughput Total restore throughput Average rate of change to the CreditControl database during office hours Average rate of change to the PotentialIssue database (constant all week long 24 hours per day) Percentage of the CreditControl database changed each day (average) Percentage of the PotentialIssue database changed each day (average) Office hours (no full database activity permitted during these hours) Estimated Value 20GB 200MB 100MB per minute 80MB per minute 500MB per hour 10MB per hour 60% 50% 8am to 7pm

30 Lab Instructions: Understanding SQL Server 2012 Recovery Models 5 Existing Backup Strategy For CreditControl Database Recovery Model: Full Type of Backup Schedule Full Saturday at 6AM, Wednesday at 6AM Differential Sunday at 10PM, Monday at 10PM, Tuesday at 10PM, Thursday at 10PM, Friday at 10PM Log Every 60 minutes on the hour Existing Backup Strategy For PotentialIssue Database Recovery Model: Full Type of Backup Schedule Full Sunday at 10PM Log Every 15 minutes starting at 10 minutes pas the hour Exercise 1: Plan a Backup Strategy Scenario You need to plan a backup strategy for the two databases on the new Proseware instance. You have been provided with RPO (recovery point objectives) and RTO (recovery time objectives) for both databases, as part of a business continuity statement. The main tasks for this exercise are as follows: 1. Review the business requirements. 2. Determine an appropriate backup strategy for each database. Task 1: Review the business requirements Review the supplied business requirements in the supporting documentation for the exercise. Task 2: Determine an appropriate backup strategy for each database Determine an appropriate backup strategy for each database. For the MarketDev database: Which recovery model should be used?

31 6 Lab Instructions: Understanding SQL Server 2012 Recovery Models Complete the following table for the backup schedule: Type of Backup Schedule For the Research database: Which recovery model should be used? Complete the following table for the backup schedule: Type of Backup Schedule Results: After this exercise, you should have created a plan to backup two databases. Exercise 2: Configure Recovery Models Scenario You have reviewed the database recovery models and identified that the current database recovery models do not meet the availability needs of the business. In this exercise, you need to set the recovery models for the databases that do not meet the requirements. The main task for this exercise is as follows: 1. Review and adjust the current database recovery models. Task 1: Review and adjust the current database recovery models Review the recovery models that you decided were required in Exercise 1, check whether or not the existing recovery models for the MarketDev and Research databases match your recommendations. If not, change the recovery models as per your recommendations. Results: After this exercise, you should have reviewed and modified the database recovery models where required.

32 Lab Instructions: Understanding SQL Server 2012 Recovery Models 7 Challenge Exercise 3: Review Recovery Models and Strategy (Only if time permits) Scenario There is another instance of SQL Server installed for supporting Customer Service operations. There is concern that existing databases on the CustomerService server instance are configured inappropriately and have invalid backup strategies, based on their RPO and RTO requirements. In this exercise, you need to review the database recovery models and backup strategies for the databases on the CustomerService instance and provide recommended changes. The main tasks for this exercise are as follows: 1. Review the RPO and RTO requirements for the databases. 2. Review the existing recovery models and backup strategies. 3. Indicate whether or not the strategy would be successful. Task 1: Review the RPO and RTO requirements for the databases The supporting documentation includes details of the business continuity requirements for the databases. You need to review this documentation. Task 2: Review the existing recovery models and backup strategies The supporting documentation also includes details of the backup strategy for the databases. You need to review this documentation. Task3: Indicate whether or not the strategy would be successful You need to assess whether or not the current backup strategy and recovery model configuration is capable of supporting the business continuity requirements. If not, explain why it would not work. Results: After this exercise, you should have assessed the strategy.

33 Lab Instructions: Backup of SQL Server 2012 Databases 1 Module 6 Lab Instructions: Backup of SQL Server 2012 Databases Contents: Exercise 1: Investigate Backup Compression 3 Exercise 2: Transaction Log Backup 3 Exercise 3: Differential Backup 4 Exercise 4: Copy-only Backup 4 Challenge Exercise 5: Partial Backup (Only if time permits) 5

34 2 Lab Instructions: Backup of SQL Server 2012 Databases Lab 6: Backup of SQL Server Databases Lab Setup For this lab, you will use the available virtual machine environment. Before you begin the lab, you must complete the following steps: 1. Revert the virtual machines as per the instructions in D:\10775A_Labs\Revert.txt. 2. In the virtual machine, click Start, click All Programs, click Microsoft SQL Server 2012, and click SQL Server Management Studio. 3. In the Connect to Server window, type Proseware in the Server name text box. 4. In the Authentication drop-down list box, select Windows Authentication and click Connect. 5. In the File menu, click Open, and click Project/Solution. 6. In the Open Project window, open the project D:\10775A_Labs\10775A_06_PRJ\10775A_06_PRJ.ssmssln. 7. From the View menu, click Solution Explorer. In Solution Explorer, double-click the query 00-Setup.sql. When the query window opens, click Execute on the toolbar. Lab Scenario You have reviewed and updated the recovery models. As the database administrator, you need to implement a database backup strategy. You have been provided with details of the required backup strategy for a number of databases on a SQL Server instance. You need to complete the required backups.

35 Lab Instructions: Backup of SQL Server 2012 Databases 3 Exercise 1: Investigate Backup Compression Scenario The size of the database backups has been increasing with the number of orders being placed. You want to investigate the amount of space that can be saved by using backup compression. In this exercise, you need to investigate the effectiveness of backup compression when backing up the MarketDev database on the Proseware instance. You will perform a full database backup with backup compression disabled. You will then perform another full database backup with backup compression enabled. You will compare the backup files produced to identify the possible space savings. The main tasks for this exercise are as follows: 1. Create a database backup without compression. 2. Create a database backup with compression. 3. Compare the file sizes created. Task 1: Create a database backup without compression Using Windows Explorer, create a new folder L:\SQLBackups. Perform a full backup of the MarketDev database with compression disabled to the file L:\SQLBackups\MarketDev_Full_Uncompressed.BAK. Task 2: Create a database backup with compression Perform a full backup of the MarketDev database with compression enabled to the file L:\SQLBackups\MarketDev_Full_Compressed.BAK. Task 3: Compare the file sizes created Calculate the space savings provided by compression as: SpaceSavings=(Uncompressed size Compressed size)*100/uncompressed size Results: After this exercise, you have calculated the space saved by using backup compression on the MarketDev database. Exercise 2: Transaction Log Backup Scenario Part of the ongoing management of the MarketDev database is a series of transaction log backups to provide point in time recovery. In this exercise, you need to back up the transaction log. The main tasks for this exercise are as follows: 1. Execute a script to introduce workload to the MarketDev database. 2. Backup the transaction log on the MarketDev database. Task 1: Execute a script to introduce workload to the MarketDev database Open and execute the script file 61 Workload File.sql from Solution Explorer.

36 4 Lab Instructions: Backup of SQL Server 2012 Databases Task 2: Backup the transaction log on the MarketDev database Backup the transaction log of the MarketDev database to the file L:\SQLBackups\MarketDev_Log_Compressed.BAK. Use backup compression during the backup. Results: After this exercise, you should have completed a transaction log backup. Exercise 3: Differential Backup Scenario There is a concern that the data volumes in the MarketDev database will be so large that daily full backups will not be possible. In this exercise, you need to perform a differential backup to assist to manage the size of the database backups. The main tasks for this exercise are as follows: 1. Execute a script to introduce workload to the MarketDev database. 2. Create a differential backup of the MarketDev database. Task 1: Execute a script to introduce workload to the MarketDev database Open and execute the script file 61 Workload File.sql from Solution Explorer. Task 2: Create a differential backup of the MarketDev database Create a differential backup of the MarketDev database to the file L:\SQLBackups\MarketDev_Differential_Compressed.BAK. Use backup compression during the backup. Using Windows Explorer, note the size of the Differential backup compared to the Full backup. Task 3: Execute a script to introduce workload to the MarketDev database Open and execute the script file 61 Workload File.sql from Solution Explorer. Task 4: Append a differential backup to the previous differential backup file Append a differential backup of the MarketDev database to the file L:\SQLBackups\MarketDev_Differential_Compressed.BAK. Using Windows Explorer, note that the size of the Differential backup has increased. The file now contains two backups. Results: After this exercise, you should have completed two differential backups. Exercise 4: Copy-only Backup Scenario Another team periodically needs a temporary copy of the MarketDev database. It is important that these copies do not interfere with the backup strategy that is being used. In this exercise, you need to perform a copy-only backup and verify the backup.

37 Lab Instructions: Backup of SQL Server 2012 Databases 5 The main task for this exercise is as follows: 1. Create a copy-only backup of the MarketDev database, ensuring to choose to verify the backup. Task 1: Create a copy-only backup of the MarketDev database, ensuring to choose to verify the backup Create a copy-only backup of the MarketDev database to the file L:\SQLBackups\MarketDev_Copy_Compressed.BAK. Make sure you choose to: Verify the backup while creating it. Use backup compression. Choose to create a new media set called MarketDev Copy Backup. For the media set description use MarketDev Copy Backup for Integration Team. Results: After this exercise, you should have completed a copy-only backup. Challenge Exercise 5: Partial Backup (Only if time permits) Scenario On the Proseware instance, there is a database called RateTracking that has two filegroups. The ARCHIVE filegroup is set to read-only and both the default filegroup USERDATA and the PRIMARY filegroup are read-write. In this exercise, you need to back up the read-write filegroups only, using T-SQL commands. The main task for this exercise is as follows: 1. Perform a backup of the read-write filegroups on the RateTracking database. Task 1: Perform a backup of the read-write filegroups on the RateTracking database Perform a backup of the read-write filegroups (USERDATA and PRIMARY) on the RateTracking database. Write the backup to the file L:\SQLBackups\RateTracking_ReadWrite.BAK. Use the CHECKSUM and INIT options. Results: After this exercise, you should have completed a partial backup.