Building a Case for Database Migration

Content of the case of building database migration Section Title Page 0 Purpose 3 0 Reason why the company has migrated. 3 0 What hindered the decision of migration. 40 Migration Process 50 Conclusion Summary 6 0 Summary and Conclusion 60 Purpose This document describes the support framework for the enterprise IT department to make business decisions about the best migration method from one IT system to another database system .

There are a number of frameworks in the Object Relational Mapping (ORM) that allows you to perform database migration during the deployment process. Migration of the schema database is the process of updating the database to the new schema and performing the necessary data manipulation. The way of thinking is simple. I used a new table in the database and I wrote some code that I need to package and migrate. Migration is code executed by the migration tool and tells you what modifications you want to make to the database. In this case, create a new table.

Migration can be thought of as a code type representation of the database schema. Since migration is similar to database versioning, teams can easily change and share the application's database schema. Migration is often paired with Laravel's architecture builder to easily build the application's database schema. Therefore, the consistency level of the database can be achieved throughout the team. The most powerful ORM can be used with various database collections. The Eloquent ORM shipped with Laravel provides an excellent simple ActiveRecord implementation for manipulating databases. Each database table has a corresponding "model" that is used to interact with the table. You can use the model to query the data in the table and insert new records into the table. This is very effective if you want to build applications that have hundreds of tables and relationships. With Eloquent you can create a very clean and cluttered free code for interacting with the database.