Exploring Online Database Operations

Size: px

Start display at page:

Download "Exploring Online Database Operations"

Muriel Small
6 years ago
Views:

1 Exploring Online Database Operations

2 Contents Managed lock priorities for partition switch... 3 Managed lock priorities index rebuild Terms of use Exploring Online Database Operations

Managed lock priorities for partition switch Estimated time to complete lab is 20 minutes In this lab, you will utilize new features of SQL Server 2014 to manage the lock priorities using some new

3 Managed lock priorities for partition switch Estimated time to complete lab is 20 minutes In this lab, you will utilize new features of SQL Server 2014 to manage the lock priorities using some new options. The DDL commands can be set to execute in a low priority queue and allow the optimizer to choose whether to wait, or kill itself or any blockers if they exist. In previous versions of SQL Server, once a partition has been swapped in, you had two options: rebuild the new partition offline, which means the partition is locked to any users for the duration of the rebuild; or keep the partition online and rebuild the index for the entire partitioned table instead. However, in SQL Server 2014, you have the ability to rebuild one or more partitions indexes while they are online and available for query. Connect to SQLONE computer 1. Click on SQLONE button on right side of the screen to connect to the SQLONE computer. If you see the following in the lower right corner of the screen, you can jump to step 5 below to set your screen resolution. 2. Click Send Ctrl-Alt-Del for SQLONE computer and then click Switch user. 3. Click Send Ctrl-Alt-Del for SQLONE computer again and then click Other user. 4. Log on to SQLONE computer as labuser with password pass@word1 Note, if you have a monitor that supports a larger screen resolution than 1024 x 768, you can change the screen resolution for the lab to go as high as 1920 x By going to a higher Exploring Online Database Operations 3

4 screen resolution, it will be easier to use SQL Server Management Studio. 5. Right click on the desktop and click on Screen resolution. 6. Select 1366 x 786 (a good minimum screen size for using SSMS) and click OK. 7. Click Keep Changes. 8. Resize the client hollaunchpad Online window for the lab to fit your screen resolution. Begin a blocking transaction 1. Open SQL Server 2014 Management Studio with a connection to the SQLONE server using Windows Authentication. In previous versions of SQL Server, running a DDL statement like a Partition Swap would have put the command into the same queue as other queries. The session would have to wait for all other locks to complete before being able to carry out the operation and then causing locks on the table itself and providing no control to the Database Administrator The following script will begin a Blocking Transaction. Using a Transaction means that we can ensure the command does not commit and we can ensure the lock remains in place for subsequent commands 2. Browse to C:\SQLSCRIPTS\E2 and select E2A-6-#1 4. Click Execute Exploring Online Database Operations 4

$Events 2. Browse to C:\SQLSCRIPTS\E2 and select E2A-6-#2 4.$ $detailed events containing the new commands and settings 2. Browse to C:\SQLSCRIPTS\E2 and select E2A-6-#3 4.$

5 Create extended event session for MLP events The following script will create the Extended Event Session for the new MLP Events 2. Browse to C:\SQLSCRIPTS\E2 and select E2A-6-#2 4. Click Execute Setup event logging This following script will set up Richard s event logging to ensure that he captures detailed events containing the new commands and settings 2. Browse to C:\SQLSCRIPTS\E2 and select E2A-6-#3 4. Click Execute Perform partition switch Exploring Online Database Operations 5

$locking sessions before timing out and killing itself 2. Browse to C:\SQLSCRIPTS\E2 and select E2A-6-#4 4.$

6 On this first attempt, Richard is going to execute the Partition Switch command using new parameters that will put the partition switch command into a low priority queue and await the outcome of any locking sessions before timing out and killing itself 2. Browse to C:\SQLSCRIPTS\E2 and select E2A-6-#4 4. Click Execute Test locking behavior Notice the timeout parameter (MAX_DURATION) these are the number of minutes. The other new parameter is ABORT_AFTER_WAIT = SELF means that this session will kill itself if any locks are not released inside one minute While the command is running 2. Browse to C:\SQLSCRIPTS\E2 and select E2A-6-#5 Exploring Online Database Operations 6

7 4. Click Execute Notice the Sch-M Locks and the fact that the switch partition session is in a low priority queue After one minute, the query in script E2A-6-#4.sql will be terminated with a failure return to the previous query window to see this Exploring Online Database Operations 7

$Browse to C:\SQLSCRIPTS\E2 and select E2A-6-#6 4. Click Execute Notice how we have changed the ABORT_AFTER_WAIT to BLOCKERS.$ This means that after the timeout interval, any sessions blocking the partition switch will be terminated and the switch

This means that after the timeout interval, any sessions blocking the partition switch will be terminated and the switch

