Tutorial ini menjelaskan langkah-langkah migrasi database MySQL ke Oracle menggunakan SQL Developer, meliputi pembuatan koneksi database sumber dan tujuan, membuat repository, melakukan proses migrasi, dan memeriksa hasil migrasi database beserta datanya di Oracle.
Part2 Best Practices for Managing Optimizer StatisticsMaria Colgan
Part 2 of the SQL Tuning workshop focuses on Optimizer Statistics and the best practices for managing them, including when and how to gather statistics. It also covers what additional information you may need to give the Optimizer and provides guidance on when not to gather statistics. Finally we look at all of the techniques you can use to speed up statistics gathering including taking advantage of Incremental statistics, parallelism and concurrency.
Part2 Best Practices for Managing Optimizer StatisticsMaria Colgan
Part 2 of the SQL Tuning workshop focuses on Optimizer Statistics and the best practices for managing them, including when and how to gather statistics. It also covers what additional information you may need to give the Optimizer and provides guidance on when not to gather statistics. Finally we look at all of the techniques you can use to speed up statistics gathering including taking advantage of Incremental statistics, parallelism and concurrency.
FOSDEM 2022 MySQL Devroom: MySQL 8.0 - Logical Backups, Snapshots and Point-...Frederic Descamps
Logical dumps are becoming popular again. MySQL Shell parallel dump & load utility changed to way to deal with logical dumps, certainly when using instances in the cloud. MySQL 8.0 released also an awesome physical snapshot feature with CLONE.
In this session, I will show how to use these two ways of saving your data and how to use the generated backup to perform point-in-time recovery like a rockstar with MySQL 8.0 in 2022 !
Upgrading MySQL databases do not come without risk. There is no guarantee that no problems will happen if you move to a new major MySQL version.
Should we just upgrade and rollback immediately if problems occur? But what if these problems only happen a few days after migrating to this new version?
You might have a database environment that is risk-adverse, where you really have to be sure that this new MySQL version will handle the workload properly.
Examples:
- Both MySQL 5.6 and 5.7 have a lot of changes in the MySQL Optimizer. It is expected that this improves performance of my queries, but is it really the case? What if there is a performance regression? How will this affect my database performance?
- Also, there are a lot of incompatible changes which are documented in the release notes, how do I know if I'm affected by this in my workload? It's a lot to read..
- Can I go immediately from MySQL 5.5 to 5.7 and skip MySQL 5.6 even though the MySQL documentation states that this is not supported?
- Many companies have staging environments, but is there a QA team and do they really test all functionality, under a similar workload?
This presentation will show you a process, using open source tools, of these types of migrations with a focus on assessing risk and fixing any problems you might run into prior to the migration.
This process can then be used for various changes:
- MySQL upgrades for major version upgrades
- Switching storage engines
- Changing hardware architecture
Additionally, we will describe ways to do the actual migration and rollback with the least amount of downtime.
Presented the "A Cloud Journey - Move to the Oracle Cloud" on behalf of Ricardo Gonzalez during Bulgarian Oracle User Group Spring Conference 2019. This presentation discusses various methods on how to migrate to the Oracle Cloud and provides recommendations as to which tool to use (and where to find it) especially assuming that Zero Downtime Migration is desired, for which the new Zero Downtime Migration tool is described and discussed in detail. More information: http://www.oracle.com/goto/move
FOSDEM 2022 MySQL Devroom: MySQL 8.0 - Logical Backups, Snapshots and Point-...Frederic Descamps
Logical dumps are becoming popular again. MySQL Shell parallel dump & load utility changed to way to deal with logical dumps, certainly when using instances in the cloud. MySQL 8.0 released also an awesome physical snapshot feature with CLONE.
In this session, I will show how to use these two ways of saving your data and how to use the generated backup to perform point-in-time recovery like a rockstar with MySQL 8.0 in 2022 !
Upgrading MySQL databases do not come without risk. There is no guarantee that no problems will happen if you move to a new major MySQL version.
Should we just upgrade and rollback immediately if problems occur? But what if these problems only happen a few days after migrating to this new version?
You might have a database environment that is risk-adverse, where you really have to be sure that this new MySQL version will handle the workload properly.
Examples:
- Both MySQL 5.6 and 5.7 have a lot of changes in the MySQL Optimizer. It is expected that this improves performance of my queries, but is it really the case? What if there is a performance regression? How will this affect my database performance?
- Also, there are a lot of incompatible changes which are documented in the release notes, how do I know if I'm affected by this in my workload? It's a lot to read..
- Can I go immediately from MySQL 5.5 to 5.7 and skip MySQL 5.6 even though the MySQL documentation states that this is not supported?
- Many companies have staging environments, but is there a QA team and do they really test all functionality, under a similar workload?
This presentation will show you a process, using open source tools, of these types of migrations with a focus on assessing risk and fixing any problems you might run into prior to the migration.
This process can then be used for various changes:
- MySQL upgrades for major version upgrades
- Switching storage engines
- Changing hardware architecture
Additionally, we will describe ways to do the actual migration and rollback with the least amount of downtime.
Presented the "A Cloud Journey - Move to the Oracle Cloud" on behalf of Ricardo Gonzalez during Bulgarian Oracle User Group Spring Conference 2019. This presentation discusses various methods on how to migrate to the Oracle Cloud and provides recommendations as to which tool to use (and where to find it) especially assuming that Zero Downtime Migration is desired, for which the new Zero Downtime Migration tool is described and discussed in detail. More information: http://www.oracle.com/goto/move
Tutorial Pentaho - Membuat Data base werehaouseJames Montolalu
dokumen ini menjelaskan cara dari awal penginstalan pentaho sampai tahapan pembuatan basis data terdistribusi menggunakan pentaho. aplikasi pentaho ini saya jalankan di sistem operasi windosws 7
Modul Praktikum Pemrograman Berorientasi Objek (Chap.12)Debby Ummul
Modul ini berisi materi praktikum tentang pembuatan aplikasi CRUD perpustakaan. Sebenarnya ini adalah edisi revisi dari modul sebelumnya yaitu Chapter 11. hehe....
Bahasa yang digunakan masih sama yaitu menggunakan bahasa Java
Tugas Besar Sistem Manajemen Basisdata
Anggota Kelompok:
Septian Rico Hernawan / 14523032
Achmad Fariid Amali / 14523075
Tungky Adi Pradana / 14523081
Lukman Ahmad Riadi / 14523245
UNTUK DOSEN Materi Sosialisasi Pengelolaan Kinerja Akademik DosenAdrianAgoes9
sosialisasi untuk dosen dalam mengisi dan memadankan sister akunnya, sehingga bisa memutakhirkan data di dalam sister tersebut. ini adalah untuk kepentingan jabatan akademik dan jabatan fungsional dosen. penting untuk karir dan jabatan dosen juga untuk kepentingan akademik perguruan tinggi terkait.
1. Tutorial migrasi database mysql – oracle menggunakan sql developer
1. kita masuk ke mysql cek database yang akan dimigrasi. Disini kita akan melakukan migrasi
database ‘classicmodels’.
2. membuat user di oracle dengan nama ‘repository’ yang akan digunakan sebagai repository saat
melakukan migrasi.
2.
3. 3. buka aplikasi sql developer, sekarang kita akan memulai langkah migrasi. Kita akan membuat
koneksi dengan cara klik tanda + pada pojok kiri halaman. Kemudian, klik new connection maka akan
muncul halaman seperti dibawah ini
4. membuat koneksi mysql ke sql developer dengan mengisi connection name dengan nama root
dan menggunakan username dan password user yang disesuaikan dengan username dan password
di mysql. Kemudian kita test apakah success atau tidak dengan cara klik tombol test. Jika success,
maka klik save.
4. 5. membuat koneksi oracle ke sql developer dengan mengisi connection name dengan nama system
dan menggunakan username dan password user yang disesuaikan dengan username dan password
user system di oracle. Kemudian kita test apakah success atau tidak dengan cara klik tombol test.
Jika success, maka klik save.
6. membuat koneksi user baru yang telah dibuat di oracle sebagai repository dalam proses migraasi
dengan cara yang sama seperti langkah sebelumnya.
5. 7. status koneksi repository, mysql, dan oracle masih disconnect sehingga kita perlu membuat
statusnya menjadi connect dengan cara klik kanan pilih connect.
8. kita akan membuat repository, dengan klik tools-Migration-Repository management-creat
repository
Kemudian pilih yang akan dijadikan repository.
12. 17. setelah proses migrasi selesai.
Convert database, kemudian klik kanan dan generate target. Lakukan seperti langkah saat proses
migrasi diatas.
13. 18. buka oracle login dengan user system, jika migrasi berhasil akan muncul user baru dengan nama
yang sama seperti database yang dimigrasi. Kemudian, buka user tersebut dan berikan password
untuk login.
14. 19. login dengan user baru yang sama dengan nama database yang dimigrasi.
19. buka tabel. Maka akan muncul tabel yang sama dengan tabel yang ada didatabase yang telah
dimigrasi.
