Decoux: Sieve: depends on the size!
Brabant: Decoux: 200GB between AWS mysql and Aurora.
Decoux: Sieve: that rules out a logical backup
Trecarichi: Decoux: Yes indeed. and it can only be single threaded.
Decoux: Sieve: all tables are InnoDB, I hope?
Weisse: So I’m trying to pump the maximum datarate from the process. Its hard to debug
Coldsmith: Nelles: mysqldump -u uname -p –routines dbname yourfile.sql
Dannhaus: Nelles: Choices for backing up MySQL data include: stopping the server and copying the files :: mysqldump -F–single-transaction :: LVM snapshot :: innobackup/xtrabackup :: replication AND one of the previous.
Decoux: Go the innobackup/xtrabackup route
Kalbach: Decoux: I dont have filesystem access.
Leibowitz: AWS only provides a MySQL interface.
Decoux: Then mysqldump –single-transaction and patience.
Cuomo: I’d use the steps to set it up as a replication slave +
Saska: Decoux: I don’t quite understand what “—single-transaction” is doing
Decoux: In that case, include the master data with the dump.
Buchert: Is this literally dumping each table as a single select?
Decoux: Sieve: ensures consistency for your dump.
Decoux: Sieve: no, as a single transaction.
Maree: Decoux: so it locks the tables?
Decoux: Danblack: I wouldn’t bother with that, and just schedule a 1-2 hours window
Julia: I have a query like this http://pastebin.com/LCCpzdix I got only records were tooltip is filled in. But I used left outer joins
Bottino: Decoux: thanks for the help
Mogg: Does anyone have any experience with AWS aurora?
Kosorog: Sieve: so what made you decide to move to RDS?
Decoux: Sieve: https://dev.mysql.com/doc/refman/5.6/en/mysqldump.html#option_mysqldump_single-transaction
Decoux: Sieve: the manual is very good at explaining at it does.
Firsching: Danblack: everything was in RDS when I started and actually, it “just works”. Its powerful once you start to understand its limitations.
Himber: Danblack: Our data is growing 20GB a week so we’re looking at trying out aurora.
Mcmanuis: Which is a new engine developed by amazon.
Decoux: Sieve: thankfully, you avoided MyISAM
Vinger: We don’t have the systems engineering or DBA skills in house to support running our own MySQL.
Decoux: Danblack: albeit that solution is fine for busy systems.
Lantz: I want this construction left join m_string mstt on mstt.m_stringID = msutt.m_stringID and mstt.type like ‘%m_page_element_tooltip%’ inner join m_lnaguage ml on ml.m_languageID = mstt.m_languageID how to do this?
Enriguez: How to let mysql now that the inner join on language is only needed when a record on tooltip is found
Decoux: Jop008: why are you using those useless brackets?
Imbruglia: To group things with parenthesis
Hunkins: If I do this left join m_string mstt on mstt.m_stringID = msutt.m_stringID and mstt.type like ‘%m_page_element_tooltip%’
Damme: Inner join m_language ml on ml.m_languageID = mstt.m_languageID
Simpler: Then I only got records with a tooltip since the inner join on language
Valencia: The inner join on language is only needed when there is a hit on m_string
Decoux: FROM a LEFT JOIN b INNER JOIN c ON . AS d ON .
Vanwassenhove: Lost in stupid parenthesis
Mangaoang: Given my example whre to place
Adib: Left join m_string mstt on mstt.m_stringID = msutt.m_stringID and mstt.type like ‘%m_page_element_tooltip%’
Devoe: Inner join m_language ml on ml.m_languageID = mstt.m_languageID
Decoux: Jop008: you made the same mistake as before.