8 Test ABORT_AFTER_WAIT The following script will change the ABORT_AFTER_WAIT to BLOCKERS 2. Browse to C:\SQLSCRIPTS\E2 and select E2A-6-#6 4. Click Execute Notice how we have changed the ABORT_AFTER_WAIT to BLOCKERS. This means that after the timeout interval, any sessions blocking the partition switch will be terminated and the switch session removed from the queue and allowed to run. After a minute, the Partition Switch command will complete successfully Exploring Online Database Operations 8

$Stop event recording The following script will stop the recording of events 2. Browse to C:\SQLSCRIPTS\E2 and select E2A-6-#7 4.$

9 Stop event recording The following script will stop the recording of events 2. Browse to C:\SQLSCRIPTS\E2 and select E2A-6-#7 4. Click Execute Close all open query windows New extended event logging features We will now look at the new Logging features 1. From SQL Server 2014 Management Studio expand the Management node in the Object Explorer under the SQLONE connection heading Exploring Online Database Operations 9

10 2. Expand Extended Events and then Sessions 3. Expand the session called mlp_session 4. Right-click on package0.event_file and select View Target Data. Exploring Online Database Operations 10

11 Effect of KILL SELF and KILL ALL BLOCKERS commands The new logging features which have captured information about the low priority queue and Sch-M locks and show the effect of the KILL SELF and KILL ALL BLOCKERS commands Exploring Online Database Operations 11

$Browse to C:\SQLSCRIPTS\E2 and select E2A-6-#8 4.$

12 New diagnostics for error log The following script will check the Error Log for New Diagnostics 2. Browse to C:\SQLSCRIPTS\E2 and select E2A-6-#8 4. Click Execute Exploring Online Database Operations 12

13 Scroll to the bottom of the returned results and notice the logging of the new events. Thus the DBA has more visibility over why certain actions have been taken by use of the Dynamic Management Views, Events log and Extended Events. 5. Close ALL the Query windows in SQL Server 2014 Management Studio Managed lock priorities index rebuild Lock priority for index rebuild In this exercise, you will try out the ability to rebuild a partitioned index online. Previously you were restricted to either rebuilding the entire index online or a single index partition could be rebuilt offline. Both of these actions would have had an impact on other users or applications depending on when they were run. These actions also use the new features provided by Managed Lock Priorities The following script will start a blocking transaction 2. Browse to C:\SQLSCRIPTS\E2 and select E2A-6-#9 Exploring Online Database Operations 13

$From SQL Server 2014 Management Studio, open the File 6. Browse to C:\SQLSCRIPTS\E2 and select E2A-6-#10 7.$

14 4. Click Execute Setup a new extended events capture This time an extra event type is being captured progress report online index operation so that this can be trapped separately 5. From SQL Server 2014 Management Studio, open the File 6. Browse to C:\SQLSCRIPTS\E2 and select E2A-6-#10 7. Click Open 8. Click Execute Start the extended event capture We will now start the event capture 2. Browse to C:\SQLSCRIPTS\E2 and select E2A-6-#11 Exploring Online Database Operations 14

$Browse to C:\SQLSCRIPTS\E2 and select E2A-6-#12 4. Click Execute While the above query is running we will check the lock and blocked request status Check blocking status 2.$

15 4. Click Execute Attempt a rebuild partition command with default behavior The following script will demonstrate the default behavior without any of the new features 2. Browse to C:\SQLSCRIPTS\E2 and select E2A-6-#12 4. Click Execute While the above query is running we will check the lock and blocked request status Check blocking status 2. Browse to C:\SQLSCRIPTS\E1 and select E2A-6-#13 Exploring Online Database Operations 15

Rebuild partition with ABORT_AFTER_WAIT=BLOCKERS The following script will demonstrate the new feature of

16 4. Click Execute Notice how the index rebuild is being blocked by the running transaction 5. Go back to the previous query window and Kill the running command by clicking on the red button (see below) Rebuild partition with ABORT_AFTER_WAIT=BLOCKERS The following script will demonstrate the new feature of rebuilding the Index using Managed Lock Priorities 2. Browse to C:\SQLSCRIPTS\E2 and select E2A-6-#14 Exploring Online Database Operations 16

$Once the command has completed successfully, stop the event capture session 5. From SQL Server 2014 Management Studio, open the File 6. Browse to C:\SQLSCRIPTS\E1 and select E2A-6-#15 7. Click Open 8.$

17 4. Click Execute Notice how by setting a low priority queue and timeout after a minute, any blocking transactions will be terminated to allow the online index rebuild to take place. Once the command has completed successfully, stop the event capture session 5. From SQL Server 2014 Management Studio, open the File 6. Browse to C:\SQLSCRIPTS\E1 and select E2A-6-#15 7. Click Open 8. Click Execute Check the extended event session log We will now have a look at the new logging features 1. From SQL Server 2014 Management Studio expand the Management node in the Object Explorer under SQLONE connection heading. If this is already open, refresh it by rightclicking on the node and click Refresh 2. Expand Extended Events and then Sessions 3. Expand the session called spoir_session Exploring Online Database Operations 17

