Mysql Standard Edition Mysql Enterprise Edition Mysql Cluster

Total Page：16

File Type：pdf, Size：1020Kb

Mysql Standard Edition Mysql Enterprise Edition Mysql Cluster

MySQL MySQL MySQL Standard Enterprise Cluster Edition Edition CGE Annual Subscription2,3,4,5 USD 2,000 USD 5,000 USD 10,000 /1-4 Socket Server /Year Oracle Premier Support3 24x7 Support Yes Yes Yes Unlimited Support Incidents Yes Yes Yes Knowledge Base Yes Yes Yes Maintenance Releases, Bug Fixes, Yes Yes Yes Patches, Updates MySQL Consultative Support Yes Yes Yes MySQL Features MySQL Database Server Yes Yes Yes MySQL Connectors Yes Yes Yes MySQL Replication Yes Yes Yes MySQL Router Yes Yes MySQL Partitioning Yes Yes MySQL Utilities Yes Yes 1 MySQL Workbench Yes Yes Yes Storage Engine: MyISAM Yes Yes Yes Storage Engine: InnoDB Yes Yes Yes Storage Engine: NDB Yes 1 Oracle Enterprise Manager for MySQL Yes Yes 1 MySQL Enterprise Monitor Yes Yes - MySQL Enterprise Dashboard1 Yes Yes - MySQL Enterprise Advisors1 Yes Yes - MySQL Query Analyzer1 Yes Yes 1 - MySQL Replication Monitor Yes Yes 1 MySQL Enterprise Backup Yes Yes - Hot backup for InnoDB1 Yes Yes - Full, Incremental, Partial backup1 Yes Yes - Full, Partial restore1 Yes Yes 1 - Point-In-Time-Recovery Yes Yes 1 MySQL Enterprise Security Yes Yes 1 - External Authentication Yes Yes 1 MySQL Enterprise TDE Yes Yes 1 - Transparent Data Encryption Yes Yes 1 MySQL Enterprise Encryption Yes Yes 1 - Asymmetric Encryption Yes Yes 1 MySQL Enterprise Firewall Yes Yes - Block SQL Injection Attacks1 Yes Yes - Intrusion Detection1 Yes Yes 1 MySQL Enterprise Audit Yes Yes 1 - Policy-based auditing compliance Yes Yes 1 MySQL Enterprise Scalability Yes Yes 1 - Thread Pool Yes Yes 1 MySQL Enterprise High-Availability Yes Yes - MySQL InnoDB Cluster Yes Yes - MySQL Group Replication Yes Yes 1 MySQL Cluster Manager Yes - Configuration & Provisioning1 Yes - Automatic Scaling1 Yes - Management & Monitoring1 Yes MySQL Cluster Geo-Replication Yes Oracle Product Certifications6 6 Certified with Oracle Linux Yes Yes Yes 6 Certified with Oracle VM Yes Yes Yes 6 Certified with Oracle Solaris Yes Yes Yes 6 Certified with Oracle GoldenGate Yes Yes Certified with Oracle Data Integrator Yes Yes 6 Certified with Oracle Fusion Middleware Yes Yes 6 Certified with Oracle Secure Backup Yes Yes Certified with Oracle Audit Vault and Yes Yes Database Firewall6 1 Features are only available in Commercial Editions 2 Annual Subscription 3 Oracle Premier Support for MySQL is included in Annual Subscriptions (no extra cost) 4 Server: is defined as the computer on which the programs are installed. A Server license allows you to use the licensed program on a single specified computer. 5 Socket: is defined as a slot that houses a chip (or a multi-chip module), which contains a collection of one or more cores. Regardless of the number of cores, each chip (or multi-chip module) counts as a single socket. All occupied sockets on which the Oracle program is installed and/or running must be licensed. 6 Non-MySQL products not included (can be purchased separately) Pricing is "per Server", for 2 classes: Servers with 1-4 Sockets, and Servers with 5+ Sockets For pricing for 5+ Socket Servers, contact the MySQL Sales Team ISVs, OEMs and VARs can learn more about MySQL as an Embedded Database. .

Copy Link

Recommended publications

