DOCSLIB.ORG

Sql Server to Aurora Mysql Migration Playbook

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Sql Server to Aurora Mysql Migration Playbook Microsoft SQL Server To Amazon Aurora with MySQL Compatibility Migration Playbook Version 1.8, September 2018 © 2018 Amazon Web Services, Inc. or its affiliates. All rights reserved. Notices This document is provided for informational purposes only. It represents AWS’s current product offer- ings and practices as of the date of issue of this document, which are subject to change without notice. Customers are responsible for making their own independent assessment of the information in this document and any use of AWS’s products or services, each of which is provided “as is” without war- ranty of any kind, whether express or implied. This document does not create any warranties, rep- resentations, contractual commitments, conditions or assurances from AWS, its affiliates, suppliers or licensors. The responsibilities and liabilities of AWS to its customers are controlled by AWS agree- ments, and this document is not part of, nor does it modify, any agreement between AWS and its cus- tomers. - 2 - Table of Contents Introduction 8 Tables of Feature Compatibility 11 AWS Schema and Data Migration Tools 23 AWS Schema Conversion Tool (SCT) 24 SCT Action Code Index 38 AWS Database Migration Service (DMS) 54 ANSI SQL 57 Migrate from SQL Server Constraints 58 Migrate to Aurora MySQL Constraints 62 Migrate from SQL Server Creating Tables 67 Migrate to Aurora MySQL Creating Tables 71 Migrate from SQL Server Common Table Expressions 77 Migrate to Aurora MySQL Common Table Expressions 80 Migrate from SQL Server Data Types 84 Migrate to Aurora MySQL Data Types 86 Migrate from SQL Server GROUP BY 96 Migrate to Aurora MySQL GROUP BY 100 Migrate from SQL Server Table JOIN 105 Migrate to Aurora MySQL Table JOIN 110 Migrate from SQL Server Views 114 Migrate to Aurora MySQL Views 117 Migrate from SQL Server Window Functions 122 Migrate to Aurora MySQL Window Functions 125 T-SQL 128 Migrate from SQL Server Collations 129 Migrate to Aurora MySQL Collations 132 Migrate from SQL Server Cursors 141 Migrate to Aurora MySQL Cursors 143 - 3 - Migrate from SQL Server Date and Time Functions 148 Migrate to Aurora MySQL Date and Time Functions 150 Migrate from SQL Server String Functions 153 Migrate to Aurora MySQL String Functions 156 Migrate from SQL Server Databases and Schemas 160 Migrate to Aurora MySQL Databases and Schemas 163 Migrate from SQL Server Transactions 166 Migrate to Aurora MySQL Transactions 170 Migrate from SQL Server DELETE and UPDATE FROM 174 Migrate to Aurora MySQL DELETE and UPDATE FROM 177 Migrate from SQL Server Stored Procedures 180 Migrate to Aurora MySQL Stored Procedures 184 Migrate from SQL Server Error Handling 189 Migrate to Aurora MySQL Error Handling 193 Migrate from SQL Server Flow Control 199 Migrate to Aurora MySQL Flow Control 202 Migrate from SQL Server Full-Text Search 207 Migrate to Aurora MySQL Full-Text Search 211 Migrate from SQL Server JSON and XML 216 Migrate to Aurora MySQL JSON and XML 219 Migrate from SQL Server MERGE 223 Migrate to Aurora MySQL MERGE 226 Migrate from SQL Server PIVOT and UNPIVOT 231 Migrate to Aurora MySQL PIVOT and UNPIVOT 235 Migrate from SQL Server Synonyms 238 Migrate to Aurora MySQL Synonyms 240 Migrate from SQL Server TOP and FETCH 241 Migrate to Aurora MySQL LIMIT (TOP and FETCH Equivalent) 244 Migrate from SQL Server Triggers 247 Migrate to Aurora MySQL Triggers 250 - 4 - Migrate from SQL Server User Defined Functions 254 Migrate to Aurora MySQL User Defined Functions 257 Migrate from SQL Server User Defined Types 260 Migrate to Aurora MySQL User Defined Types 263 Migrate from SQL Server Sequences and Identity 266 Migrate to Aurora MySQL Sequences and Identity 271 Migrate from SQL Server Managing Statistics 276 Migrate to Aurora MySQL Managing Statistics 278 Configuration 281 Migrate from SQL Server Session Options 282 Migrate to Aurora MySQL Session Options 285 Migrate from SQL Server Database Options 289 Migrate to Aurora MySQL Database Options 290 Migrate from SQL Server Server Options 291 Migrate to Aurora MySQL Server Options 293 High Availability and Disaster Recovery (HADR) 296 Migrate from SQL Server Backup and Restore 297 Migrate to Aurora MySQL Backup and Restore 301 Migrate from SQL Server High Availability Essentials 309 Migrate to Aurora MySQL High Availability Essentials 313 Indexes 322 Migrate from SQL Server Clustered and Non Clustered Indexes 323 Migrate to Aurora MySQL Clustered and Non Clustered Indexes 327 Management 331 Migrate from SQL Server SQL Server Agent 332 Migrate to Aurora MySQL Agent 333 Migrate from SQL Server Alerting 336 Migrate to Aurora MySQL Alerting 338 Migrate from SQL Server Database Mail 342 Migrate to Aurora MySQL Database Mail 345 - 5 - Migrate from SQL Server ETL 346 Migrate to Aurora MySQL ETL 348 Migrate from SQL Server Viewing Server Logs 374 Migrate to Aurora MySQL Viewing Server Logs 376 Migrate from SQL Server Maintenance Plans 379 Migrate to Aurora MySQL Maintenance Plans 382 Migrate from SQL Server Monitoring 388 Migrate to Aurora MySQL Monitoring 391 Migrate from SQL Server Resource Governor 392 Migrate to Aurora MySQL Resource Governor 394 Migrate from SQL Server Linked Servers 396 Migrate to Aurora MySQL Linked Servers 399 Migrate from SQL Server Scripting 400 Migrate to Aurora MySQL Scripting 402 Performance Tuning 407 Migrate from SQL Server Execution Plans 408 Migrate to Aurora MySQL Execution Plans 410 Migrate from SQL Server Query Hints and Plan Guides 412 Migrate to Aurora MySQL Query Hints and Plan Guides 415 Physical Storage 419 Migrate from SQL Server Partitioning 420 Migrate to Aurora MySQL Partitioning 422 Security 428 Migrate from SQL Server Column Encryption 429 Migrate to Aurora MySQL Column Encryption 431 Migrate from SQL Server Data Control Language 433 Migrate to Aurora MySQL Data Control Language 434 Migrate from SQL Server Transparent Data Encryption 437 Migrate to Aurora MySQL Transparent Data Encryption 438 Migrate from SQL Server Users and Roles 443 - 6 - Migrate to Aurora MySQL Users and Roles 445 Appendix A: SQL Server 2018 Deprecated Feature List 448 Appendix B: Migration Quick Tips 449 Management 449 SQL 449 Glossary 453 - 7 - Introduction The migration process from SQL Server to Amazon Aurora MySQL typically involves several stages. The first stage is to use the AWS Schema Conversion Tool (SCT) and the AWS Database Migration Service (DMS) to convert and migrate the schema and data. While most of the migration work can be auto- mated, some aspects require manual intervention and adjustments to both database schema objects and database code. The purpose of this Playbook is to assist administrators tasked with migrating SQL Server databases to Aurora MySQL with the aspects that can't be automatically migrated using the Amazon Web Services Schema Conversion Tool (AWS SCT). It focuses on the differences, incompatibilities, and similarities between SQL Server and Aurora MySQL in a wide range of topics including T-SQL, Configuration, High Availability and Disaster Recovery (HADR), Indexing, Management, Performance Tuning, Security, and Physical Storage. The first section of this document provides an overview of AWS SCT and the AWS Data Migration Ser- vice (DMS) tools for automating the migration of schema, objects and data. The remainder of the doc- ument contains individual sections for SQL Server features and their Aurora MySQL counterparts. Each section provides a short overview of the feature, examples, and potential workaround solutions for incompatibilities. You can use this playbook either as a reference to investigate the individual action codes generated by the AWS SCT tool, or to explore a variety of topics where you expect to have some incompatibility issues. When using the AWS SCT, you may see a report that lists Action codes , which indicates some manual conversion is required, or that a manual verification is recommended. For your convenience, this Playbook includes an SCT Action Code Index section providing direct links to the relevant topics that discuss the manual conversion tasks needed to address these action codes. Alternatively, you can explore the Tables of Feature Compatibility section that provides high-level graphical indicators and descriptions of the feature compatibility between SQL Server and Aurora MySQL. It also includes a graphical compatibility indicator and links to the actual sections in the playbook. There are two appendices at the end of this playbook: Appendix A: SQL Server 2008 Deprecated Feature List provides focused links on features that were deprecated in SQL Server 2008R2. Appendix B: Migration Quick Tips provides a list of tips for SQL Server administrators or developers who have little experience with MySQL. It briefly highlights key differences between SQL Server and Aurora MySQL that they are likely to encounter. - 8 - Note that not all SQL Server features are fully compatible with Aurora MySQL, or have simple work- arounds. From a migration perspective, this document does not yet cover all SQL Server features and capabilities. This first release focuses on some of the most important features and will be expanded over time. - 9 - Disclaimer The various code snippets, commands, guides, best practices, and scripts included in this document should be used for reference only and are provided as-is without warranty. Test all of the code, com- mands, best practices, and scripts outlined in this document in a non-production environment first. Amazon and its affiliates are not responsible for any direct or indirect damage that may occur from the information contained
Load more

