Since travel to deliver content and awareness is being held for a while (COVID-19), I am missing the interaction I would have with people at random times during a conference, the exchange of ideas and impromptu problem solving.
The hallway track of a conference has always been my favorite part: the networking, exchanging ideas, getting feedback about products, all of that is harder to replicate without talks and social the setting of a conference.
I decided to experiment and try to find new ways to interact with “my” audience, the idea of Office Hours came, which originally is not mine, however I like the fact that I can have a technical conversation with someone that has questions about databases (not just about Cloud SQL) and also provide a window of opportunity for you to give me feedback on our products.
Examples of things we can talk about:
Best Practices for Migrations
Where to store your data
Should I put my Server on Kubernetes?
How do I migrate my data to the cloud?
The pilot started with 30 min sessions with the availability to talk to up to 10 people weekly (5h/week). However I think it is more productive a change to up to 3h/week and talking to 9 people in 20 min slots in more timezones.
Write down your questions and add it to the booking tool.
If a lengthy context is needed to understand your problem, please add the information in the booking tool, however do not send to me:
PII – Personal Identifiable Information
Your SQL Dump
Your intellectual property
No database credentials
Have defined scope of what you want to talk about, I can’t solve everything in 20 minutes.
Do not double book, other people should also take advantage of this
This is not a guaranteed consultancy agreement, this is just people talking informally about tech problems and possible solutions, information shared and explained are guides, you are responsible for weighing your options and if any advice is executed, the outcome is your responsibility.
-h the hostname or IPV4 address of the primary should replace [MASTER_IP]
-P the port or the primary server, usually [MASTER_PORT] value will be 3306
-u takes the username passed on [USERNAME]
-p informs that a password will be given
--databases a comma separated list of the databases to be imported. Keep in mind [DBS]should not include the sys, performance_schema, information_schema, and mysql schemas
--hex-blob necessary for dumping binary columns which types could be BINARY, BLOB and others
--skip-triggers recommended for the initial load, you can import the triggers at a later moment
--master-data according to the documentation: “It causes the dump output to include a CHANGE MASTER TO statement that indicates the binary log coordinates (file name and position) of the dumped server”
--order-by-primary it dumps the data in the primary key order
--no-autocommit encloses the table between a SET autocommit=0 and COMMIT statements
--default-character-set informs the default character set
--ignore-table must list the VIEW to be ignored on import, for multiple views, use this option multiple times. Views can be imported later on after promotion of the replica is done
--single-transaction a START TRANSACTION is sent to the database so the dump will contain the data up to that point in time
--set-gtid-purged writes the the state of the GTID information into the dump file and disables binary logging when the dump is loaded into the replica
After that the result is compressed in a GZIP file and uploaded to a bucket on Google Cloud Storage with gsutil cp - gs://[BUCKET]/[PATH_TO_DUMP] where [BUCKET] is the bucket you created on GCS and [PATH_TO_DUMP] will save the file in the desired path.
Be aware that no DDL operations should be performed in the database while the dump is being generated else you might find inconsistencies.
See something wrong in this tutorial? Please don’t hesitate to message me through the comments or the contact page.