18 4. Right-click on package0.event_file and select View Target Data. Scroll to the bottom and notice the new logging features which have captured information about the low priority queue and SCH-M locks and show the effect of the KILL ALL BLOCKERS commands Exploring Online Database Operations 18

$Browse to C:\SQLSCRIPTS\E2 and select E2A-6-#16 7. Click Open 8.$

19 The following script will check the Error Log for New Diagnostics 5. From SQL Server 2014 Management Studio, open the File 6. Browse to C:\SQLSCRIPTS\E2 and select E2A-6-#16 7. Click Open 8. Click Execute 9. Scroll to the bottom of the results Exploring Online Database Operations 19

The impact of being able to rebuild partitioned indexes online is huge and provides DBAs with the ability to load data into a table during the business day without impacting on the performance of the

20 The impact of being able to rebuild partitioned indexes online is huge and provides DBAs with the ability to load data into a table during the business day without impacting on the performance of the database for other users. This would be very useful in a data warehousing environment where intra-day loads into a fact table can be handled without 10. Close all open query windows in SQL Server 2014 Management Studio. 11. Close SQL Server 2014 Management Studio Exploring Online Database Operations 20

21 Terms of use 2014 Microsoft Corporation. All rights reserved. By using this Hands-on Lab, you agree to the following terms: The technology/functionality described in this Hands-on Lab is provided by Microsoft Corporation in a sandbox testing environment for purposes of obtaining your feedback and to provide you with a learning experience. You may only use the Hands-on Lab to evaluate such technology features and functionality and provide feedback to Microsoft. You may not use it for any other purpose. You may not modify, copy, distribute, transmit, display, perform, reproduce, publish, license, create derivative works from, transfer, or sell this Hands-on Lab or any portion thereof. COPYING OR REPRODUCTION OF THE HANDS-ON LAB (OR ANY PORTION OF IT) TO ANY OTHER SERVER OR LOCATION FOR FURTHER REPRODUCTION OR REDISTRIBUTION IS EXPRESSLY PROHIBITED. THIS HANDS-ONLAB PROVIDES CERTAIN SOFTWARE TECHNOLOGY/PRODUCT FEATURES AND FUNCTIONALITY, INCLUDING POTENTIAL NEW FEATURES AND CONCEPTS, IN A SIMULATED ENVIRONMENT WITHOUT COMPLEX SET-UP OR INSTALLATION FOR THE PURPOSE DESCRIBED ABOVE. THE TECHNOLOGY/CONCEPTS REPRESENTED IN THIS HANDS-ON LAB MAY NOT REPRESENT FULL FEATURE FUNCTIONALITY AND MAY NOT WORK THE WAY A FINAL VERSION MAY WORK. WE ALSO MAY NOT RELEASE A FINAL VERSION OF SUCH FEATURES OR CONCEPTS. YOUR EXPERIENCE WITH USING SUCH FEATURES AND FUNCITONALITY IN A PHYSICAL ENVIRONMENT MAY ALSO BE DIFFERENT. FEEDBACK. If you give feedback about the technology features, functionality and/or concepts described in this Hands-on Lab to Microsoft, you give to Microsoft, without charge, the right to use, share and commercialize your feedback in any way and for any purpose. You also give to third parties, without charge, any patent rights needed for their products, technologies and services to use or interface with any specific parts of a Microsoft software or service that includes the feedback. You will not give feedback that is subject to a license that requires Microsoft to license its software or documentation to third parties because we include your feedback in them. These rights survive this agreement. MICROSOFT CORPORATION HEREBY DISCLAIMS ALL WARRANTIES AND CONDITIONS WITH REGARD TO THE HANDS-ON LAB, INCLUDING ALL WARRANTIES AND CONDITIONS OF MERCHANTABILITY, WHETHER EXPRESS, IMPLIED OR STATUTORY, FITNESS FOR A PARTICULAR PURPOSE, TITLE AND NON- INFRINGEMENT. MICROSOFT DOES NOT MAKE ANY ASSURANCES OR Exploring Online Database Operations 21

22 REPRESENTATIONS WITH REGARD TO THE ACCURACY OF THE RESULTS, OUTPUT THAT DERIVES FROM USE OF THE VIRTUAL LAB, OR SUITABILITY OF THE INFORMATION CONTAINED IN THE VIRTUAL LAB FOR ANY PURPOSE. DISCLAIMER This lab contains only a portion of new features and enhancements in Microsoft SQL Server Some of the features might change in future releases of the product. In this lab, you will learn about some, but not all, new features. Exploring Online Database Operations 22

Introduction to Azure Machine Learning

Introduction to Azure Machine Learning Contents Overview... 3 Create a Workspace and Experiment... 5 Explore and Visualize Data... 10 Create a Simple Predictive Model... 14 Exercises... 25 Terms of Use...