Amit Bansal CTO Edominer Systems P Ltd | Peopleware India Who Is Amit Bansal?

Total Page:16

File Type:pdf, Size:1020Kb

Amit Bansal CTO Edominer Systems P Ltd | Peopleware India Who Is Amit Bansal? Amit Bansal CTO eDominer Systems P Ltd | Peopleware India Who is Amit Bansal? CTO, eDominer Systems & Peopleware India Conducted more than 200 workshops on SQL Server & BI for top notch IT companies world wide Microsoft MVP for SQL Server Microsoft Certified Trainer Advisory Council member Speaker at TechED India, TechED US & TechED Europe Technical Reviewer – MSL courses on SQL Server SME – SQL Server 2008 certifications UG Lead (Delhi NCR) – Culminis Manager – www.WeTogether.in, www.DelhiDevs.com, www.BlogBoard.in Agenda & Session takeaways Query Optimizer characteristics Using Query & Table Hints Plan Freezing concept Scenarios from the wild What are Plan Guides & different types Implementing Plan Guides Managing & Validating Plan Guides Plan Guide considerations Summary Query Optimizer characteristics Cost based optimization Does the Query Optimizer always do a fine job? Does it always select the best query plan? Use Hints to affect the query plan selection Use Hints as a last resort, Use with caution To be used only by experienced DBDs & DBAs Is there really a problem? Check if there are other issues Identify the real cause of a poor plan What if SQL Server fails to generate a valid plan? (error 8622 is raised) Join, Query & Table Hints FAST N Hint Functionality RECOMPILE Index Hints OPTIMIZE FOR Hint OPTIMIZE FOR UNKNOWN Hint Join Hints JOIN Hints Parallelism FORCE ORDER Hint Locking INDEX Hint Compilation FORCESEEK Hint READPAST Hint Table Hints USE PLAN Hint …. Plan Freezing concepts Forcing / Locking down a query plan Provides greater query performance stability & predictability Enables organizations to promote stable query plans Hardware Server replacements Server upgrades Production Deployments Plan Freezing can Optimize query performance Copy query plans between servers Prevent the plan cache from growing excessively with large compiled plans that are not reused Scenarios from the wild… A query started mis-behaving after SQL Server upgrade Query text cannot be modified to use hints Eg: Application/vendor code, ISV, etc Query performance degraded after hardware upgrade You need to copy plans from one server to the other Overcoming ‘Parameter Sniffing’ issues After a service pack upgrade – “my query just starting running 4 times slower today and the plan is different from yesterday” ……sigh What are Plan Guides? Plan Freezing concept is implemented with Plan Guides A DB object that associates a set of query hints with the query Can be created using: sp_create_plan_guide sp_create_plan_guide_from_handle Fixed query plan (XML Showplan output) can be also be applied Available in Standard, Enterprise, Evaluation & Developer edition Types of Plan Guides Object Plan Guides matches queries that execute in the context of a SQL Server object (SP, UDF, DML triggers etc) SQL Plan Guides matches queries that execute in the context of stand-alone Transact-SQL statements and batches ( not part of a database object) Template Plan Guides matches stand-alone queries that parameterize to a specified form To override the current PARAMETERIZATION setting Object Plan Guides You are interested in a T-SQL statement appearing in the context of a SQL Server object SQL Server object can be: Stored Procedure User Defined Function (Scalar) Multi-statement table-valued user-defined functions DML Triggers Object Plan Guides sp_create_plan_guide @name = N'Guide1', @stmt = N'SELECT *FROM Sales.SalesOrderHeader AS h, Sales.Customer AS c, Sales.SalesTerritory AS t WHERE h.CustomerID = c.CustomerID AND c.TerritoryID = t.TerritoryID AND CountryRegionCode = @Country_region', @type = N'OBJECT', @module_or_batch = N'Sales.GetSalesOrderByCountry', @params = NULL, @hints = N'OPTION (OPTIMIZE FOR (@Country_region = N''US''))' Implementing Object Plan Guides Name Title Company SQL Plan Guides You are interested in a particular T-SQL statement Stand-alone Or part of a batch T-SQL statements sent by CLR objects, extended SPs & Dynamic SQL (EXEC (sql_string)) are processed as batches The text has to be exactly the same: Case, whitespace, etc. SQL Plan Guides sp_create_plan_guide @name = N'Guide2', @stmt = N'SELECT TOP 1 * FROM Sales.SalesOrderHeader ORDER BY OrderDate DESC', @type = N'SQL', @module_or_batch = NULL, @params = NULL, @hints = N'OPTION (MAXDOP 1)'; Implementing SQL Plan Guides Name Title Company Template Plan Guides To override PARAMETERIZATION database setting Can only use the following hints: PARAMETERIZATION FORCED PARAMETERIZATION SIMPLE Little tricky SQL Server has to construct a template of the query in the same format that it will be in once it is parameterized Special stored procedure: sp_get_query_template @params is only used for TEMPLATE plan guide Template Plan Guides EXEC sp_create_plan_guide @name = N'TemplateGuide1', @stmt = N'SELECT * FROM AdventureWorks.Sales.SalesOrderHeader AS h INNER JOIN AdventureWorks.Sales.SalesOrderDetail AS d ON h.SalesOrderID = d.SalesOrderID WHERE h.SalesOrderID = @0', @type = N'TEMPLATE', @module_or_batch = NULL, @params = N'@0 int', @hints = N'OPTION(PARAMETERIZATION FORCED)'; Implementing Template Plan Guides Name Title Company Applying a Fixed Query Plan to a Plan Guide Useful when you know about an existing execution plan that performs better than the one selected by the optimizer for a particular query Can be applied to OBJECT or SQL plan guides Extract the XML Showplan from the cache and supply it to the sp_create_plan_guide Applying a Fixed Query Plan to a Plan Guide Creating Plan Guides directly from the plan cache Creates one or more plan guides from a query plan in the plan cache Can be applied to OBJECT or SQL plan guides Extract the plan handle from the cache and supply it to the sp_create_plan_guide_from_handle Creating Plan Guides directly from the plan cache Managing & Validating Plan Guides Managing Plan Guides sp_control_plan_guide ENABLE, DISABLE, DROP Validating Plan guides sys.fn_validate_plan_guide Plan Guides considerations The statement text in the plan guide must exactly match the query text To verify that your plan guide was used, see for specific elements in XML Showplan output PlanGuideDB & PlanGuideName (or) TemplatePlanGuideDB & TemplatePlanGuideName Query Plan (properties window) Summary There are many scenarios where you cannot use hints Plan Guides come to rescue Three different types (OBJECT, SQL, TEMPLATE) SQL Server 2008 enhancements Applying a fixed query to a plan guide using XML Showplan Creating a plan directly from a plan in the plan cache Validating Plan Guides Plan Guide Considerations © 2009 Microsoft Corporation. All rights reserved. Microsoft, Windows, Windows Vista and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION..
Recommended publications
  • Sqlserver 2005, 2008, 2012
    Installation and Startup Guide Edition March 2020 Copyright © Atos IT Solutions and Services GmbH 2020 Microsoft, MS, MS-DOS and Windows are trademarks of Microsoft Corporation. The reproduction, transmission, translation or exploitation of this document or its content is not permitted without express written authority. Offenders will be liable for damages. All rights reserved, including rights created by patent grant or registration of a utility model or design. Right of technical modification reserved. Installation Guide TEMPPO V6.3 Edition March 2020 Contents Contents 1 Introduction ....................................................................................... 1 2 Installation ........................................................................................ 2 3 Startup & first steps ......................................................................... 27 4 Appendix .......................................................................................... 30 Installation Guide TEMPPO V6.3 Edition March 2020 Introduction 1 Introduction This manual describes the installation of TEMPPO (Test Execution, Management, Planning and rePorting Organizer) Version 6.3 as client. Managing the test process involves a large number of engineering disciplines like project management, risk management, high and low level design, development and metrics collection. In former times testers managed their tests and test management with Word table or Excel sheets which had the main disadvantages that tests were not organized, couldn’t be
    [Show full text]
  • Parallel and Append Hint in Insert Statement
    Parallel And Append Hint In Insert Statement Sunrise Gay subjoins his viridescence focalise pryingly. Is Odysseus preconscious when Marlin precool signally? Ocean-going Cole ensanguining unworthily. Insert statement with array inserts, then create an access method that parallel and hint in insert statement We can see which each source i was inserted into excel table only. Parallel statements that appends will append hint will propose an answer for a different sessions can. The table specified in tablespec is the probe table of the hash join. Oracle hint was an error logging table or merge statement itself is not possible. Before you can execute DML statements in parallel, you must display the parallel DML feature. The insert or insert and parallel hint in append hint is that page helpful in. Instructs the optimizer selectivity and parallel insert on the source records mark or azure storage requirements. Oracle choose among different options or may be i missed to understand. You do part of these large, update as cpus is genetated for pointing this hint and parallel in insert statement, the index partition, consider adding an error message is that your help us the. Doing all modifications to statement and parallel hint in append insert statement are too large database table were responsible for the plans and for the definition query? When a mortgage is overloaded and all input DOP is larger than the default DOP, the algorithm uses the default degree of input. Instructs the optimizer to use but full outer court, which prohibit a native execution method based on a hash join.
    [Show full text]
  • The Use of Hints in Object-Relational Query Optimization
    Comput Syst Sci & Eng (2004) 6: 337–345 International Journal of © 2004 CRL Publishing Ltd Computer Systems Science & Engineering The use of hints in object-relational query optimization David Taniar*, Hui Yee Khaw*. Haorianto Cokrowijoyo Tijoe* and Johanna Wenny Rahayu† *School of Business Systems, Monash University, Clayton, Victoria 3800, Australia. Email: {David.Taniar,Haorianto.Tjioe}@infotech.monash.edu.au †Department of Computer Science and Computer Engineering, La Trobe University, Bundoora, Victoria 3803, Australia Email: [email protected] Object-Relational queries are queries which can handle data objects feature on the existing relational data environment. REF is one of most impor- tant data structures in Object-Relational Databases can be explained as a logical pointer to define the link between two tables which similar func- tion to pointers in object oriented programming language. There are three ways of writing REF join queries which are: REF Join, Path Expression Join and DEREF/VALUE Join. In this paper, we study optimization technique for Object-Relational queries using hints. Hints are additional comments which are inserted into an SQL statement for the purpose of instructing or suggesting the optimizer to perform the specified operations. We utilize various hints including Optimizer hints, Table join and anti-join hints, and Access method hints. We analyse performance of various object-relation- al queries particularly in three ways of writing REF queries using the TRACE and TKPROF utilities which provide query execution statistics and exe- cution plans. Keywords: object-relational query optimization, ORBMS, REF 1. INTRODUCTION pointer to define the link between two tables (Taniar, Rahayu and Srivastava, 2003).
    [Show full text]
  • Mysql 5.7: Performance Improvements in Optimizer
    MySQL 5.7: Performance Improvements in Optimizer Olav Sandstå Senior Principal Engineer MySQL Optimizer Team, Oracle April 25, 2016 Copyright © 2016, Oracle and/or its affiliates. All rights reserved. Safe Harbor Statement The following is intended to outline our general product direction. It is intended for information purposes only, and may not be incorporated into any contract. It is not a commitment to deliver any material, code, or functionality, and should not be relied upon in making purchasing decisions. The development, release, and timing of any features or functionality described for Oracle’s products remains at the sole discretion of Oracle. Copyright © 2016, Oracle and/or its affiliates. All rights reserved. 2 Program Agenda 1 Improvements in optimizer • Cost model • New optimizations 2 Understanding query performance • Explain extensions • Optimizer trace 3 Tools for improving query plans • New hints • Query rewrite plugin Copyright © 2016, Oracle and/or its affiliates. All rights reserved. 3 MySQL Optimizer MySQL Server SELECT a, b Cost based JOIN FROM t1 optimizations JOIN t2 Table JOIN ON t1.a = t2.b Cost Model scan JOIN t3 Range Ref t1 ON t2.b = t3.c Parser scan access Optimizer Heuristics WHERE t2.d > 20 AND t2.d < 30; t2 t3 Table/index info Statistics (data dictionary) (storage engines) Copyright © 2016, Oracle and/or its affiliates. All rights reserved. 4 Optimizer Performance Improvements in MySQL 5.7 Cost model improvements: New optimizations: • Cost model for WHERE conditions • Merging of derived tables (condition filtering effect) • Optimization of IN queries – Improved JOIN order • Union ALL optimization • Improved index statistics – Better index selection, better join order • Configurable “cost constants” Copyright © 2016, Oracle and/or its affiliates.
    [Show full text]
  • Workbench-En.Pdf
    MySQL Workbench Abstract This is the MySQL Workbench Reference Manual. It documents the MySQL Workbench Community and MySQL Workbench Commercial releases for versions 8.0 through 8.0.26. If you have not yet installed the MySQL Workbench Community release, please download your free copy from the download site. The MySQL Workbench Community release is available for Microsoft Windows, macOS, and Linux. MySQL Workbench platform support evolves over time. For the latest platform support information, see https:// www.mysql.com/support/supportedplatforms/workbench.html. For notes detailing the changes in each release, see the MySQL Workbench Release Notes. For legal information, including licensing information, see the Preface and Legal Notices. For help with using MySQL, please visit the MySQL Forums, where you can discuss your issues with other MySQL users. Document generated on: 2021-10-01 (revision: 70942) Table of Contents Preface and Legal Notices ................................................................................................................ vii 1 General Information ......................................................................................................................... 1 1.1 What Is New in MySQL Workbench ...................................................................................... 1 1.1.1 New in MySQL Workbench 8.0 Release Series ........................................................... 1 1.1.2 New in MySQL Workbench 6.0 Release Series ..........................................................
    [Show full text]
  • SQL Server Execution Plans Second Edition by Grant Fritchey SQL Server Execution Plans
    SQL Handbooks SQL Server Execution Plans Second Edition By Grant Fritchey SQL Server Execution Plans Second Edition By Grant Fritchey Published by Simple Talk Publishing September 2012 First Edition 2008 Copyright Grant Fritchey 2012 ISBN: 978-1-906434-92-2 The right of Grant Fritchey to be identified as the author of this work has been asserted by him in accordance with the Copyright, Designs and Patents Act 1988 All rights reserved. No part of this publication may be reproduced, stored or introduced into a retrieval system, or transmitted, in any form, or by any means (electronic, mechanical, photocopying, recording or otherwise) without the prior written consent of the publisher. Any person who does any unauthorized act in relation to this publication may be liable to criminal prosecution and civil claims for damages. This book is sold subject to the condition that it shall not, by way of trade or otherwise, be lent, re-sold, hired out, or otherwise circulated without the publisher's prior consent in any form other than which it is published and without a similar condition including this condition being imposed on the subsequent publisher. Technical Reviewer: Brad McGehee Editors: Tony Davis and Brad McGehee Cover Image by Andy Martin Typeset by Peter Woodhouse & Gower Associates Table of Contents Introduction 13 Changes in This ___________________________________________ Second Edition 15 _________________________________________ Code Examples 16 _______________________________________________________ Chapter 1: Execution Plan Basics
    [Show full text]
  • The Query Optimizer in Oracle Database 19C What's New?
    The Query Optimizer in Oracle Database 19c What’s New? Christian Antognini @ChrisAntognini antognini.ch Christian Antognini • Senior principal consultant and partner at Trivadis • Focus: get the most out of database engines • Logical and physical database design • Query optimizer • Application performance management • Author of Troubleshooting Oracle Performance @ChrisAntognini antognini.ch Agenda • All Environments • Reporting on Hint Usage • Execution Plan Comparison Refer to the Oracle • Online Statistics Gathering Enhancements Database SQL Tuning Guide • Enterprise Edition with Management Packs for technical information • Statistics Maintenance Enhancements about the new features • Real-Time SQL Monitoring for Developers • Enterprise Edition on Exadata The Database Licensing • Automatic Resolution of Plan Regressions Information User Manual • High-Frequency SPM Evolve Advisor Task provides information about • Real-Time Statistics their availability • High-Frequency Automatic Statistics Collection • Quarantine for Runaway SQL Statements • Automatic Indexing Disclaimer • This presentation covers the versions 19.[3-5] • This presentation does not cover the query optimizer features that are specific to the Autonomous Database services All Environments Reporting on Hint Usage • It is an issue to verify whether hints added to SQL statements are actually used • To make it easier, there is a new section in the output generated by the DBMS_XPLAN.DISPLAY* functions • The new section (Hint Report) reports hints into two categories • Valid (used)
    [Show full text]
  • SAP HANA Performance Guide for Developers Company
    PUBLIC SAP HANA Platform 2.0 SPS 04 Document Version: 1.1 – 2019-10-31 SAP HANA Performance Guide for Developers company. All rights reserved. All rights company. affiliate THE BEST RUN 2019 SAP SE or an SAP SE or an SAP SAP 2019 © Content 1 SAP HANA Performance Guide for Developers......................................6 2 Disclaimer................................................................. 7 3 Schema Design..............................................................8 3.1 Choosing the Appropriate Table Type...............................................8 3.2 Creating Indexes..............................................................9 Primary Key Indexes........................................................10 Secondary Indexes.........................................................11 Multi-Column Index Types....................................................12 Costs Associated with Indexes.................................................13 When to Create Indexes..................................................... 14 3.3 Partitioning Tables............................................................15 3.4 Query Processing Examples.....................................................16 3.5 Delta Tables and Main Tables....................................................18 3.6 Denormalization.............................................................19 3.7 Additional Recommendations....................................................21 4 Query Execution Engine Overview...............................................22 4.1
    [Show full text]
  • Postgresql User's Guide
    PostgreSQL User's Guide The PostgreSQL Development Team Edited by Thomas Lockhart PostgreSQL User's Guide by The PostgreSQL Development Team Edited by Thomas Lockhart PostgreSQL is Copyright © 1996-2000 by PostgreSQL Inc. Table of Contents Table of Contents . i List of Tables . xiv List of Examples . xvi Summary. i Chapter 1. Introduction. 1 What is Postgres? . 1 A Short History of Postgres . 1 The Berkeley Postgres Project . 2 Postgres95. 2 PostgreSQL . 3 About This Release . 4 Resources. 4 Terminology . 5 Notation . 6 Problem Reporting Guidelines . 6 Identifying Bugs. 6 What to report . 7 Where to report bugs . 9 Y2K Statement . 9 Copyrights and Trademarks . 10 Chapter 2. SQL Syntax . 11 Key Words. 11 Reserved Key Words. 11 Non-reserved Keywords . 14 Comments . 15 Names. 16 Constants . 16 String Constants . 16 Integer Constants. 17 Floating Point Constants. 17 Constants of Postgres User-Defined Types . 17 Array constants . 18 Fields and Columns . 18 Fields. 18 Columns . 19 Operators. 19 Expressions . 19 Parameters . 20 Functional Expressions . 20 Aggregate Expressions . 20 Target List . 21 Qualification. 21 From List . 21 Chapter 3. Data Types . 23 Numeric Types . 25 The Serial Type . 26 Monetary Type . 26 Character Types . 27 Date/Time Types . 28 i Date/Time Input . 28 Date/Time Output . 33 Time Zones. 34 Internals . 34 Boolean Type. 35 Geometric Types . 35 Point . 36 Line Segment . 36 Box . 36 Path. 37 Polygon . 37 Circle . 38 IP Version 4 Networks and Host Addresses . 38 CIDR. 39 inet . 39 Chapter 4. Operators . ..
    [Show full text]
  • Infor Enterprise Server Technical Reference Guide for Oracle Database Driver Copyright © 2015 Infor
    Infor Enterprise Server Technical Reference Guide for Oracle Database Driver Copyright © 2015 Infor Important Notices The material contained in this publication (including any supplementary information) constitutes and contains confidential and proprietary information of Infor. By gaining access to the attached, you acknowledge and agree that the material (including any modification, translation or adaptation of the material) and all copyright, trade secrets and all other right, title and interest therein, are the sole property of Infor and that you shall not gain right, title or interest in the material (including any modification, translation or adaptation of the material) by virtue of your review thereof other than the non-exclusive right to use the material solely in connection with and the furtherance of your license and use of software made available to your company from Infor pursuant to a separate agreement, the terms of which separate agreement shall govern your use of this material and all supplemental related materials ("Purpose"). In addition, by accessing the enclosed material, you acknowledge and agree that you are required to maintain such material in strict confidence and that your use of such material is limited to the Purpose described above. Although Infor has taken due care to ensure that the material included in this publication is accurate and complete, Infor cannot warrant that the information contained in this publication is complete, does not contain typographical or other errors, or will meet your specific requirements. As such, Infor does not assume and hereby disclaims all liability, consequential or otherwise, for any loss or damage to any person or entity which is caused by or relates to errors or omissions in this publication (including any supplementary information), whether such errors or omissions result from negligence, accident or any other cause.
    [Show full text]
  • The Use of Hints in Sql-Nested Query Optimization
    Journal of Data Mining and Knowledge Discovery ISSN: 2229–6662 & ISSN: 2229–6670, Volume 3, Issue 1, 2012, pp.-54-57. Available online at http://www. bioinfo. in/contents. php?id=42 THE USE OF HINTS IN SQL-NESTED QUERY OPTIMIZATION LOKHANDE A.D. AND SHETE R.M. M. E Computer Science and Engineering Dept., Sipna C. O. E. T. Amravati, MS, India. *Corresponding Author: Email- [email protected] and [email protected] Received: February 21, 2012; Accepted: March 15, 2012 Abstract- The query optimization phase in query processing plays a crucial role in choosing the most efficient strategy for executing a que- ry. In this paper, we study an optimization technique for SQL-Nested queries using Hints. Hints are additional comments that are inserted into an SQL statement for the purpose of instructing the optimizer to perform the specified operations. We utilize various Hints including Optimizer Hints, Table join and anti-join Hints, and Access method Hints. We analyse the performance of various nested queries using the TRACE and TKPROF utilities which provide query execution statistics and execution plan. Keywords- Hint, query optimization, parsing. Citation: Lokhande A.D. and Shete R.M. (2012) The use of Hints in SQL-Nested query optimization. Journal of Data Mining and Knowledge Discovery, ISSN: 2229–6662 & ISSN: 2229–6670, Volume 3, Issue 1, pp.-54-57. Copyright: Copyright©2012 Lokhande A.D. and Shete R.M. This is an open-access article distributed under the terms of the Creative Com- mons Attribution License, which permits unrestricted use, distribution, and reproduction in any medium, provided the original author and source are credited.
    [Show full text]
  • Bao: Learning to Steer Query Optimizers
    Bao: Learning to Steer Query Optimizers Ryan Marcus12, Parimarjan Negi1, Hongzi Mao1, Nesime Tatbul12, Mohammad Alizadeh1, Tim Kraska1 1MIT CSAIL 2Intel Labs fryanmarcus, pnegi, hongzi, tatbul, alizadeh, [email protected] ABSTRACT 60.2s PostgreSQL Query optimization remains one of the most challenging 60 PostgreSQL (no loop join) problems in data management systems. Recent efforts to apply machine learning techniques to query optimization 40 challenges have been promising, but have shown few prac- tical gains due to substantive training overhead, inability 21.2s to adapt to changes, and poor tail performance. Motivated 20 19.7s by these difficulties and drawing upon a long history of re- search in multi-armed bandits, we introduce Bao (the Bandit 0.4s optimizer). Bao takes advantage of the wisdom built into Query latency (seconds) 0 existing query optimizers by providing per-query optimiza- 16b 24b tion hints. Bao combines modern tree convolutional neu- JOB Query ral networks with Thompson sampling, a decades-old and well-studied reinforcement learning algorithm. As a result, Figure 1: Disabling the loop join operator in PostgreSQL Bao automatically learns from its mistakes and adapts to can improve (16b) or harm (24b) a particular query's per- changes in query workloads, data, and schema. Experimen- formance. These example queries are from the Join Order tally, we demonstrate that Bao can quickly (an order of mag- Benchmark (JOB) [30]. nitude faster than previous approaches) learn strategies that improve end-to-end query execution performance, including tail latency. In cloud environments, we show that Bao can 2. Brittleness. While performing expensive training oper- offer both reduced costs and better performance compared ations once may already be impractical, changes in query with a sophisticated commercial system.
    [Show full text]