Mysql Replication Tutorial
MySQL Replication Tutorial Lars Thalmann Technical lead Replication, Backup, and Engine Technology Mats Kindahl Lead Developer Replication Technology MySQL Conference and Expo 2008 Concepts 3 MySQL Replication Why? How? 1. High Availability Snapshots (Backup) Possibility of fail-over 1. Client program mysqldump 2. Load-balancing/Scale- With log coordinates out 2. Using backup Query multiple servers InnoDB, NDB 3. Off-site processing Don’t disturb master Binary log 1. Replication Asynchronous pushing to slave 2. Point-in-time recovery Roll-forward Terminology Master MySQL Server • Changes data • Has binlog turned on Master • Pushes binlog events to slave after slave has requested them MySQL Server Slave MySQL Server • Main control point of replication • Asks master for replication log Replication • Gets binlog event from master MySQL Binary log Server • Log of everything executed Slave • Divided into transactional components • Used for replication and point-in-time recovery Terminology Synchronous replication Master • A transaction is not committed until the data MySQL has been replicated (and applied) Server • Safer, but slower • This is available in MySQL Cluster Replication Asynchronous replication • A transaction is replicated after it has been committed MySQL Server • Faster, but you can in some cases loose transactions if master fails Slave • Easy to set up between MySQL servers Configuring Replication Required configuration – my.cnf Replication Master log-bin server_id Replication Slave server_id Optional items in my.cnf – What
[Show full text]
Beyond Relational Databases
EXPERT ANALYSIS BY MARCOS ALBE, SUPPORT ENGINEER, PERCONA Beyond Relational Databases: A Focus on Redis, MongoDB, and ClickHouse Many of us use and love relational databases… until we try and use them for purposes which aren’t their strong point. Queues, caches, catalogs, unstructured data, counters, and many other use cases, can be solved with relational databases, but are better served by alternative options. In this expert analysis, we examine the goals, pros and cons, and the good and bad use cases of the most popular alternatives on the market, and look into some modern open source implementations. Beyond Relational Databases Developers frequently choose the backend store for the applications they produce. Amidst dozens of options, buzzwords, industry preferences, and vendor offers, it’s not always easy to make the right choice… Even with a map! !# O# d# "# a# `# @R*7-# @94FA6)6 =F(*I-76#A4+)74/*2(:# ( JA$:+49>)# &-)6+16F-# (M#@E61>-#W6e6# &6EH#;)7-6<+# &6EH# J(7)(:X(78+# !"#$%&'( S-76I6)6#'4+)-:-7# A((E-N# ##@E61>-#;E678# ;)762(# .01.%2%+'.('.$%,3( @E61>-#;(F7# D((9F-#=F(*I## =(:c*-:)U@E61>-#W6e6# @F2+16F-# G*/(F-# @Q;# $%&## @R*7-## A6)6S(77-:)U@E61>-#@E-N# K4E-F4:-A%# A6)6E7(1# %49$:+49>)+# @E61>-#'*1-:-# @E61>-#;6<R6# L&H# A6)6#'68-# $%&#@:6F521+#M(7#@E61>-#;E678# .761F-#;)7-6<#LNEF(7-7# S-76I6)6#=F(*I# A6)6/7418+# @ !"#$%&'( ;H=JO# ;(\X67-#@D# M(7#J6I((E# .761F-#%49#A6)6#=F(*I# @ )*&+',"-.%/( S$%=.#;)7-6<%6+-# =F(*I-76# LF6+21+-671># ;G';)7-6<# LF6+21#[(*:I# @E61>-#;"# @E61>-#;)(7<# H618+E61-# *&'+,"#$%&'$#( .761F-#%49#A6)6#@EEF46:1-#
[Show full text]
Two Node Mysql Cluster
Two Node MySQL Cluster 1.0 EXECUTIVE SUMMARY This white paper describes the challenges CONTENTS involved in deploying the 2 node High Available MySQL-Cluster with a proposed solution. For the SECTION PAGE sake of users reading this document it also describes in brief the main components of the MySQL Cluster which are necessary to 1.0 EXECUTIVE SUMMARY………………………1 understand the paper overall. 2.0 BUSINESS CHALLENGES……………………1 The solution relies on the Linux HA framework 3.0 MYSQL CLUSTER……………………………..1 (Heartbeat/Pacemaker) so the white paper can 3.1 CLIENTS/APIS………………………………….2 be best understood with the knowledge of Linux 3.2 SQL NODE………………………………………2 HA framework. 3.3 DATA NODE…………………………………….2 3.4 NDB MANAGEMENT NODE………………….3 3.5 CHALLENGES………………………………….3 3.6 SOLUTION………………………………………4 4.0 REFERENCES………………………………….7 2.0 BUSINESS CHALLENGES The MySQL cluster demands at least 4 nodes to be present for deploying a High Available MySQL database cluster. The typical configuration of any enterprise application is a 2 Node solution (Active-Standby mode or Active-Active Mode). The challenge lies in fitting the MySQL Clsuter Nodes in the 2 Nodes offering the application services and to make it work in that configuration with no single point of failure. 3.0 MYSQL CLUSTER The intent of this section is to briefly mention the important actors and their roles in the overall MySQL Cluster. For more information the reader can refer to the MYSQL reference documents from its official site (http://dev.mysql.com/doc/index.html). MySQL Cluster is a technology that enables clustering of in-memory databases in a “shared-nothing system”.
[Show full text]
Data Platforms Map from 451 Research
1 2 3 4 5 6 Azure AgilData Cloudera Distribu2on HDInsight Metascale of Apache Kaa MapR Streams MapR Hortonworks Towards Teradata Listener Doopex Apache Spark Strao enterprise search Apache Solr Google Cloud Conﬂuent/Apache Kaa Al2scale Qubole AWS IBM Azure DataTorrent/Apache Apex PipelineDB Dataproc BigInsights Apache Lucene Apache Samza EMR Data Lake IBM Analy2cs for Apache Spark Oracle Stream Explorer Teradata Cloud Databricks A Towards SRCH2 So\ware AG for Hadoop Oracle Big Data Cloud A E-discovery TIBCO StreamBase Cloudera Elas2csearch SQLStream Data Elas2c Found Apache S4 Apache Storm Rackspace Non-relaonal Oracle Big Data Appliance ObjectRocket for IBM InfoSphere Streams xPlenty Apache Hadoop HP IDOL Elas2csearch Google Azure Stream Analy2cs Data Ar2sans Apache Flink Azure Cloud EsgnDB/ zone Platforms Oracle Dataﬂow Endeca Server Search AWS Apache Apache IBM Ac2an Treasure Avio Kinesis LeanXcale Trafodion Splice Machine MammothDB Drill Presto Big SQL Vortex Data SciDB HPCC AsterixDB IBM InfoSphere Towards LucidWorks Starcounter SQLite Apache Teradata Map Data Explorer Firebird Apache Apache JethroData Pivotal HD/ Apache Cazena CitusDB SIEM Big Data Tajo Hive Impala Apache HAWQ Kudu Aster Loggly Ac2an Ingres Sumo Cloudera SAP Sybase ASE IBM PureData January 2016 Logic Search for Analy2cs/dashDB Logentries SAP Sybase SQL Anywhere Key: B TIBCO Splunk Maana Rela%onal zone B LogLogic EnterpriseDB SQream General purpose Postgres-XL Microso\ Ry\ X15 So\ware Oracle IBM SAP SQL Server Oracle Teradata Specialist analy2c PostgreSQL Exadata
[Show full text]
Mariadb Presentation
THE VALUE OF OPEN SOURCE MICHAEL ”MONTY” WIDENIUS Entrepreneur, MariaDB Hacker, MariaDB CTO MariaDB Corporation AB 2019-09-25 Seoul 11 Reasons Open Source is Better than Closed Source ● Using open standards (no lock in into proprietary standards) ● Resource friendly; OSS software tend to work on old hardware ● Lower cost; Usually 1/10 of closed source software ● No cost for testing the full software ● Better documentation and more troubleshooting resources ● Better support, in many cases directly from the developers ● Better security, auditability (no trap doors and more eye balls) ● Better quality; Developed together with users ● Better customizability; You can also participate in development ● No vendor lock in; More than one vendor can give support ● When using open source, you take charge of your own future Note that using open source does not mean that you have to become a software producer! OPEN SOURCE, THE GOOD AND THE BAD ● Open source is a better way to develop software ● More developers ● More spread ● Better code (in many cases) ● Works good for projects that can freely used by a lot of companies in their production or products. ● It's very hard to create a profitable company developing an open source project. ● Not enough money to pay developers. ● Hard to get money and investors for most projects (except for infrastructure projects like libraries or daemon services). OPEN SOURCE IS NATURAL OR WHY OPEN SOURCE WORKS ● You use open source because it's less expensive (and re-usable) ● You solve your own problems and get free help and development efforts from others while doing it.
[Show full text]
Mysql Cluster Wann Brauche Ich Das?
MySQL Cluster Wann brauche ich das? Mario Beck Principal Sales Consultant [email protected] The presentation 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. 2.1BN USERS 8X DATA GROWTH IN 5 YRS 750M USERS 70+ NEW DOMAINS EVERY 60 SECONDS 20M APPS PER DAY 40% DATA GROWTH PER YEAR 600 NEW VIDEOS EVERY 60 SECONDS $1TR BY 2014 100K TWEETS PER MINUTE $700BN IN 2011 5.3BN MOBILE SUBS IN 2010 (78% PENETRATION) 13K iPHONE APPS 370K CALL MINUTES EVERY 60 SECONDS DOWNLOADED PER MINUTE Driving new Database Requirements EXTREME WRITE SCALABILITY REAL TIME USER EXPERIENCE ROCK SOLID RELIABILITY ELIMNATE BARRIERS TO ENTRY No Trade-Offs Transactional Integrity EXTREME WRITE SCALABILITYComplex REALQueries TIME USER EXPERIENCE Standards & Skillsets ROCK SOLID RELIABILITY ELIMNATE BARRIERS TO ENTRY No Trade-Offs: Cellular Network HLR / HSS Location Updates AuC, Call Routing, Billing Pre & Post Paid • Massive volumes of write traffic • <3ms database response • Downtime & lost transactions = lost $ Billing, AuC, VLR MySQL Cluster in Action: http://bit.ly/oRI5tF No Trade-Offs: eCommerce • Integrated Service Provider platform • eCommerce • Payment processing • Fulfillment • Supports 1k+
[Show full text]
Mysql Workbench Release Notes
MySQL Workbench Release Notes Abstract This document contains release notes for the changes in each release of MySQL Workbench. For additional MySQL Workbench documentation, see MySQL Workbench. MySQL Workbench platform support evolves over time. For the latest platform support information, see https:// www.mysql.com/support/supportedplatforms/workbench.html. Updates to these notes occur as new product features are added, so that everybody can follow the development process. If a recent version is listed here that you cannot find on the download page (https://dev.mysql.com/ downloads/), the version has not yet been released. The documentation included in source and binary distributions may not be fully up to date with respect to release note entries because integration of the documentation occurs at release build time. For the most up-to-date release notes, please refer to the online documentation instead. For legal information, see the 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-09-23 (revision: 23350) Table of Contents Preface and Legal Notices ................................................................................................................. 4 Changes in MySQL Workbench 8.0 .................................................................................................... 5 Changes in MySQL Workbench 8.0.27 (Not yet released, General Availability) .............................. 5 Changes in MySQL Workbench 8.0.26 (2021-07-20, General Availability) ..................................... 5 Changes in MySQL Workbench 8.0.25 (2021-05-11, General Availability) ..................................... 5 Changes in MySQL Workbench 8.0.24 (2021-04-20, General Availability) ..................................... 5 Changes in MySQL Workbench 8.0.23 (2021-01-18, General Availability) ..................................... 7 Changes in MySQL Workbench 8.0.22 (2020-10-19, General Availability) ....................................
[Show full text]
Mysql Cluster – Evaluation and Tests, OCTOBER 2, 2012 1 Mysql Cluster – Evaluation and Tests
MySQL Cluster – Evaluation and Tests, OCTOBER 2, 2012 1 MySQL Cluster – Evaluation and Tests Michael Raith (B.Sc.), Master-Student F Abstract Websites or web applications, whether they represent shopping systems, on demand services or a social networks, have something in common: data must be stored somewhere and somehow. This job can be achieved by various solutions with very different performance characteristics, e.g. based on simple data ﬁles, databases or high performance RAM storage solutions. For today’s popular web applications it is important to handle database operations in a minimum amount of time, because they are struggling with a vast increase in visitors and user generated data. Therefore, a major requirement for modern database application is to handle huge data (also called “big data”) in a short amount of time and to provide high availability for that data. A very popular database application in the open source community is MySQL, which was originally developed by a swedisch company called MySQL AB and is now maintenanced by Oracle. MySQL is shipped in a bundle with the Apache web server and therefore has a large distribution. This database is easily installed, maintained and administrated. By default MySQL is shipped with the MyISAM storage engine, which has good performance on read requests, but a poor one on massive parallel write requests. With appropriate tuning of various database settings, special architecture setups (replication, partitioning, etc.) or other storage engines, MySQL can be turned into a fast database application. For example Wikipedia uses MySQL for their backend data storage. In the lecture “Ultra Large Scale Systems” and “System Engineering” teached by Walter Kriha at Media University Stuttgart, the question “Can a MySQL database application handle more then 3000 database requests per second?” came up some time.
[Show full text]
Sales Consultant Mysql GBU ([email protected]) Agenda 1 Mysql Within Oracle
MySQL @ Oracle Carsten Thalheimer Sales Consultant MySQL GBU ([email protected]) Agenda 1 MySQL within Oracle 2 Overview of MySQL architecture 3 Inside MySQL 4 Commercial MySQL vs. „Open Source“ MySQL 5 MySQL Subscription / MySQL License 6 A MySQL Reference 7 Questions and Answers Copyright © 2014, Oracle and/or its affiliates. All rights reserved. | 2 MySQL within Oracle More Investment, More Innovation ... 20 Years MySQL … 10 Years InnoDB of Oracle Stewardship … 5 Years MySQL within Oracle 2x Engineering Staff 3x QA Staff Dez 2009 2x Support Staff May 2015 Copyright © 2014, Oracle and/or its affiliates. All rights reserved. | 3 Source: http://db-engines.com/en/ranking Copyright © 2014, Oracle and/or its affiliates. All rights reserved. | Source: http://db-engines.com/en/ranking Copyright © 2014, Oracle and/or its affiliates. All rights reserved. | Driving MySQL Innovation Year 2010 – 2013 (from MySQL Release 5.1 to MySQL Release 5.6) MySQL Enterprise Monitor 2.2 MySQL Cluster Manager 1.1 MySQL Enterprise Backup 3.7 MySQL Database 5.6 MySQL Cluster 7.1 Oracle VM Template for MySQL MySQL Cluster 7.2 MySQL Utilities 1.3 MySQL Cluster Manager 1.0 Enterprise Edition MySQL Cluster Manager 1.2 MySQL Cluster 7.3 MySQL Workbench 5.2 MySQL Enterprise Oracle Certifications MySQL Utilities 1.0 MySQL Workbench 6.0 MySQL Database 5.5 MySQL Windows Installer MySQL Migration Wizard MySQL Enterprise Monitor 3.0 MySQL Enterprise Backup 3.5 MySQL Enterprise Security MySQL for Excel 1.0 / 1.1 MySQL Enterprise Backup 3.9 MySQL Enterprise Monitor 2.3 MySQL Enterprise Scalability MySQL Enterprise Backup 3.8 MySQL Yum Linux repository MySQL Enterprise Audit MySQL Enterprise HA (DRBD) All GA! - 2010 All GA! - 2011 All GA! - 2012 All GA! - 2013 and Connector/ODBC, Connector/PHP, Connector/Net, Connector/J, Connector Python, Connector /C++, Connector/C, Ruby Driver … Copyright © 2014, Oracle and/or its affiliates.
[Show full text]
A Closer Look at Mysql Cluster an Architectural Overview - Mariadb White Paper - 08-26-13-001.Docx Page 1
w: www.mariadb.com e: [email protected] MySQL Cluster Internal Architecture Max Mether MariaDB Keywords: MySQL Cluster, MySQL, High Availability, HA, Clustering, Architecture 1 Introduction MySQL Cluster is tightly linked to the MySQL server, yet it is a separate product. Due to its distributed nature, MySQL Cluster has a far more complicated architecture than a standard MySQL database. This presentation and white paper will describe the internal architecture of the MySQL Cluster product and the different mechanisms and process that exists to insure the availability of the cluster. We will also take a close look at the data and message flow that takes place between the nodes in the cluster during different types of operations. 2 MySQL Cluster Features MySQL Cluster can be distinguished from many other clustering products in that it offers five nines availability with a shared-nothing architecture. Most clustering products use a shared-disk architecture. Using a shared- nothing architecture allows the cluster to run on commodity hardware, thus greatly reducing costs compared to shared-disk architecture. Having a shared-nothing architecture does, however, come with a different cost, namely, a more complex way of ensuring high availability and synchronization of the nodes which is mainly seen as increased network traffic. MySQL Cluster also provides ACID transactions with row level locking using the READ-COMMITTED isolation level. MySQL Cluster is, in general, an in-memory database, however non-indexed data can be stored on disk and the disks are also used for checkpointing to ensure durability through system shutdown. MySQL cluster provides unique hash indexes as well as ordered T-tree indexes.
[Show full text]
In Mysql/Mariadb?
T h e O W A S P F o u n d a t i o n h t t p : / / w w w . o w a s p . o r g O W A S P E U T o u r B u c h a Do you r e s“GRANT ALL PRIVILEGES” t ... in MySQL/MariaDB? 2 0 1 DevOps Engineer 3 Gabriel PREDA [email protected] @eRadical Co pyr igh t © Th e O W AS P Fo un dat ion Per mi ssi on is gr ant ed to co py, dis tri bu te an d/ or mo dif y thi s do cu me nt un de r the ter ms of the O W AS P Lic en se. 2 DevOps = new BORG DevOps Engineer ??? ● Development – Web Applications (“Certified MySQL Associate”, “Zend Certified Engineer”) – Real Time Analytics ● Operations – MySQL DBA (15+ instances) – Sysadmin (<25 virtual & physical servers) 3 My MySQL● Over 15 MariaDB / TokuDBMariaDB(s) instances ● Statistics in MariaDB – < 1TB from Oct 2012 – < 12G raw data daily – < 12,000,000 events processed daily – < 90,000,000 rows added daily BigData? NO!!! ● I can copy all of that to my laptop ● “Working data set” - less than 1G & less than 7,500,000 rows 4 MySQL History ● 1983 – first version of MySQL created by Monty Wideniuns ● 1994 – MySQL is released OpenSource ● 2004 Oct – MySQL 4.1 GA ● 2005 Oct – InnoDB (Innobase) is bought by Oracle – Black Friday ● 2008 Ian – MySQL AB is bought by Sun (1bn $) ● 2008 Nov – MySQL 5.1 GA ● 2009 Apr – Sun is bought by Oracle (7,4 bn $) ● 2010 Dec – MySQL 5.5 GA ● 2012 Apr – MariaDB 5.5 GA ● 2013 Feb – MySQL 5.6 – first version made by Oracle ● 2013 Feb – MySQL will be replaced by MariaDB in Fedora & OpenSuSE * Max Mether – SkySQL “MySQL and MariaDB: Past, Present and Future” 5 Where are we NOW()? Drizzle MySQL TokuDB (Oracle) (Tokutek) Percona Server (Percona) MariaDB (Monty Program, Brighthouse MariaDB Foundation) (Infobright) Replication: ● Asynchronous InfiniDB ● Semi-synchronous (Calpont) ● Galera Synchronous (Codership) ● Tungsten Replication (Continuent) 6 Elementary..
[Show full text]
Securing Your Mysql/Mariadb Data Ronald Bradford, Colin Charles Percona Live Europe Amsterdam 2016
Securing your MySQL/MariaDB Data Ronald Bradford, Colin Charles Percona Live Europe Amsterdam 2016 #PerconaLive @bytebot @RonaldBradford About: Colin Charles ● Chief Evangelist (in the CTO office), Percona Inc ● Founding team of MariaDB Server (2009-2016), previously at Monty Program Ab, merged with SkySQL Ab, now MariaDB Corporation ● Formerly MySQL AB (exit: Sun Microsystems) ● Past lives include Fedora Project (FESCO), OpenOffice.org ● MySQL Community Contributor of the Year Award winner 2014 ● http://bytebot.net/blog/ #PerconaLive @bytebot @RonaldBradford About: Ronald Bradford ● Experienced MySQL database guy ● Author/Blogger/Speaker ● Looking for my next great opportunity ● http://ronaldbradford.com/presentations/ ● http://effectivemysql.com #PerconaLive @bytebot @RonaldBradford Agenda ● Observed insecure practices ● Securing communications ● Securing connections ● Securing data ● Securing user accounts ● Securing server access #PerconaLive @bytebot @RonaldBradford Found in Signs of Poor Security any version ● old_passwords ● 'root' MySQL user without password ● Users without passwords ● 'root' MySQL user ● Anonymous users ● Generic OS DBA user e.g. 'dba' ● GRANT privilege users ● Disabled OS ● ALL privilege users Firewall/SELinux/Apparmor ● '%' host user accounts ● Open data directory privileges ● Default test database #PerconaLive @bytebot @RonaldBradford Easy Fixes $ mysql_secure_installation #PerconaLive @bytebot @RonaldBradford Very easy to Current Insecure Practices fix practices ● Using password on command line ○ Command
[Show full text]