Database and Application Code
With no showstoppers found with MariaDB, the next phase of validating the solution entailed taking a look at moving on to the implementation phase by evaluating both database and application code for migration to arrive at a feasible plan. Once the work w
- PDF / 213,116 Bytes
- 15 Pages / 439.37 x 666.142 pts Page_size
- 43 Downloads / 265 Views
Database and Application Code With no showstoppers found with MariaDB, the next phase of validating the solution entailed taking a look at moving on to the implementation phase by evaluating both database and application code for migration to arrive at a feasible plan. Once the work was completed in the previous phase they were pretty optimistic and excited about the MariaDB solution; however, they wanted to analyze the process of not only adding new customers but migrating existing customers on the Oracle DBMS to MariaDB. The LOE was also a concern from the applications side as well as mapping data types, database code changes, and rewrites for PL SQL, and of course sequences. From a database perspective the database team was not too concerned about anything from their side. There would be syntax differences, and Vernon knew they would have to code around packages and such that Oracle had built in but MariaDB did not. The sequences were not even going to be a huge hurdle, as they could be implemented to work similarly to Oracle with some PL SQL programming on the database side. The bigger question was the application code, and it turned out to be easier than anyone thought.
© William Wood 2019 W. Wood, Migrating to MariaDB, https://doi.org/10.1007/978-1-4842-3997-1_3
33
Chapter 3
Database and Application Code
Migrating the Database The team at Financial Widgets Plus (FWP) found that MariaDB contained the requirements they were looking for and so much more, all in one package, but there were still many unanswered questions. The biggest question had been answered, and yes MariaDB was viable and they had made it their choice; however, how they were going to get there opened up a copious amount of additional questions. It seemed easy for new customers to just start out on the new database once the code database and application side were modified to work. On the database side there were triggers, stored procedures, and datatypes to migrate, but Vernon and his team needed to do a deep dive into everything to get an idea of the scope of work involved. Certainly, there would be application code changes to interface and perform transactions with the new OSDBMS. All functionality would have to be available, or a new process would have to be created to perform the same actions just as they were currently being completed. It was now time to take a look at the scope involved and get a strategic plan in place to make it happen, while at the same time mitigating risk. Vernon had an idea of exactly how to plan his approach to completing a task as monumental as this. In higher level mathematics and physics, one of the biggest and often overlooked side effects was learning to break what seemed like daunting tasks into smaller, easier to manage and solve tasks, approaching each one individually. Previous experience gave him some insight from having completed his share of successful Oracle migrations over the years, so Vernon was certain it could be done. Obviously this was going to be quite different, as he wasn’t managing th
Data Loading...
