Easy MySQL Database Migrations (No Downtime and No Data Dumps!!)

Поделиться
HTML-код
  • Опубликовано: 5 янв 2022
  • Migrate your MySQL database with zero downtime! We’re leveraging the power of Vitess to let you connect your database to PlanetScale. Try us out as a replica and then switch over your database to PlanetScale completely. That’s right, no dumping your data, no restoring from backup. Just give us a connection and let us handle the rest.
    Database Imports Documentation - docs.planetscale.com/concepts...
    📚 Learn more about PlanetScale
    • Website: planetscale.com/
    • Docs: docs.planetscale.com/
    ------------------
    💬 Follow PlanetScale on social media
    • Twitter: / planetscale
    • TikTok: / planetscale
    • Twitch: / planetscale
    • LinkedIn: / planetscale
  • НаукаНаука

Комментарии • 20

  • @alkolaqi83
    @alkolaqi83 Год назад +1

    Im glad you posted this video so practical use case ❤

  • @vasiovasio
    @vasiovasio 2 года назад

    Wow, Amazing! Real Aurora RDS Competitor! Good Luck!

  • @iamrafiqulislam
    @iamrafiqulislam 2 года назад

    Will pkease show how migrate from db in a VPS server? do we need to configure replication on source db or plametscale will do that automatically? Please, also instruct how to configure bind-adress securely, please would be a great help?

  • @ashokgtm
    @ashokgtm Год назад

    seems to be something interesting tool, like to explore more.

  • @OANVanh
    @OANVanh 2 года назад

    Hi planetscale.
    my main branch contains data but when I create a development branch it is created without the information contained in the tables, is this normal or something extra has to be done so that it also copies the data from the tables.

    • @PlanetScale
      @PlanetScale  2 года назад

      Hey there! The schema should be migrated to your new branch, but right now it does not copy over the data although we plan to update that in the future.

  • @kevinzunigacuellar
    @kevinzunigacuellar 2 года назад

    Feels like magic

    • @PlanetScale
      @PlanetScale  2 года назад

      It's one of our favorite features. Glad you enjoyed it!

  • @vextorfx6243
    @vextorfx6243 Год назад

    I hope that the plan basic remains free for life and offers the same advantages.

  • @wsh4and
    @wsh4and 2 года назад

    What instance is your aws rds? I am using t2.micro
    I got an error 'Could not connect to database
    Please check your connection information above and try again. Learn about common issues
    Error checking server configuration: expected gtid mode to be ON, is instead []'

    • @PlanetScale
      @PlanetScale  2 года назад

      Hi! Were you able to check that the gtid mode is on in your AWS console settings for RDS? We explain more in our documentation at planetscale(dot)com/docs.

    • @wsh4and
      @wsh4and 2 года назад

      @@PlanetScale hi, aws premium support told me that it’s off by default and can’t be change 😩. Any other way to do this?

    • @PlanetScale
      @PlanetScale  2 года назад +1

      @@wsh4and Could you email into PlanetScale support and we can try to help you out more? You can find a link on our homepage.

  • @mjeffria
    @mjeffria Год назад

    I got an error 'external database settings are not compatible with PlanetScale: "log_bin" must be "ON", but found: "OFF"'

    • @PlanetScale
      @PlanetScale  Год назад

      You will need to have the binary logs enabled on the database you're importing. I don't know what external database provider you are using, but you can probably google its name + "binary logs" and find where the setting is. They are included in the migration guides here: planetscale.com/docs/tutorials/aws-rds-migration-guide

    • @mjeffria
      @mjeffria Год назад

      @@PlanetScale i used aws rds mysql 5.7. How to turn on it?

    • @PlanetScale
      @PlanetScale  Год назад +1

      @@mjeffria Perfect. The link will be helpful then for getting the bin log settings correct.

  • @cinismovirtual
    @cinismovirtual Год назад +1

    It's a real pain that PlanetScale don't support constraints! 🥺 Each database in the real world uses them, so in practical terms, at least in my case, is useless.

    • @PlanetScale
      @PlanetScale  Год назад +1

      You can read a bit more about why we don't support them here: planetscale.com/docs/learn/operating-without-foreign-key-constraints And also how to operate without them. As your database scales, they can definitely become a problem.

    • @HalesEnchanted
      @HalesEnchanted Год назад

      Yeah. I had to completely re-write my database to get it to work with my laravel app!