LEADER 03407nam 22005295 450 001 9910338006603321 005 20200705065521.0 010 $a1-4842-3997-0 024 7 $a10.1007/978-1-4842-3997-1 035 $a(CKB)4100000007204878 035 $a(MiAaPQ)EBC5611949 035 $a(DE-He213)978-1-4842-3997-1 035 $a(CaSebORM)9781484239971 035 $a(PPN)232967407 035 $a(OCoLC)1085010604 035 $a(OCoLC)on1085010604 035 $a(EXLCZ)994100000007204878 100 $a20181206d2019 u| 0 101 0 $aeng 135 $aurcnu|||||||| 181 $ctxt$2rdacontent 182 $cc$2rdamedia 183 $acr$2rdacarrier 200 10$aMigrating to MariaDB $eToward an Open Source Database Solution /$fby William Wood 205 $a1st ed. 2019. 210 1$aBerkeley, CA :$cApress :$cImprint: Apress,$d2019. 215 $a1 online resource (162 pages) 311 $a1-4842-3996-2 330 $aMitigate the risks involved in migrating away from a proprietary database platform toward MariaDB?s open source database engine. This book will help you assess the risks and the work involved, and ensure a successful migration. Migrating to MariaDB describes the process and lessons learned during a migration from a proprietary database management engine to the MariaDB open source solution. The book discusses the drivers for making the decision and change, walking you through all aspects of the process from evaluating the licensing, navigating the pitfalls and hurdles of a migration, through to final implementation on the new platform. The book highlights the cost-effectiveness of MariaDB and how the licensing worries are simplified in comparison to running on a proprietary platform. You?ll learn to do your own risk assessment, to identify database and application code that may need to be modified or re-implemented, and to identify MariaDB features to provide the security and failover protection needed by corporate customers. Let the author?s experience in migrating a financial firm to MariaDB inform your own efforts, helping you to develop a road map for both technical and political success within your own organization as you migrate away from proprietary lock-in toward MariaDB?s open source solution. What You'll Learn: Evaluate and compare licensing costs between proprietary databases and MariaDB Perform a proper risk assessment to inform your planning and execution of the migration Build a migration road map from the book?s example that is specific to your situation Make needed application changes and migrate data to the MariaDB open source database engine. 606 $aDatabase management 606 $aOpen source software 606 $aComputer programming 606 $aDatabase Management$3https://scigraph.springernature.com/ontologies/product-market-codes/I18024 606 $aOpen Source$3https://scigraph.springernature.com/ontologies/product-market-codes/I29090 615 0$aDatabase management. 615 0$aOpen source software. 615 0$aComputer programming. 615 14$aDatabase Management. 615 24$aOpen Source. 676 $a004.36 700 $aWood$b William$4aut$4http://id.loc.gov/vocabulary/relators/aut$0769577 801 0$bUMI 801 1$bUMI 906 $aBOOK 912 $a9910338006603321 996 $aMigrating to MariaDB$92510914 997 $aUNINA