Recommended publications
  • RDBMS in the Cloud: Deploying SQL Server on AWS
    RDBMS in the Cloud: Deploying SQL Server on AWS Darryl Osborne Vlad Vlasceanu June 2015 Amazon Web Services – RDBMS in the Cloud: Deploying SQL Server on AWS May 2015 © 2015, Amazon Web Services, Inc. or its affiliates. All rights reserved. Notices This document is provided for informational purposes only. It represents AWS’s current product offerings and practices as of the date of issue of this document, which are subject to change without notice. Customers are responsible for making their own independent assessment of the information in this document and any use of AWS’s products or services, each of which is provided “as is” without warranty of any kind, whether express or implied. This document does not create any warranties, representations, contractual commitments, conditions or assurances from AWS, its affiliates, suppliers or licensors. The responsibilities and liabilities of AWS to its customers are controlled by AWS agreements, and this document is not part of, nor does it modify, any agreement between AWS and its customers. Page 2 of 67 Amazon Web Services – RDBMS in the Cloud: Deploying SQL Server on AWS May 2015 Contents Abstract 5 SQL Server Solutions on AWS 6 Amazon RDS for SQL Server 6 SQL Server on Amazon EC2 6 Hybrid Scenarios 7 Choosing between SQL Server Solutions on AWS 7 Amazon RDS for SQL Server 9 Starting a Microsoft SQL Server RDS Instance 11 Security 15 Performance Management 19 High Availability 26 Monitoring and Management 27 Managing Cost 30 SQL Server on Amazon EC2 33 Starting a Microsoft SQL Server Instance 33 Security 38 Performance Management 40 High Availability 44 Monitoring and Management 48 Managing Cost 49 Caching 52 Hybrid Scenarios 53 Backups to the Cloud 53 SQL Server Log Shipping – Between On-Premises and Amazon EC2 57 Page 3 of 67 Amazon Web Services – RDBMS in the Cloud: Deploying SQL Server on AWS May 2015 SQL Server AlwaysOn Availability Groups – Between On-Premises and Amazon EC2 58 Amazon RDS Migration Tool 59 Conclusion 60 Further Reading 61 Appendix 62 I.
    [Show full text]
  • Aptum Database Administration Program September 2019 Overview
    SERVICE GUIDE APTUM DATABASE ADMINISTRATION PROGRAM SEPTEMBER 2019 OVERVIEW Aptum’s Database Administration (DBA) Program was designed to DBA Plan hours can be leveraged for all database-related activities help our customers reduce the cost of normal operation and the risk of detailed within this document, up to the allocation purchased. If you application and database downtime. require more hours than are purchased in a plan for a given month, any excess will be billed on an hourly basis at the standard Database Customers can work with Aptum’s Solutions Engineers and Certified Administration rate. Database Administrators to obtain assistance with everything from database engine configuration, performance optimization, clustering Included Database Platforms: administration, and replication administration. Microsoft SQL Server To help you achieve your performance goals, we offer our DBA plans in MySQL/MariaDB/Percona block-hour increments: 4 hours* * Hours are monthly and renew at the 1st of each calendar month and do not roll over. Overage rates are applicable only after block hours are consumed. All hours are 8 hours* applicable to the entire solution not per server. 12 hours* 20 hours* THE NEED FOR DATABASE ADMINISTRATION Most applications—especially those that support enterprise processes enable e-commerce, or facilitate collaboration—are database-intensive and demand optimal performance from the database. Applications and database queries may utilize very lean and elegant code, but the structure and configuration of your databases can be a detriment to high performance. There are dozens, sometimes hundreds, of configuration settings that need to be optimally tuned to enhance database performance. When the database is installed, most configuration defaults are applied automatically.
    [Show full text]
  • Schema in Database Sql Server
    Schema In Database Sql Server Normie waff her Creon stringendo, she ratten it compunctiously. If Afric or rostrate Jerrie usually files his terrenes shrives wordily or supernaturalized plenarily and quiet, how undistinguished is Sheffy? Warring and Mahdi Morry always roquet impenetrably and barbarizes his boskage. Schema compare tables just how the sys is a table continues to the most out longer function because of the connector will often want to. Roles namely actors in designer slow and target multiple teams together, so forth from sql management. You in sql server, should give you can learn, and execute this is a location of users: a database projects, or more than in. Your sql is that the view to view of my data sources with the correct. Dive into the host, which objects such a set of lock a server database schema in sql server instance of tables under the need? While viewing data in sql server database to use of microseconds past midnight. Is sql server is sql schema database server in normal circumstances but it to use. You effectively structure of the sql database objects have used to it allows our policy via js. Represents table schema in comparing new database. Dml statement as schema in database sql server functions, and so here! More in sql server books online schema of the database operator with sql server connector are not a new york, with that object you will need. This in schemas and history topic names are used to assist reporting from. Sql schema table as views should clarify log reading from synonyms in advance so that is to add this game reports are.
    [Show full text]
  • Sql Create Table Variable from Select
    Sql Create Table Variable From Select Do-nothing Dory resurrect, his incurvature distasting crows satanically. Sacrilegious and bushwhacking Jamey homologising, but Harcourt first-hand coiffures her muntjac. Intertarsal and crawlier Towney fanes tenfold and euhemerizing his assistance briskly and terrifyingly. How to clean starting value inside of data from select statements and where to use matlab compiler to store sql, and then a regular join You may not supported for that you are either hive temporary variable table. Before we examine the specific methods let's create an obscure procedure. INSERT INTO EXEC sql server exec into table. Now you can show insert update delete and invent all operations with building such as in pay following a write i like the Declare TempTable. When done use t or t or when to compact a table variable t. Procedure should create the temporary tables instead has regular tables. Lesson 4 Creating Tables SQLCourse. EXISTS tmp GO round TABLE tmp id int NULL SELECT empire FROM. SQL Server How small Create a Temp Table with Dynamic. When done look sir the Execution Plan save the SELECT Statement SQL Server is. Proc sql create whole health will select weight married from myliboutdata ORDER to weight ASC. How to add static value while INSERT INTO with cinnamon in a. Ssrs invalid object name temp table. Introduction to Table Variable Deferred Compilation SQL. How many pass the bash array in 'right IN' clause will select query. Creating a pope from public Query Vertica. Thus attitude is no performance cost for packaging a SELECT statement into an inline.
    [Show full text]
  • Support Aggregate Analytic Window Function Over Large Data by Spilling
    Support Aggregate Analytic Window Function over Large Data by Spilling Xing Shi and Chao Wang Guangdong University of Technology, Guangzhou, Guangdong 510006, China North China University of Technology, Beijing 100144, China Abstract. ​Analytic function, also called window function, is to query the aggregation of data over a sliding window. For example, a simple query over the online stock platform is to return the average price of a stock of the last three days. These functions are commonly used features in SQL databases. They are supported in most of the commercial databases. With the increasing usage of cloud data infra and machine learning technology, the frequency of queries with analytic window functions rises. Some analytic functions only require const space in memory to store the state, such as SUM, AVG, while others require linear space, such as MIN, MAX. When the window is extremely large, the memory space to store the state may be too large. In this case, we need to spill the state to disk, which is a heavy operation. In this paper, we proposed an algorithm to manipulate the state data in the disk to reduce the disk I/O to make spill available and efficiency. We analyze the complexity of the algorithm with different data distribution. 1. Introducion In this paper, we develop novel spill techniques for analytic window function in SQL databases. And discuss different various types of aggregate queries, e.g., COUNT, AVG, SUM, MAX, MIN, etc., over a relational table. Aggregate ​analytic function, also called aggregate window function, is to query the aggregation of data over a sliding window.
    [Show full text]
  • Exploiting Fuzzy-SQL in Case-Based Reasoning
    Exploiting Fuzzy-SQL in Case-Based Reasoning Luigi Portinale and Andrea Verrua Dipartimentodi Scienze e Tecnoiogie Avanzate(DISTA) Universita’ del PiemonteOrientale "AmedeoAvogadro" C.so Borsalino 54 - 15100Alessandria (ITALY) e-mail: portinal @mfn.unipmn.it Abstract similarity-basedretrieval is the fundamentalstep that allows one to start with a set of relevant cases (e.g. the mostrele- The use of database technologies for implementingCBR techniquesis attractinga lot of attentionfor severalreasons. vant products in e-commerce),in order to apply any needed First, the possibility of usingstandard DBMS for storing and revision and/or refinement. representingcases significantly reduces the effort neededto Case retrieval algorithms usually focus on implement- developa CBRsystem; in fact, data of interest are usually ing Nearest-Neighbor(NN) techniques, where local simi- alreadystored into relational databasesand used for differ- larity metrics relative to single features are combinedin a ent purposesas well. Finally, the use of standardquery lan- weightedway to get a global similarity betweena retrieved guages,like SQL,may facilitate the introductionof a case- and a target case. In (Burkhard1998), it is arguedthat the basedsystem into the real-world,by puttingretrieval on the notion of acceptancemay represent the needs of a flexible sameground of normaldatabase queries. Unfortunately,SQL case retrieval methodologybetter than distance (or similar- is not able to deal with queries like those neededin a CBR ity). Asfor distance, local acceptancefunctions can be com- system,so different approacheshave been tried, in orderto buildretrieval engines able to exploit,at thelower level, stan- bined into global acceptancefunctions to determinewhether dard SQL.In this paper, wepresent a proposalwhere case a target case is acceptable(i.e.
    [Show full text]
  • A First Attempt to Computing Generic Set Partitions: Delegation to an SQL Query Engine Frédéric Dumonceaux, Guillaume Raschia, Marc Gelgon
    A First Attempt to Computing Generic Set Partitions: Delegation to an SQL Query Engine Frédéric Dumonceaux, Guillaume Raschia, Marc Gelgon To cite this version: Frédéric Dumonceaux, Guillaume Raschia, Marc Gelgon. A First Attempt to Computing Generic Set Partitions: Delegation to an SQL Query Engine. DEXA’2014 (Database and Expert System Applications), Sep 2014, Munich, Germany. pp.433-440. hal-00993260 HAL Id: hal-00993260 https://hal.archives-ouvertes.fr/hal-00993260 Submitted on 28 Oct 2014 HAL is a multi-disciplinary open access L’archive ouverte pluridisciplinaire HAL, est archive for the deposit and dissemination of sci- destinée au dépôt et à la diffusion de documents entific research documents, whether they are pub- scientifiques de niveau recherche, publiés ou non, lished or not. The documents may come from émanant des établissements d’enseignement et de teaching and research institutions in France or recherche français ou étrangers, des laboratoires abroad, or from public or private research centers. publics ou privés. A First Attempt to Computing Generic Set Partitions: Delegation to an SQL Query Engine Fr´ed´ericDumonceaux, Guillaume Raschia, and Marc Gelgon LINA (UMR CNRS 6241), Universit´ede Nantes, France [email protected] Abstract. Partitions are a very common and useful way of organiz- ing data, in data engineering and data mining. However, partitions cur- rently lack efficient and generic data management functionalities. This paper proposes advances in the understanding of this problem, as well as elements for solving it. We formulate the task as efficient process- ing, evaluating and optimizing queries over set partitions, in the setting of relational databases.
    [Show full text]
  • Look out the Window Functions and Free Your SQL
    Concepts Syntax Other Look Out The Window Functions and free your SQL Gianni Ciolli 2ndQuadrant Italia PostgreSQL Conference Europe 2011 October 18-21, Amsterdam Look Out The Window Functions Gianni Ciolli Concepts Syntax Other Outline 1 Concepts Aggregates Different aggregations Partitions Window frames 2 Syntax Frames from 9.0 Frames in 8.4 3 Other A larger example Question time Look Out The Window Functions Gianni Ciolli Concepts Syntax Other Aggregates Aggregates 1 Example of an aggregate Problem 1 How many rows there are in table a? Solution SELECT count(*) FROM a; • Here count is an aggregate function (SQL keyword AGGREGATE). Look Out The Window Functions Gianni Ciolli Concepts Syntax Other Aggregates Aggregates 2 Functions and Aggregates • FUNCTIONs: • input: one row • output: either one row or a set of rows: • AGGREGATEs: • input: a set of rows • output: one row Look Out The Window Functions Gianni Ciolli Concepts Syntax Other Different aggregations Different aggregations 1 Without window functions, and with them GROUP BY col1, . , coln window functions any supported only PostgreSQL PostgreSQL version version 8.4+ compute aggregates compute aggregates via by creating groups partitions and window frames output is one row output is one row for each group for each input row Look Out The Window Functions Gianni Ciolli Concepts Syntax Other Different aggregations Different aggregations 2 Without window functions, and with them GROUP BY col1, . , coln window functions only one way of aggregating different rows in the same for each group
    [Show full text]
  • Lecture 3: Advanced SQL
    Advanced SQL Lecture 3: Advanced SQL 1 / 64 Advanced SQL Relational Language Relational Language • User only needs to specify the answer that they want, not how to compute it. • The DBMS is responsible for efficient evaluation of the query. I Query optimizer: re-orders operations and generates query plan 2 / 64 Advanced SQL Relational Language SQL History • Originally “SEQUEL" from IBM’s System R prototype. I Structured English Query Language I Adopted by Oracle in the 1970s. I IBM releases DB2 in 1983. I ANSI Standard in 1986. ISO in 1987 I Structured Query Language 3 / 64 Advanced SQL Relational Language SQL History • Current standard is SQL:2016 I SQL:2016 −! JSON, Polymorphic tables I SQL:2011 −! Temporal DBs, Pipelined DML I SQL:2008 −! TRUNCATE, Fancy sorting I SQL:2003 −! XML, windows, sequences, auto-gen IDs. I SQL:1999 −! Regex, triggers, OO • Most DBMSs at least support SQL-92 • Comparison of different SQL implementations 4 / 64 Advanced SQL Relational Language Relational Language • Data Manipulation Language (DML) • Data Definition Language (DDL) • Data Control Language (DCL) • Also includes: I View definition I Integrity & Referential Constraints I Transactions • Important: SQL is based on bag semantics (duplicates) not set semantics (no duplicates). 5 / 64 Advanced SQL Relational Language Today’s Agenda • Aggregations + Group By • String / Date / Time Operations • Output Control + Redirection • Nested Queries • Join • Common Table Expressions • Window Functions 6 / 64 Advanced SQL Relational Language Example Database SQL Fiddle: Link sid name login age gpa sid cid grade 1 Maria maria@cs 19 3.8 1 1 B students 2 Rahul rahul@cs 22 3.5 enrolled 1 2 A 3 Shiyi shiyi@cs 26 3.7 2 3 B 4 Peter peter@ece 35 3.8 4 2 C cid name 1 Computer Architecture courses 2 Machine Learning 3 Database Systems 4 Programming Languages 7 / 64 Advanced SQL Aggregates Aggregates • Functions that return a single value from a bag of tuples: I AVG(col)−! Return the average col value.
    [Show full text]
  • Sql Server to Aurora Postgresql Migration Playbook
    Microsoft SQL Server To Amazon Aurora with Post- greSQL Compatibility Migration Playbook 1.0 Preliminary September 2018 © 2018 Amazon Web Services, Inc. or its affiliates. All rights reserved. Notices This document is provided for informational purposes only. It represents AWS’s current product offer- ings and practices as of the date of issue of this document, which are subject to change without notice. Customers are responsible for making their own independent assessment of the information in this document and any use of AWS’s products or services, each of which is provided “as is” without war- ranty of any kind, whether express or implied. This document does not create any warranties, rep- resentations, contractual commitments, conditions or assurances from AWS, its affiliates, suppliers or licensors. The responsibilities and liabilities of AWS to its customers are controlled by AWS agree- ments, and this document is not part of, nor does it modify, any agreement between AWS and its cus- tomers. - 2 - Table of Contents Introduction 9 Tables of Feature Compatibility 12 AWS Schema and Data Migration Tools 20 AWS Schema Conversion Tool (SCT) 21 Overview 21 Migrating a Database 21 SCT Action Code Index 31 Creating Tables 32 Data Types 32 Collations 33 PIVOT and UNPIVOT 33 TOP and FETCH 34 Cursors 34 Flow Control 35 Transaction Isolation 35 Stored Procedures 36 Triggers 36 MERGE 37 Query hints and plan guides 37 Full Text Search 38 Indexes 38 Partitioning 39 Backup 40 SQL Server Mail 40 SQL Server Agent 41 Service Broker 41 XML 42 Constraints
    [Show full text]
  • Firebird 3 Windowing Functions
    Firebird 3 Windowing Functions Firebird 3 Windowing Functions Author: Philippe Makowski IBPhoenix Email: pmakowski@ibphoenix Licence: Public Documentation License Date: 2011-11-22 Philippe Makowski - IBPhoenix - 2011-11-22 Firebird 3 Windowing Functions What are Windowing Functions? • Similar to classical aggregates but does more! • Provides access to set of rows from the current row • Introduced SQL:2003 and more detail in SQL:2008 • Supported by PostgreSQL, Oracle, SQL Server, Sybase and DB2 • Used in OLAP mainly but also useful in OLTP • Analysis and reporting by rankings, cumulative aggregates Philippe Makowski - IBPhoenix - 2011-11-22 Firebird 3 Windowing Functions Windowed Table Functions • Windowed table function • operates on a window of a table • returns a value for every row in that window • the value is calculated by taking into consideration values from the set of rows in that window • 8 new windowed table functions • In addition, old aggregate functions can also be used as windowed table functions • Allows calculation of moving and cumulative aggregate values. Philippe Makowski - IBPhoenix - 2011-11-22 Firebird 3 Windowing Functions A Window • Represents set of rows that is used to compute additionnal attributes • Based on three main concepts • partition • specified by PARTITION BY clause in OVER() • Allows to subdivide the table, much like GROUP BY clause • Without a PARTITION BY clause, the whole table is in a single partition • order • defines an order with a partition • may contain multiple order items • Each item includes
    [Show full text]
  • Using the Set Operators Questions
    UUSSIINNGG TTHHEE SSEETT OOPPEERRAATTOORRSS QQUUEESSTTIIOONNSS http://www.tutorialspoint.com/sql_certificate/using_the_set_operators_questions.htm Copyright © tutorialspoint.com 1.Which SET operator does the following figure indicate? A. UNION B. UNION ALL C. INTERSECT D. MINUS Answer: A. Set operators are used to combine the results of two ormore SELECT statements.Valid set operators in Oracle 11g are UNION, UNION ALL, INTERSECT, and MINUS. When used with two SELECT statements, the UNION set operator returns the results of both queries.However,if there are any duplicates, they are removed, and the duplicated record is listed only once.To include duplicates in the results,use the UNION ALL set operator.INTERSECT lists only records that are returned by both queries; the MINUS set operator removes the second query's results from the output if they are also found in the first query's results. INTERSECT and MINUS set operations produce unduplicated results. 2.Which SET operator does the following figure indicate? A. UNION B. UNION ALL C. INTERSECT D. MINUS Answer: B. UNION ALL Returns the combined rows from two queries without sorting or removing duplicates. sql_certificate 3.Which SET operator does the following figure indicate? A. UNION B. UNION ALL C. INTERSECT D. MINUS Answer: C. INTERSECT Returns only the rows that occur in both queries' result sets, sorting them and removing duplicates. 4.Which SET operator does the following figure indicate? A. UNION B. UNION ALL C. INTERSECT D. MINUS Answer: D. MINUS Returns only the rows in the first result set that do not appear in the second result set, sorting them and removing duplicates.
    [Show full text]