|
(→Appendix A: Database Moving)
|
(→Appendix A: Database Moving)
|
| Line 57: | |||
| There seems to be some confusion lately regarding moving databases/cloning databases. If the database is not switching vendor types (i.e. ''Apache Derby'' to ''Microsoft SQLServer'') and instead using the same vendor type (i.e. ''Oracle'' to ''Oracle''), there is no sense in running the '''migrate-db''' script to export & import data into the new database that may lie in a new datacenter. The reason for this is because '''migrate-db''' uses [http://www.dbunit.org/ dbunit] to export information from the database, store it into an XML file that anthillpro recognizes with its internal DDLs to do an import (note...not a native dump format for each database vendor type), and then imports the XML information into the new database. This is adding a layer of complexity to the process...almost as if relying on a software process to take care of something that a hardware process can already do. | There seems to be some confusion lately regarding moving databases/cloning databases. If the database is not switching vendor types (i.e. ''Apache Derby'' to ''Microsoft SQLServer'') and instead using the same vendor type (i.e. ''Oracle'' to ''Oracle''), there is no sense in running the '''migrate-db''' script to export & import data into the new database that may lie in a new datacenter. The reason for this is because '''migrate-db''' uses [http://www.dbunit.org/ dbunit] to export information from the database, store it into an XML file that anthillpro recognizes with its internal DDLs to do an import (note...not a native dump format for each database vendor type), and then imports the XML information into the new database. This is adding a layer of complexity to the process...almost as if relying on a software process to take care of something that a hardware process can already do. | ||
| - | Instead, users should look to using their respective database vendor's tools to export the database, import it at the new datacenter, and then hook up anthillpro with the new datacenter's database. | + | Instead, users should look to using their respective database vendor's tools to export the database, import it at the new datacenter, and then hook up anthillpro with the new datacenter's database. What may need changed is [http://wiki.urbancode.com/AnthillPro/Cloning_an_AnthillPro_Instance#Connection_Settings_Modification listed on the Cloning AnthillPro Instance page, under 'Connection Settings']. |
